In this case I would agree, considering you are on a windows platform.
If you were on AIX or HPUX, I would not upgrade to 7.3.3 as it will
only be supported until Dec 31 2007 and 7.2.2 is supported until June
30 2008. I have no idea as to why EMC did it this way, but that is
what is listed in the ending releases on powerlink.
I think we'll wait for 7.4.1 (the 7.4 upgrade was a dismal failure) or
move to Solaris on SPARC and 7.3.3 ;-)
Ken
On Nov 21, 2007 7:18 AM, Fazil Saiyed <Fazil.Saiyed AT anixter DOT com> wrote:
> Hello,
> Seems like an ideal opportunity to upgrade to 7.3.3 platform, besides
> following the steps in DR guide, one approach that is quite simple and
> works fine is as follows. ( Not something that would be recommended by
> some folks or emc but nevertheless works just as well). I still recommend
> full backups of old server with Full index backup also for any event of
> failover, issues.
> 1. copy old nsr directory to new server, after you shut down all
> networker services on original server.
> 2. Shut down old server, remove from domain, keep it off the network etc.
> 3. Rename the new server name to old and move it to domain, match IP
> properties, nslookup, etc.
> 4. Install new networker version on top of old nsr directory, which you
> copied in step 1 ( any location you like on the server)
> 5. You will have to be careful about how you specified original index in
> the client attributes, if it calls for D:\nsr\index then that's where you
> should do initial install, if you did not specify index directory in
> client attribute, moving it to C should not be a problem.
> 6. Start networker services, resync the hardware, you may have to redo
> jbconfig, since the drivers etc would have changed
> 7. Move your host file, double check your config etc ( along with step
> one)
> You should be up and running at this point, i believe this approach could
> work well even for DR if the nsr directory is replicated with proper care,
> this approach is similar to upgrading networker on the same server, no
> need for mmrecov, nsrck etc, however as always , once the server is
> successfully moved to new hardware you should run the index check & run
> the full backup, test recover etc asap.
> I am sure some folks would not like bypassing normal networker dr
> routine, so get a second opinions and test it out.
> HTH
>
>
> 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
>
--
They that can give up essential liberty to obtain a little
temporary safety deserve neither liberty nor safety.
--Benjamin Franklin
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
|
