Networker

[Networker] NW 7.2->7.4 upgrade - clients...

2008-05-23 03:32:51
Subject: [Networker] NW 7.2->7.4 upgrade - clients...
From: tkimball <networker-forum AT BACKUPCENTRAL DOT COM>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Fri, 23 May 2008 03:31:14 -0400
stan wrote:
> 
> PowerLink also has a document on how to do the upgrade. Its worth a  
> read.
> 
> The process of upgrading is pretty simple, but its time consuming.
> 
> EMC recommands that before doing the update, you do the following  
> three things ...
> 
> nsrck -X
> nsrck -m
> nsrck -L6
> 
> The second command needs to be done while the system is idle because  
> it shuts down the media database. I am about to update from 7.4 SP1 to  
> 7.4 SP2. I didn't do those integrity checks when I did previous  
> updates, but when I did the first one yesterday, it ran all day. Your  
> NetWorker server will also need a lot of free disk space to go from  
> pre-7.4 to 7.4 due to the database conversion.


I'm reading this document now; Your first command should be:

nsrim -X

not 'nsrck -X' which actually emulates -L3 (and should explain why it would 
have taken almost a day to run).  The L6 could be more interesting though.  :/  
I have a weekly cron to run that nsrim command (to enforce some offsite volumes 
to recycle earlier/properly) so that should be fine with me.

Some additional comments regarding what I've read:

-> Getting constantly stonewalled regarding support of 6.x clients; This 
document says nothing (sort of), whereas the Sun EBS documents specifically say 
that no clients prior to 7.1.x will be supported.  We have compile servers 
running Solaris 2.5.1 and 2.6 that just can't be upgraded, so they need to be 
on the 6.x client; Any suggestions/clarifications would be immensely helpful 
here.

-> I'm actually happy to see that they've given warning about their database 
getting quite a bit larger; I'm curious to know what the RL experience has been 
with this (so I can see if a mirror pair of 146 gig disks are a justified 
enough upgrade from the pair of 36s and pair of 18s currently in use).

-> They're recommending a separate NMC server for environments with >50 
clients.  Experience with this is also appreciated - we can probably set aside 
hardware for this but it would need to be 'carefully chosen.' (VPN fun)

-> They've sent a warning out for AlphaStor - no surprise there, it's the 
reason we've held our upgrade for so long (still on 7.1.3 and AS 
3.0.something).  We're intending to just rip it out and continue without it, 
but if we add it again it would be done as if it were a new install - the 
existing database is hopelessly messed up from an upgrade standpoint.

--TSK

-----=====-----
Timothy Kimball, Sungard/BRASS

+----------------------------------------------------------------------
|This was sent by t.s.kimball AT gmail DOT com via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER