TSM – Moving Nodes to a new Domain. A question that frequently come up by TSM Admins that “how to move Nodes to a new Domain?” This is usually the case when you had grouped several nodes under one domain then you needed to change the backup policies for few of them, so you find out the need to move these few nodes to a new policy Domain. Below is a high view of the steps to Move Nodes to a new TSM Domain: 1. There is a change introduced by Microsoft for certificates. From the vsbkp.log located on the server where the Virtual Server Agent is installed. ![]() Define the following. Assign new management class as default management class. Validate and activate new policy set. Update node to reflect domain change. Update associated client backup jobs by copying the old schedule(s) to new domain, update new schedule(s) accordingly, associate copied schedule(s) to updated nodes, delete old schedule(s) from old domain. Run a move nodedata specifying from=old. Run a backup stgpool from the new seq. Take into account the new stgpool in any admin schedules or scripts you have set up. Recall copy stgpool tapes for old domain, or let the data expire off. You can, if you so desire, after recalling the tapes, move nodedata to scratch tape and delete the volume when complete with discard=yes. Please leave me a comment if you had a success or a failure following these steps . Install Sql Agent Backup Exec 2012 Tapestry
It was very popular so I’ve combined the two posts together and added a. If you have decided to use StarWind Virtual Tape Library in an environment where you have Symantec Backup Exec and looking to find out how to integrate both products.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2017
Categories |