Just want to share my experience doing this upgrade.

Networker server 7.4.4 to 7.5.1. Server 2003 standard 32bit backing up to an 
EDL 4200 with 6 storage nodes. Distributed environment (complex firewall 
setting)

I used the procedure generator. And also read through some install/upgrade 
documentation. The procedure generator had it all. 

Upgrading Networker is simple. I did an uninstall and kept the DB. Then I ran 
an install. The install upgraded the GST server as well.

After the upgrade I logged on to the management console and everything looked 
fine. But few minutes later the server (not the operatin system) stopped 
responding. I could not issue a simple command line like nsrlic, it just hang. 
I gave it about 1 hour, and then it was fine. 

We were able to start backups imediadely when networker started to respond 
again. We see no new problems with backups after the upgrade. 

We have some minor issues though. 

-GST doesn't start automaticall after reboot.

-Management console, if left standing shows obsolete info, and needs to be 
refreshed by restarted by exit out and open again.

That's all we know about, and this upgrade was performed 2 days ago.

Kind regards,
Johannes



-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Craig Faller
Sent: 10. júní 2009 12:46
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Networker upgrade 7.4.4 - 7.5.1

With every version there have been a small percentage of environments where it 
has all gone pearshaped or they have run into bugs which havent caused issues 
for the majority, we've upgraded numerous customers to 751 without any 
unforeseen issues ( a few licensing issues, rhel5 udev problems, etc).  I would 
suggest you install this version on a Proof-of-concept system in your 
environment and put it through its paces, this way you can determine if its a 
feasable direction and or what issues may occur and they can be addressed prior 
to moving forwards.
 
or just wait for 7.5.2, but again you still wont know how it will perform in 
your environment.

________________________________

From: EMC NetWorker discussion on behalf of Joe N. Wallace
Sent: Wed 10/06/2009 7:26 AM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Networker upgrade 7.4.4 - 7.5.1



My understanding from this discussion here is that the 7.5.1 version is a
no-go.

-Problem with the ports

-problem with shortname/FQDN

-GUI problem
>From this discussion it also seems EMC is not doing anything about this. Is
there no explanation?

Why did they release the sp 1 if it's just crap?

Wallace
2009/6/10 Robert Brault <RBrault AT edfinancial DOT com>

> Problem #1:
>
> I have had issues with refreshing of the application. If I leave the app
> open on a remote desktop session and then come back the next day my
> screen does not update for gui. I have to then close down the app and
> re-open it for the gui to have the new information.
>
> Problem #2:
>
> When I first installed networker it was already attached to the domain
> so the client name was called networker.domain.name. After installing
> the latest 7.5.1 it change my client name to just networker. I had to
> change my NDMP jobs to match the new name.
>
> Problem #3: Separate yet equally important issue.
>
> I upgraded to the latest version so that I could have a Server 2008 box
> as a storage node. This worked. But, I have since found that snapimage
> is not supported on for server 2008. They stated that they do not see
> supporting it in the future neither.
>
> -Robert
>  -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> On
> Behalf Of Yaron Zabary
> Sent: Tuesday, June 09, 2009 4:27 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Networker upgrade 7.4.4 - 7.5.1
>
> JKK wrote:
> > Hi.
> >
> > I'm planning an networker ugrade from 7.4.4 to 7.5.1 in our
> distributed
> > environment consisting of 5 storage nodes and some 500 clients. We're
> using
> > single data zone.
> >
> > Acoring to documentation this is pretty easy.
> > it's recomended to run these commands
> > nsrim -X
> > nsrck -m
> > nsrck -L6
>
>   With 500 clients, this nsrck can take more than a day. This is a
> quote from a letter I sent to this forum on November 18th, 2008:
>
> "   If you need to run to run nsrck -L6, I suggest that you will do that
>
> in parallel. I use the following script (on Solaris) to get things to
> run faster:
>
> #!/bin/sh
>
> cd /nsr/index
> CLIENTS=`du -sk * | sort -nr | awk '{print $2}'`
>
> for client in $CLIENTS
> do
> echo $client
> at -s -qd now<<EOB
> time nsrck -L6 $client
> EOB
> sleep 1
> done
>
>   You need to add the third line to queuedefs for the above to work. It
>
> runs 20 jobs (on a 24 threads T1000). Since this process is CPU bound
> there is no point in doing much more than your processors (say five for
> your typical quad core Intel CPU).
>
> # cat /etc/cron.d/queuedefs
> a.4j1n
> b.10j2n90w
> d.20j4n60w
>
>   With the above I was able to check 70Gb of index which took over 22
> hours in under four hours."
>
>
> >
> > upgrade the storage nodes first. After that,it's pretty much
> next-next-
> > finish.
> >
> > Is anyone out there with experience doing an 7.5.1 upgrade? any
> issues? and
> > how where the issues resolved?
>
>   Last time I spoke with GlassHouse, they said that this upgrade is not
>
> recommended and that I should stay at 7.4.4. I am, however, dissatisfied
>
> with 7.4.4 which I why I wanted to upgrade. If you want to upgrade
> because of stability, I think 7.4.4.4 might be a better option (if you
> can get it). I will give a call to GH and see if I can get it from them.
>
> >
> > Johannes
> >
> > 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
>
>
> --
>
> -- Yaron.
>
> 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
>
> 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
>

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

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

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