01-15-2015 09:59 AM
Hi All,
I'm looking at moving Netbackup (7.1.0.4) to a new server. Once this has stablized I will update to the latest version. From what I understand I need to copy the DR file to the new server and then after the import run a catalog restore. I assume that I have to take the latest INCR and FULL DR files for the import? I also want to change the name of the server. From what I was researching using this method it requires the same hostname. Are there any other options if I want to change the hostname?
DR files
-rwxrwx--- 1 544 18 117K Jan 6 18:00 Catalog-Backup_1420585068_INCR
-rwxrwx--- 1 544 18 133K Jan 7 11:13 Catalog-Backup_1420647028_INCR
-rwxrwx--- 1 544 18 149K Jan 8 12:21 Catalog-Backup_1420737551_INCR
-rwxrwx--- 1 544 18 165K Jan 9 11:47 Catalog-Backup_1420821901_INCR
-rwxrwx--- 1 544 18 177K Jan 10 10:04 Catalog-Backup_1420902124_INCR
-rwxrwx--- 1 544 18 35K Jan 11 09:47 Catalog-Backup_1420985337_FULL
-rwxrwx--- 1 544 18 40K Jan 12 10:57 Catalog-Backup_1421077953_INCR
-rwxrwx--- 1 544 18 57K Jan 13 16:43 Catalog-Backup_1421185280_INCR
-rwxrwx--- 1 544 18 73K Jan 14 12:52 Catalog-Backup_1421257819_INCR
-rwxrwx--- 1 544 18 89K Jan 15 10:22 Catalog-Backup_1421335217_INCR
Thanks,
Nick
Solved! Go to Solution.
01-15-2015 10:15 AM
If you want to change your master server's hostname, the ONLY option is to enlist professional services from either Symantec or one of their designated partners. The hostname is sprinkled throughout the NetBackup configuration files, databases, etc., and requires the use of special tools only available to those folks in order to accurately make those changes. Doing this yourself would not be supported by Symantec.
For the server upgrade, you would need to stay within the Windows family for the master server's OS; again, changing to a Unix/Linux based OS would require professional services.
Yes, you will need the most recent full and incremental backups to recover the catalog. Plan for enough downtime to perform the changeover. You of course cannot have two servers on your network with the same name, so you might want to build the new server first with a different name, then change it once the old master server has been shut down. That would help minimize downtime.
For more complete info on upgrade steps, see Marianne's excellent recent post:
https://www-secure.symantec.com/connect/forums/need-upgrade-os-netbackup-media-server
01-15-2015 10:15 AM
If you want to change your master server's hostname, the ONLY option is to enlist professional services from either Symantec or one of their designated partners. The hostname is sprinkled throughout the NetBackup configuration files, databases, etc., and requires the use of special tools only available to those folks in order to accurately make those changes. Doing this yourself would not be supported by Symantec.
For the server upgrade, you would need to stay within the Windows family for the master server's OS; again, changing to a Unix/Linux based OS would require professional services.
Yes, you will need the most recent full and incremental backups to recover the catalog. Plan for enough downtime to perform the changeover. You of course cannot have two servers on your network with the same name, so you might want to build the new server first with a different name, then change it once the old master server has been shut down. That would help minimize downtime.
For more complete info on upgrade steps, see Marianne's excellent recent post:
https://www-secure.symantec.com/connect/forums/need-upgrade-os-netbackup-media-server
01-15-2015 10:23 AM
Thanks Ron for the quick response.
01-16-2015 12:42 AM
Some TNs to confirm what Ron has said:
Using catalog backup and recovery to transfer NetBackup catalogs between Windows master servers as part of a hardware refresh
http://www.symantec.com/docs/TECH77447
How to migrate the NetBackup catalog information from one platform to another (UNIX to Windows or vice versa), rename a Master Server, cluster an existing Master Server, or merge multiple NetBackup domains.
http://www.symantec.com/docs/TECH31385