You could use export/import node across the network with server-to-server virtual volumes; or, you could use physical tapes (especially if they're collocated), which would eliminate the network data transfer. These are just TWO ways to "skin this cat"... but that's what you asked. Some folks would just leave the data on the original server and start running to the new server; it all depends on your backup strategies, policies, archive data vs. backup data, billing, etc.... Don France -----Original Message----- From: Roland Bender [mailto:[EMAIL PROTECTED]] Sent: Sunday, November 19, 2000 10:20 PM To: [EMAIL PROTECTED] Subject: How to restore data from one TSM Server to a client on another TS M Server (separate TSM Databases) Have a nice day.... i face the following problem. We have two TSM Servers with one TSM instance on server one, and two TSM instances on Server two. If a user moved to another department, his personal data should follow him from TSM server two instance two, to TSM sever one. I noticed the export node command but was not sure if it point me the right way. Any help would be appreciated. Thank you. Best regards, Freundliche Grüsse Roland Bender Boehringer Ingelheim Pharma KG A Informationsverarbeitung IT Betrieb Ingelheim Job- und Datenservice Telefon: +49 (0) 6132/ 77 - 2014 Telefax: +49 (0) 6132 /77 - 3216 e-Mail: [EMAIL PROTECTED] > __________________________________________________________________________ > ____________________________ > Notice: An electronic message is not binding on its sender. Any message referring to a binding engagement must be confirmed in writing and duly signed. > __________________________________________________________________________ > ____________________________ > Internetauftritt der Firma Boehringer Ingelheim Pharma KG => http://www.boehringer-ingelheim.com > __________________________________________________________________________ > ____________________________ >
