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 creat
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/gotc
r" <[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
>Wh
> What are the pitfalls/gotchas/hazards/ROT/suggestions of changing a NODES
> Policy Domain ?
If the node has centrally scheduled backups you will need to copy the
schedule to the new domain (unless a suitable schedule exists there
already) and execute a 'define association' command to associate t
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
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 ca
