Re: [Veritas-bu] Master server upgrade

I have done something similar several times in our environment for either lease 
returns or to perform a "fail safe" upgrade.  What we have done is as follows...

1. Build out the replacement server as close to the original
2. Present a LUN to the old server and copy /usr/openv to the new LUN
3. Stop all services on the old server when it's time to cut over
4. Run a last sync of the copy to the new /usr/openv LUN
5. Move the new LUN to the new server
6. Shut down the old Master
7. Rename/reIP new master to old masters name/IP
8. Perform install and upgrade of NetBackup on new master
9. Test, test, test

If everything worked well you are on your new server, if there is a problem, 
you take the new server off the network, and power back on your old server and 
troubleshoot with the original catalog untouched...that's just how I do it so 
that I have safe upgrades or server migrations.  

Chris Alley, MCSE
Sr. Data Protection Administrator
Kforce Technology Services
813-552-1388
www.kforce.com

Great People = Great Results®                                       



Confidentiality Notice: This email message, including any attachments, is for 
the sole use of the intended recipient(s) and may contain confidential and/or 
privileged information.  Any unauthorized review, use, disclosure or 
distribution is prohibited.  If you are not the intended recipient, please 
contact the sender by reply email and destroy all copies of the original.


-----Original Message-----
From: veritas-bu-bounces AT mailman.eng.auburn DOT edu 
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Justin 
Piszcz
Sent: Friday, August 13, 2010 3:07 PM
To: Rusty.Major AT sungard DOT com
Cc: veritas-bu AT mailman.eng.auburn DOT edu; veritas-bu-bounces AT 
mailman.eng.auburn DOT edu
Subject: Re: [Veritas-bu] Master server upgrade

Hi,

I did this in the past and got bitten a little bit, a couple of the FIBER HBA's 
were legacy and were not supported in Solaris 10, make sure your hardawre will 
be supported in Solaris 10.

Probably not a problem for a T5120 but definitely an issue for an old V440.

Justin.

On Fri, 13 Aug 2010, Rusty.Major AT sungard DOT com wrote:

> This is a basic list of what I've done this in the past:
>
> 1) Configure new server to match your old server as much as possible 
> and where applicable (interface configuration, filesystems, NBU patch 
> level, tape config, etc.).
> 2) Shut down NBU on original
> 3) Tar up the entire /usr/openv directory
> 4) Copy tarball over to new server
> 5) Untar on new server
> 6) Swap the hostname and IP so that the new server is the same name 
> (this is a requirement to keept NBU working properly)
>
> The tar of the entire /usr/openv directory will capture all your 
> config files, settings, scripts, etc. Installing and patching NBU to 
> the new server will ensure that everything will function properly when 
> you untar it. I've done this on several NBU servers with success. Most 
> were going from Solaris 9 to 10, but one or two were Solaris 8 and the 
> process didn't seem to be any different. This takes us most of the day 
> to get this completed, but NBU will need to be down anyway to ensure 
> everything is in sync. You could even mirror/rsync the filesystem to 
> the new server or if you have /usr/openv on external storage you swing 
> it over to the new server when that is ready. Regardless of your 
> solution to this problem, if you don't have much experience with the 
> chosen method, I would highly recommend doing this in a test/lab 
> configuration first and prepare a list of steps.
>
> Rusty Major, MCSE, BCFP, VCS ? Sr. Storage Engineer ? SunGard 
> Availability Services ? 757 N. Eldridge Suite 200, Houston TX 77079 ?
> 281-584-4693
> Keeping People and Information Connected® ?
> http://availability.sungard.com/
> P Think before you print
> CONFIDENTIALITY:  This e-mail (including any attachments) may contain 
> confidential, proprietary and privileged information, and unauthorized 
> disclosure or use is prohibited.  If you received this e-mail in 
> error, please notify the sender and delete this e-mail from your system.
>
>
>
> Victor Engle <victor.engle AT gmail DOT com>
> Sent by: <veritas-bu-bounces AT mailman.eng.auburn DOT edu>
> 08/13/2010 12:36 PM
>
> To
> veritas-bu AT mailman.eng.auburn DOT edu
> cc
>
> Subject
> [Veritas-bu] Master server upgrade
>
>
>
>
>
>
> List,
>
> I'm planning a Netbackup server upgrade from Solaris 8 sparc to 
> Solaris 10 on CMT (T5120) and I wondered if anyone might have a check 
> list or plan that might have been used to do a similar upgrade? The 
> master is the only server in the environment.
>
> At a high level I know I need to do the following...
>
> 1. Install the solaris 10 system and get netbackup installed on the 
> new system.
> 2. Stop netbackup on the old server.
> 3. Restore the catalog to the new server 4. Configure Storage Units on 
> the new server.
>
> Questions:
>
> 1. How are the licenses moved from the old server to the new server?
> 2. Does the catalog restore include the policies or are they restored 
> some other way?
> 3. What are the gotchas I might try to avoid?
>
> Thanks for any experiences you might be willing to share.
> Vic
> _______________________________________________
> 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