Hi, Ruud.  Never underestimate the bandwidth of a truck - but latency
can be problematic.  A somewhat workable option would be to perform an
export node filedata=all to tape, then FedEx the tapes next-day.  Once
you import the data on the target server, you can then do an export
toserver= fromdate= merge=yes, which hopefully will minimize the payload
sent over the WAN.

It would be even easier if, prior to the export, you could get
management to agree that you could afford to lose a day's worth of
backups, in which case you wouldn't even have to do the merge.  (Ok,
maybe two days.)

On 7/31/2012 4:52 AM, Meuleman, Ruud wrote:

All,

We have to move about 150 TB backup data from one TSM LC to an other. Using command "export node 
<node_name> filedata=all toserver <server_name>" will take months.

Does anybody knows if it is possible to export the metadata of backupdata from 
one LC to an other and update the owner of the volumes on the LM? The LC's 
share the same library. The involved TSM clients have there own 
collocationgroup.

Kind Regards,
Ruud Meuleman

**********************************************************************

This transmission is confidential and must not be used or disclosed by anyone 
other than the intended recipient. Neither Tata Steel Europe Limited nor any of 
its subsidiaries can accept any responsibility for any use or misuse of the 
transmission by anyone.

For address and company registration details of certain entities within the 
Tata Steel Europe group of companies, please visit 
http://www.tatasteeleurope.com/entities

**********************************************************************