Re: [ADSM-L] Combining two TSM servers into one.

If you don't already have domains on server 2 with the same names as the
ones on server 1, you'll want to EXPORT POLICY to server 2 first, and make
sure that the copy groups have valid storage pools for their destinations.
Then, when you EXPORT NODE, they'll be imported into the same policy
domains they were in on server 1, and the data will be copied into the
storage pools indicated for those copy groups.

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
robben.leaf AT usbank DOT com



             "Ochs, Duane"
             <Duane.Ochs AT QG DOT CO
             M>                                                         To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor                                                  cc
             Manager"
             <[email protected]                                     Subject
             .EDU>                     Re: [ADSM-L] Combining two TSM
                                       servers into one.

             04/21/2008 04:20
             PM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






One question. I've read the documentation and it's not clear where the
data goes after it is imported.
There is no STG or devclass parameter allowed.



-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Robben Leaf
Sent: Monday, April 21, 2008 3:36 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Combining two TSM servers into one.

You can export a node's data directly from one TSM server instance to
another one if you use the TOSERVER parameter in the EXPORT NODE
command.

That being said, depending on your retention policies, it might be
simpler
- and faster - to simply take the clients that back up to TSM server 1,
and point them at TSM server 2, and let the old data expire off of
server 1 as time passes. If you need to restore from the old TSM server,
just point the client back to server 1 for the restore. When all the
data on server 1 is older than your retention policy, it can be
decommissioned. Archive data should be copied to server 2, of course.

Hope that helps!

Robben Leaf
Enterprise Storage Backup and Retention
651-962-2698
robben.leaf AT usbank DOT com



             "Ochs, Duane"
             <Duane.Ochs AT QG DOT CO
             M>
To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor
cc
             Manager"
             <[email protected]
Subject
             .EDU>                     [ADSM-L] Combining two TSM
servers
                                       into one.

             04/21/2008 03:21
             PM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






I'm sure someone has done this before. I'm just looking for a little
kick in the right direction.
I have two TSM servers.
One (TSM server 1) with a L700 library using SDLT320 drives with a 50gb
db and approximately 90 TB of data and another (TSM server 2) using a SL
T950 with LTO-4. Both are behind the same SVC.
I'm combining the two TSM servers into the same library and into the
same TSM DB.

Option one, get a LTO-4 drive connected to TSM server1 and export nodes
one at a time, then import the data into TSM server 2.

Option two, get a SDLT320 drive connected to TSM server 2, export from
TSM server 1 and import into 2.

??? Option three,  Is it possible to export to disk, and move the file
system from TSM server 1 to TSM server 2 and import ?

Option 1 and 2 will be time consuming, Option 3 would probably be the
most efficient, if possible.
Any advice or any other suggestions ?

Both TSM servers are running TSM 5.4.3 on AIX 5.3.

Thanks,
Duane



U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains
information that is, or may be, covered by electronic communications
privacy laws, and is also confidential and proprietary in nature. If you
are not the intended recipient, please be advised that you are legally
prohibited from retaining, using, copying, distributing, or otherwise
disclosing this information in any manner. Instead, please reply to the
sender that you have received this communication in error, and then
immediately delete it. Thank you in advance for your cooperation.



---------------------------------------------------------------------



U.S. BANCORP made the following annotations
---------------------------------------------------------------------
Electronic Privacy Notice. This e-mail, and any attachments, contains 
information that is, or may be, covered by electronic communications privacy 
laws, and is also confidential and proprietary in nature. If you are not the 
intended recipient, please be advised that you are legally prohibited from 
retaining, using, copying, distributing, or otherwise disclosing this 
information in any manner. Instead, please reply to the sender that you have 
received this communication in error, and then immediately delete it. Thank you 
in advance for your cooperation.



---------------------------------------------------------------------