Export/Import node might be your best bet for what you are trying to achieve. I'm not sure if that method will carry the backupset information along with it, but you have the option of using DEFine BACKUPSET to make the backupsets available on the destination server.
From the online TSM help:
Use this command to define a client backup set that was previously generated on one server and make it available to the server running this command. The client node has the option of restoring the backup set from the server running this command rather than the one on which the backup set was generated.
Any backup set generated on one server can be defined to another server as long as the servers share a common device type. The level of the server to which the backup set is being defined must be equal to or greater than the level of the server that generated the backup set.
Hope this helps,
Ted
At 01:03 PM 11/20/2003 +1100, you wrote:
Guys (and gals),
Is there a way to migrate node information (backup data, backupsets etc) between TSM servers? I have two identically configured TSM servers (4.2.3.0 on AIX) on the same network backing up around 1000 servers between them. As some of my nodes are holding more data than others, I have an uneven load on each TSM server and want to "migrate" nodes from one to the other. Registering the node on the other TSM server and pointing the node from one to the other is easy enough to do, but I won't retain backup history or backupset information.
Any assistance would be helpful.
Regards,
------------------------------------------------------------------------------
Graham Trigge IT Technical Specialist Server Support Telstra Australia
Office: (02) 8272 8657 Mobile: 0409 654 434
---------------------------------------- The information contained in this e-mail and any attachments to it: (a) may be confidential and if you are not the intended recipient, any interference with, use, disclosure or copying of this material is unauthorised and prohibited. If you have received this e-mail in error, please delete it and notify the sender; (b) may contain personal information of the sender as defined under the Privacy Act 1988 (Cth). Consent is hereby given to the recipient(s) to collect, hold and use such information for any reasonable purpose in the ordinary course of TES' business, such as responding to this email, or forwarding or disclosing it to a third party.
