Hi Erin,

Just did an upgrade a few weeks ago 5.5.X to 7.0 and 6.0.x to 7.1.

No real problems, just a reminder. If you have large index databases 
take a book with you. The coversion will take hours.

Copied my short installation notes below.

Upgrade 7.1


-1- Enable license upgrade.

# nsrcap -v -c enablercode  

-2- Close Networker daemons. 

# nsr_shutdown

-3- backup /nsr filesystem

# cd /nsr
# tar cvf /free_filesystem/nsr.tar .

-4- Remove old packages

# pkgrm SUNWsbuc
# pkgrm SUNWsbum
# pkgrm SUNWsbun
# pkgrm SUNWsbus1
# pkgrm SUNWsbus2

-5- Check if patches are removed.

# showrev -p | grep 108884

Version 5.5.1 108884
Version 6.0.1 111962

-6- Install new packages

# share /cdrom/ebs_vol1
# mount -o soft,bg jr1:/cdrom/ebs_vol1 /cdrom
# cd /cdrom/Solaris/Sparc
# pkadd -d .

Answer all to question which package to install.

SUNWebsc
SUNWebsd
SUNWebsm
SUNWebsn
SUNWebss

Answer No to "should Networker startup after install".

-7- Start the Networker Daemons 

# /etc/init.d/networker start 

Networker will now rebuild the index and media database. This could take
a few hours.

Good luck,

Robert-Jan

 

-----Oorspronkelijk bericht-----
Van: Davina Treiber [mailto:Treiber AT HOTPOP DOT COM] 
Verzonden: donderdag 8 april 2004 8:34
Aan: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Onderwerp: Re: [Networker] upgrade 6.0.1 -> 7.0


Erin S. Voss wrote:
> We are going to be upgrading our Networker (Sun-flavored, "Enterprise 
> Backup
> Solution") installation from 6.0.1 to 7.0 next week.  Our server is
running
> Solaris 8, and we've already got the auth code for the upgrade
license.
>
> The documentation provided by Sun makes it seem like the upgrade is 
> very straightforward.
> 1) back up your backup server and write down important info (like 
> bootstrap locations)
> 2) remove the old software package
> 3) install the new package
> 4) allow resource files to be converted
>
> If others have done similar upgrades, are there other things you would

> recommend doing?  Any problems you encountered?
>
> Any advice would be appreciated.

The process looks correct, nothing more complex is required.

Why are you going to 7.0? It's getting quite old now, and 7.1.1 has many
more bugfixes.

The way I understand it, Legato has different teams working on different
code trees. I believe that 7.0 evolved from 6.2, whereas 7.1 evolved
from 6.1. IMHO 6.1 was more mature than 6.2. It seems also that just
because a bugfix goes into one tree it doesn't necessarily go into the
other.

--
Note: To sign off this list, send a "signoff networker" command via
email to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can also
view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=


================================================================================
PGGM heeft aan het opstellen en verzenden van dit E-mail bericht de nodige zorg 
besteed. Desondanks is het mogelijk dat dit bericht onvolledig is, onjuistheden 
bevat, niet voor u is bestemd of te laat wordt ontvangen. PGGM aanvaardt 
daarvoor geen enkele aansprakelijkheid.
De informatie verzonden met dit E-mail bericht is uitsluitend bestemd voor de 
geadresseerde. Gebruik van deze informatie door anderen dan de geadresseerde is 
verboden. Openbaarmaking, vermenigvuldiging, verspreiding en/of verstrekking 
van deze informatie aan derden is niet toegestaan. Indien u niet de beoogde 
ontvanger van dit bericht bent, gelieve u de afzender per omgaande van de 
onjuiste adressering/ontvangst op de hoogte te stellen en dit bericht, met 
inbegrip van eventuele bijlagen, uit uw systeem te wissen.
PGGM staat er niet voor in dat dit bericht en/of bijlage(n) op generlei wijze 
schade kan veroorzaken, hoegenaamd ook, en aanvaardt daarvoor geen enkele 
aansprakelijkheid.
================================================================================
PGGM has taken all reasonable care by the editing and the sending of this 
E-mail message. Nevertheless it might happen that this communication is 
incomplete or incorrect, that you are not the intended recipient or that this 
message will be received late. PGGM does not accept any liability for this.
The information contained in this communication is strictly confidential and 
may be legally privileged. It is intended solely for the use of the individual 
or entity to whom it is addressed and others authorised to receive it. If you 
are not the intended recipient you are hereby notified that any disclosure, 
copying,  distribution or taking any action in reliance on the contents of this 
information is strictly prohibited and may be unlawful. If you are not the 
intended recipient of this message, you are requested to inform the sender by 
return of the incorrect address/receipt and to delete it from your system, 
including the attachments, if any.
PGGM does no warrant that this message and/or any attachment can in any way not 
cause any damage at all and does not accept any liability for such circumstance.
================================================================================

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=