cancel
Showing results for 
Search instead for 
Did you mean: 

Netbackup upgrade from 7.1.0.4 to 7.6.0.1

adminhp
Level 2

Hi,

Working on upgrading Netbackup master server 7.1.0.4 running on Windows 2003 R2 SP2 32Bit to Netbackup 7.6.0.1 running on Windows 2012. Single master/media server and not using any advanced features, just couple DSSUs and attached to a tape auto-loader, also using the master/media server as a vmware proxy for vSphere 5.0. Reading through the upgrade guide, it says Windows 2003 (32bit) is not supported for master/media server in 7.6. I have a new server with Windows 2012 installed.

The following link below is exactly what I need to get done, but the solution does not work for me, so not sure if I am missing something here which is highly possible. When I tried to upgrade Netbackup 7.1.0.4 to 7.6.0.1 on Windows 2003, the upgrade checker reports everything passed except the 32 bit OS check, but the upgrade simply does not launch. The plan was to upgrade to 7.6 and then import the catalogs to the new server.

Now looking at the 7.6 admin guide, the only OS it support is Windows 2012, so installing 7.1.0.4 on Windows 2012 and importing the catalogs from the old server seems to be out of question even though I have not tried it. Appreciate any help for pointers on how to get this done. Thanks

https://www-secure.symantec.com/connect/forums/upgrading-netbackup-71-netbackup-75-or-higher

http://www.symantec.com/business/support/index?page=content&id=TECH77447

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Amol_Nair
Level 6
Employee

Yes you are right starting Netbackup 7.6 support for windows 32-bit machines as master/media has been stopped.

 

You may need to follow a slightly longer procedure to get it done if you would like to move from windows 2003 to windows 2012. Here are the steps you would need to follow:

1. Take a full catalog backup on windows 2003 (32-bit) - 7.1.0.4.

2. Format your machine and install windows 2003 (64-bit).

3. Install Netbackup 7.1.0.4 on this 64 bit windows 2003 machine, keeping the hostname, and the netbackup install path the same.

4. Do a Full catalog recovery.

5. Upgrade Netbackup from 7.1.0.4 to 7.6.0.1 - on windows 2003 R2 - 64bit.

6. Take a Full catalog backup again.

7. Install windows 2012 keeping the hostname, Netbackup install path the same.

8 Install Netbackup 7.6.0.1 on the windows 2012 machine and then run another Full catalog recovery.

 

View solution in original post

4 REPLIES 4

Amol_Nair
Level 6
Employee

Yes you are right starting Netbackup 7.6 support for windows 32-bit machines as master/media has been stopped.

 

You may need to follow a slightly longer procedure to get it done if you would like to move from windows 2003 to windows 2012. Here are the steps you would need to follow:

1. Take a full catalog backup on windows 2003 (32-bit) - 7.1.0.4.

2. Format your machine and install windows 2003 (64-bit).

3. Install Netbackup 7.1.0.4 on this 64 bit windows 2003 machine, keeping the hostname, and the netbackup install path the same.

4. Do a Full catalog recovery.

5. Upgrade Netbackup from 7.1.0.4 to 7.6.0.1 - on windows 2003 R2 - 64bit.

6. Take a Full catalog backup again.

7. Install windows 2012 keeping the hostname, Netbackup install path the same.

8 Install Netbackup 7.6.0.1 on the windows 2012 machine and then run another Full catalog recovery.

 

adminhp
Level 2

Amol, Thanks for the step by step directions. Will do this.

chack22
Level 4

I have the same problem, but I'm going to do a 2-step upgrade using a Windows 2008R2 VM as the intermediate box., before doing another migration to the final 2012 box. Waiting for support for Windows 2012 R2 as a master before running through this. That way I have an easy roll-back, if something goes wrong, just power on the old master. Just a thought?

adminhp
Level 2

Thanks Chack. I eventually ended up installing Windows 2008R2 on the new physical server and then install 7.1. and then 7.1.0.4 patch and then did a catalog recovery, (The catalog import wizard did not run as advertised, so had to use the command line bprecover -wizard from admincmd). Then upgraded to 7.6.0.1 and everything worked relatively well other than some minor adjustments.

 

Since we use multiple DSSUs and the backup server is also a vmware proxy, I did not want to do this on a VM. I will now wait for 2012 R2 support and then do this all over again.Greatly appreciate the help and suggestions from both of you guys.