ADSM-L

Re: moving client node data from one library to another

2005-09-15 11:20:38
Subject: Re: moving client node data from one library to another
From: William Boyer <bjdboyer AT COMCAST DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 15 Sep 2005 11:19:57 -0400
Use the MOVE NODEDATA  command.


Bill Boyer
"Some days you're the bug, some days you're the windshield" - ??

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Alexander Lazarevich
Sent: Thursday, September 15, 2005 11:16 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: moving client node data from one library to another

TSM 5.3.1 on win2K server.

We have two OVerland Neo 4100 libraries, one is LTO2 (two LTO2 drives) and the 
other is LTO3 (two LTO3 drives). The libraries are
seperate. TSM has sepearete backup discspool->tape paths for each library. And 
policy sets are setup accordingly for which clients
we want to backup to which library.

The LTO3 library is brand new, and we need to move some of the data from the 
LTO2 library to the LTO3 library. We want to move the
data belonging only to certain client nodes. For example, we want the LTO3 
library to be collocated, and the LTO2 library will
remain non-collocated, and we want to move only a few of the client node data 
that is currently on the LTO2 library (and the data is
non-collocated) to the LTO3 library and have it be collocated. However, I don't 
see any way to move data just for specific client
nodes. I only see how to move data via volumes and spools.

Is there any way to move data that is bound to a client node?

I have changed the client node policy sets, thus the ones we want to move, any 
future backups will rebind that client data to the
new policy set, and thus any new data will be moved to the LTO3 library, and 
thus be collocated. But how do I move client data that
is still on the LTO2 library?

Thanks in advance,

Alex

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