Paul,
Not sure what your retention looks like, but if you move the nodes to a
different domain with a different retention (smaller), then the data will
get bound to the new policy after a backup is performed and the new data
retention will kick in at that time. I believe that your understanding of
You could always use the "COPY DOMAIN" command to create the new domain, which
would include all current policy sets, management classes, and copy groups.
Then modify as needed.
May be easier than recreating the wheel ..
-Rick Adamson
-Original Message-
From: ADSM: Dist Stor Manage
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
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.
