Re: Changing Policy Domains
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU What are the pitfalls/gotchas/hazards/ROT/suggestions of changing a NODES Policy Domain ? You will lose any associated client schedules. However, rather than create a whole new policy domain, just create some new (non-default) management classes, and use them in the option files for the nodes you want to affect? -- Mark Stapleton
Re: Changing Policy Domains
Thanks for the quick response. I do not understand the scope of lose any associated client schedules ? Do you mean for the node that I am moving to the new PD ? I thought about the MC issue. However, wouldn't this cause issues with everything already backed-up ? I assume it would automagically rebind everything or is this only for new backups ? What would happen do old, inactive backups that are still ticking off the clock due to deleted filesystems, switched systems, etc ? Stapleton, Mark [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] 07/23/2004 11:59 AM Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] To [EMAIL PROTECTED] cc Subject Re: Changing Policy Domains From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU What are the pitfalls/gotchas/hazards/ROT/suggestions of changing a NODES Policy Domain ? You will lose any associated client schedules. However, rather than create a whole new policy domain, just create some new (non-default) management classes, and use them in the option files for the nodes you want to affect? -- Mark Stapleton
Re: Changing Policy Domains
If the OLD policy domain and the NEW policy domain don't have the same management class NAMES, and the client has files bound to the OLD management class names that don't exist in NEW, you will get some weird messages in the activity log when expiration runs. If you create the new PD by copying the old PD, that shouldn't be a problem... -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan Forray/AC/VCU Sent: Friday, July 23, 2004 11:52 AM To: [EMAIL PROTECTED] Subject: Changing Policy Domains What are the pitfalls/gotchas/hazards/ROT/suggestions of changing a NODES Policy Domain ? I really need to move some nodes to different PD's so I can move their management classes to use different, non-collocated storage pools ! I can't move the whole PD/MC since there are some heavy-hitters I can't move due to the size of the non-collocated storagepool.
Re: Changing Policy Domains
You will have to def assoc to add them to a backup schedule in the new domain. If you want to move the existing data to the new storagepool structure, you will need to do move nodedata NODE from=OLDSTGPOOL to=NEWSTGPOOL for the primary tape pool. Your normal backup stg processing will create the new copies in the copypool tape storagepool. If you want to then get rid of the data in the old copypool stgpool, you will have to delete vol discarddata=yes for each of the copypool tapes that contain data for that node. You will need to restart the scheduler on the node. [EMAIL PROTECTED] 7/23/2004 11:51:54 AM What are the pitfalls/gotchas/hazards/ROT/suggestions of changing a NODES Policy Domain ? I really need to move some nodes to different PD's so I can move their management classes to use different, non-collocated storage pools ! I can't move the whole PD/MC since there are some heavy-hitters I can't move due to the size of the non-collocated storagepool.
