Kelly,

Thanks for the info.

You are right - with 140 clients we do not use collocation.  So data is spread
all over the libraries.

The other problem (and I forgot to mention this) is that two of the three
existing libraries will be retired completely.  A third (retained) library will
need the "cleared" space to absorb incoming data from a
"to-be-retired" library.  Some of the exported data would end up in a
newly-added library on our system.

The reassignments I have in mind are this:

Backups:
3575-L18 (node set 1) --> 3583
3575-L12 (node set 1) --> 3583
3575-L06    -->  3583

3575-L12 (node set 2) --> 3575-L18
3575-L18 (node set 2)  -> stays put

3575-L06  --> gone
3575-L12 --> gone

So, for example, I would relocate the data from node set #1 in the L18 to the
new 3583, then clear the source space in the L18.
Then I would relocate the data from node set #1 in the L12 to the newly-cleared
space in the L18.  Then I could retire the L12.

And so forth...

It's the actual export/import technique that I don't completely understand.

Any additional help would be greatly appreciated.

Thanks again.

Tab Trepagnier
ADSM administrator
Laitram Corporation






"Kelly J. Lipp" <[EMAIL PROTECTED]> on 01/24/2001 12:37:53 PM

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:    (bcc: Tab Trepagnier/Corporation/Laitram/US)
Subject:  Re: Moving node data from one library to another




You could export a nodes data and then import it to different pools.  You
may well find that's a royal pain.  How about rearranging your pools so
you've got the configuration the way you want it.  Then do a selective
backup of those clients using the new library.  Then let the old data in the
other library die a natural death through expiration.  That will take awhile
depending on your retention parameters but certainly easier than moving the
data around.

Export is the only way to be selective about getting data off of tapes.  If
you original pool is collocated, you could perhaps figure out which tapes
were being used by which nodes and move the data from those volumes to the
new pools.  I sort of doubt that you're collocated though.

Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (240) 539-7175
Email: [EMAIL PROTECTED] or [EMAIL PROTECTED]
www.storsol.com
www.storserver.com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Tab Trepagnier
Sent: Wednesday, January 24, 2001 10:39 AM
To: [EMAIL PROTECTED]
Subject: Moving node data from one library to another


We are reorganizing our data and library assignments on our ADSM 3.1 (soon
TSM
4.1) system.

Right now we use management classes to steer any given node's data to a
particular library.

The reorg will require that data from certain nodes be reassigned to
different
libraries and that their existing data be moved to the newly assigned
libraries.

What is the cleanest way to do that?  I have very limited experience with
Export
and none whatsoever with Import.

Obviously, the requirement is that no data be lost.

Thanks in advance.

Tab Trepagnier
ADSM administrator
Laitram Corporation

Reply via email to