Forum Discussion
For me, the time and effort to create a new primary server and reconfigure your backup environment is not worth it. You will have huge problem to deal with, with the media server as they belong to only one netbackup domain and with old backups at the datadomains.
There is another way you can move your server if you cannot afford the time to do a catalogue recovery. I have used it many times to migrate net backups from one server to another. Not for 10.1.1, but I do not see why it will not work.
Use an "rsync tool" to start copying the veritas folder from your server to the new server without stopping netbackup. Use a destination folder other that the original location but at the same drive as netbackup installation (eg not the c:\program files\veritas but c:\veritas_temp)
When the first run finish, run it again and again until the data transfer time is acceptable.
Then
Stop the netbackup primary server. Check that all processes are stopped and run the "rsync tool" ones more.
Remove the server from the domain (if the server belongs to a domain) and change the IP of the server.
Add the old primary IP to the new server.
Rename the new server with the same name as the old server and add the server to the domain.
Install the netbackup primary server using the same netbackup version and netbackup name (sort or FQDN).
When you finish with the installation, stop netbackup.
Rename the c:\program files\veritas to c:\program files\ veritas_new
Move the c:\veritas_temp to c:\program files\veritas.
Copy from the old server registry the server list and any other variables you may have changed.
Start netbackup.
I suggest you to first test it in a test environment
StefanosM That suggested scenario seems to be very good. However by rsync you mean robocopy's mirroring?
Thank you very much.
- Nicolai12 months agoModerator
Yes, Rsync is for Linux what robocopy is for Windows.
Related Content
- 7 years ago
- 8 years ago
- 10 years ago