ADSM-L

Re: Moving Node Data Between Storage Pools

2005-02-14 12:58:48
Subject: Re: Moving Node Data Between Storage Pools
From: David E Ehresman <deehre01 AT LOUISVILLE DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 14 Feb 2005 12:58:27 -0500
As TRushforth pointed out, MOVE NODEDATA only works for the pirmary
storage pool. A BACKUP STG of the new primary storagepool will get the
data into the new copy storagepool.  Then you are left with all your old
data that is also still in the old copy storagepool.  Unless this was
fixed int 5.3, there is no good way to get rid of it.  You can let it
expire or you can delete the volumes (discarddata-yes) containing the
old data and then rebackup the old primary storagepool to recreate any
data that was still valid on those deleted volumes.

David

>>> charles.hart AT MEDTRONIC DOT COM 02/14/05 11:06 AM >>>
We have a windows client domain that writes to its own tape pool for
about 200+ Windows clients (Collocation On Primary Tape Pool / Off on
Copy Pool).  We would like to split the clients out in to additional
domains for restore purposes.

The question I have is how do move the data of client A in Domain A to
a new Domain with a new tape pool.

Options
Move Data moves backup data at volume level not client specific.
Export / Import Node is only for server to server...
Upd node to new domain and hope TSM will Magically migrate data?
Upd node to new domain and hope TSM will know to restore previous data
from old tape pool etc?
Make New Domain's backup Copy Pool Absolute to force a full? Then let
old data drop off?

Appreciate any input.

Regards,

Charles

<Prev in Thread] Current Thread [Next in Thread>