I don't know that you have to restart the schedules after changing the
node's policy domain, as long as you make sure to reset the schedule 
association.
Running QUERY ASSOCIATION when changing the domain is something I always
remember to do the moment after hitting enter.

On Fri, Jun 05, 2015 at 02:52:48PM +0000, Thomas Denier wrote:
> This should work fine. There will be some additional complications if you use 
> the TSM central scheduler to trigger backups for the affected nodes.
>
> You will need to copy schedule definitions from the old policy domain to the 
> new one, unless the new one already has suitable schedule definitions.
>
> You will need to execute "define association" commands.
>
> You may need to restart the schedule services (Windows) or processes 
> (Linux/Unix) on the affected nodes. My best guess is that this will be 
> necessary if prompt mode scheduling is used and will not be necessary if 
> polling mode scheduling is used.
>
> Thomas Denier
> Thomas Jefferson University
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Paul_Dudley
> Sent: Thursday, June 04, 2015 8:33 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Moving nodes to a new policy
>
> If I have nodes that are currently under a policy that keeps 5 backup 
> versions, can I move them to another policy which keeps only 2 backup 
> versions?
>
> Will TSM then start expiring all the older backup versions of files which are 
> no longer needed?
>
> We have two nodes which are taking up a lot of backup space in TSM and want 
> to reduce this.
> The information contained in this transmission contains privileged and 
> confidential information. It is intended only for the use of the person named 
> above. If you are not the intended recipient, you are hereby notified that 
> any review, dissemination, distribution or duplication of this communication 
> is strictly prohibited. If you are not the intended recipient, please contact 
> the sender by reply email and destroy all copies of the original message.
>
> CAUTION: Intended recipients should NOT use email communication for emergent 
> or urgent health care matters.

--
-- Skylar Thompson (skylar2 AT u.washington DOT edu)
-- Genome Sciences Department, System Administrator
-- Foege Building S046, (206)-685-7354
-- University of Washington School of Medicine