Export backup data between LC
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 **
Re: Export backup data between LC
The answer is no. What you can do with TSM 6.3, is set up node replication. Let the dying server replicate its data to the target server, and when it is in sync, break the replication and shut the dying server down. That's probably less work for you, but still won't happen quickly. Or if this is about server consolidation, you could just set up 2 instances on the target machine, without needing to get all the metadata in one DB. Can you tell us why you are doing this? Folks might have some more creative solutions. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Meuleman, Ruud Sent: Tuesday, July 31, 2012 7:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export backup data between LC 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 **
Re: Export backup data between LC
Hi You can export node form source server and import to target and after that set replication ... This will speed up the process But if you go with export/import for replication you should export from source and import on target and after that set replication... there is IBM note about this Regards Chavdar On Tue, Jul 31, 2012 at 3:06 PM, Prather, Wanda wanda.prat...@icfi.com wrote: The answer is no. What you can do with TSM 6.3, is set up node replication. Let the dying server replicate its data to the target server, and when it is in sync, break the replication and shut the dying server down. That's probably less work for you, but still won't happen quickly. Or if this is about server consolidation, you could just set up 2 instances on the target machine, without needing to get all the metadata in one DB. Can you tell us why you are doing this? Folks might have some more creative solutions. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Meuleman, Ruud Sent: Tuesday, July 31, 2012 7:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export backup data between LC 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 **
Re: Export backup data between LC
Been there - done that - and as Wanda said, there is no easy/quick way. When we went to the new split-licensing model, I had to create a separate TSM server for the clients we are PVU licensing - 6-nodes with 200TB occupancy and 100M objects had to be moved - and yes, it took many weeks. On Tue, Jul 31, 2012 at 7:52 AM, Meuleman, Ruud ruud.meule...@tatasteel.com 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 ** -- *Zoltan Forray* TSM Software Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html
Re: Export backup data between LC
We are upgrading TSM server 5.5.5.2 to TSM server 6.2.2.30. TSM LM 6.2 still supports TSM LC TSM5.5. When we have no TSM5.5 anymore we will upgrade to TSM 6.3. Backup client we start new backups on the TSM 6.2.2.30. Archive client we have to export all data from TSM server 5.5.5.2 to TSM server 6.2.2.30. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Prather, Wanda Sent: Tuesday, July 31, 2012 2:07 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Export backup data between LC The answer is no. What you can do with TSM 6.3, is set up node replication. Let the dying server replicate its data to the target server, and when it is in sync, break the replication and shut the dying server down. That's probably less work for you, but still won't happen quickly. Or if this is about server consolidation, you could just set up 2 instances on the target machine, without needing to get all the metadata in one DB. Can you tell us why you are doing this? Folks might have some more creative solutions. -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Meuleman, Ruud Sent: Tuesday, July 31, 2012 7:52 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Export backup data between LC 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 ** ** 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 **
Re: Export backup data between LC
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 **
