Veritas-bu

Re: [Veritas-bu] Upgrade NetBackup from 6.5.6 (x86) to 7.1.0.4 (x64)

2012-06-27 22:50:41
Subject: Re: [Veritas-bu] Upgrade NetBackup from 6.5.6 (x86) to 7.1.0.4 (x64)
From: Anurag Sharma <sharma.anurag AT hotmail DOT com>
To: <kevin.oconnor AT esbi DOT ie>, veritas-bu <veritas-bu AT mailman.eng.auburn DOT edu>, <anurag.sharma3 AT hp DOT com>
Date: Thu, 28 Jun 2012 08:20:36 +0530
Very Nice Kevin
 
Thank you for sharing.
 
Others can also keep as this can be quite instrumental in migrations.
 
Anurag
 

From: Kevin.OConnor AT ESBI DOT IE
To: veritas-bu AT mailman.eng.auburn DOT edu
Date: Thu, 7 Jun 2012 12:51:33 +0100
Subject: Re: [Veritas-bu] Upgrade NetBackup from 6.5.6 (x86) to 7.1.0.4 (x64)

Hi Anurag,

 

This doc might be of some use.

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

 

I recently upgraded to 7.0.1 and new hardware, after researching it a lot it was easier than I expected.

We however kept the IP addresses the same to save hassle with media and client server connections, especially any behind a firewall.

I also ran a catalog backup to a SAN disk for part of the migration.

 

Here’s the general steps I carried out.

 

1.       The master server was running 6.5.5 on Windows 2003 so I first upgraded it to 7.0.1, NBUMServer1.

2.       I had a second server with windows 2008 x64 R2 with a different name but no Netbackup installation, NBUMServer2.

3.       I then stopped the NBUMServer1 services and disabled them in case someone tried to start them.

4.       Rename NBUMServer1 to NBUMServer3

5.       Assign new IP address to NBUMServer3

6.       Reboot NBUMServer3

7.       Delete the NBUMServer1 Active Directory account & DNS entry.

8.       Make sure the IP address of NBUMServer1 is free (ping –a NBUMServer3_ipaddress should not name a server)

9.       Change IP address on NBUMServer2 to NBUMServer1_ipaddress

10.   Rename the NBUMServer2 to NBUMServer1.

11.   Reboot the new NBUMServer1.

12.   Connect SAN drive with Catalog backup to NBUMServer1.

13.   Install Netbackup 7.0 x64 Master Server onto new NBUMServer1 box

14.   Patch to 7.0.1

15.   Stop all Netbackup Services

16.   Perform a Catalog restore from the SAN Drive

17.   Add Media server list back into Netbackup (Host Properties > Master Servers > Servers > Media Servers)

18.   Reboot NBUMServer1

19.   Install Java and copy conf file from NBUMServer3

20.   Copy over hosts file from NBUMServer3

21.   Run nbtstat –R

22.   Restart Netbackup Services

 

At that point everything came up on the New Hardware as the original Master Server Name and with everything still intact.

 

You could then connect both the ATL’s and the VTL to the new master server and have access to all of the old backups for restores.

 

Hope that helps.

 

Regards

Kevin

 

Kevin O’Connor | Storage Management | Service Delivery | Technology Solutions | ESB Business Service Centre | www.esb.ie

 

From: Anurag Sharma [mailto:sharma.anurag AT hotmail DOT com]
Sent: 01 June 2012 5:28P
To: veritas-bu
Subject: [Veritas-bu] Upgrade NetBackup from 6.5.6 (x86) to 7.1.0.4 (x64)

 

Hi Team,
 
We have one netbackup master server which is on x86 windows 2003 running netbackup 6.5.6 with two tape libraries LTO2/LTO3 respectively.
 
We have procured a new mastter server which is on 064 windows 2008 R2 with netbackup 7.1.0.4 with EMC data domain DD890.
 
Now we have to migrate all the backups from old master server to the new master server.
 
 
I have following questions
 
Is it possible to migrate netbackup from one hardware to another ? I know the the netbackup master serve name has to be the same but can it have a differnet IP  ???
 
I was thinking first upgrading the exisisting server to 7.5 and connect it to data domain and move all the backups to data domain storage units and then migrate to new hardware. Is this the right approach or is there a better approach.??
 
 
Please guide many of you might have upgraded from 6.5. Please through ideas.
 
 
Anurag


An timpeallacht? - Smaoinigh air sula bpriontáileann tú an r-phost seo. Please consider the Environment before printing this email. * ** *** ** * ** *** ** * ** *** ** * Tá an t-eolas sa ríomhphost seo agus in aon chomhad a ghabhann leis rúnda agus ceaptha le haghaidh úsáide an té nó an aonáin ar seoladh chuige iad agus na húsáide sin amháin. Is tuairimí nó dearcthaí an údair amháin aon tuairimí nó dearcthaí ann, agus ní gá gurb ionann iad agus tuairimí nó dearcthaí ESB. Má bhfuair tú an ríomhphost seo trí earráid, ar mhiste leat é sin a chur in iúl don seoltóir. Scanann ESB ríomhphoist agus ceangaltáin le haghaidh víreas, ach ní ráthaíonn sé go bhfuil ceachtar díobh saor ó víreas agus ní glacann dliteanas ar bith as aon damáiste de dhroim víreas. Cláraithe an Chomhlachta: http://www.esb.ie/companies This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. Any views or opinions presented are solely those of the author, and do not necessarily represent those of ESB. If you have received this email in error please notify the sender. Although ESB scans e-mail and attachments for viruses, it does not guarantee that either is virus-free or accepts no liability for any damage sustained as a result of viruses. Company Registration Information: http://www.esb.ie/companies * ** *** ** * ** *** ** * ** *** ** *
_______________________________________________ Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<Prev in Thread] Current Thread [Next in Thread>