We have a Networker 7.5.1 server that we are attempting to upgrade to
7.6.1.2. When we do the upgrade, our lockboxes become inaccessible and end
up having to be recreated. This means that all the database backup jobs that
use them have to be recreated because we haven't found an easy way to
convince the backup jobs to use the new lockboxes.

The procedure we are using to upgrade is to make a backup of all of the
bootstrap and index information, uninstall the 7.5.1 rpms and then install
the 7.6.1.2 rpms and put all the bootstrap/index information back. The
server is running on Red Hat Linux 5.5 and the NMC is running on Windows.
Storage nodes are Red Hat Linux 5.4. Should we perhaps be doing this
differently? Has anyone else had this issue? We've stumped EMC, it seems.

Possibly related - when we upgraded the operating system last fall, we lost
our lockboxes then as well. We didn't touch Networker directly, but it
somehow corrupted all the lockboxes and everything had to be recreated.

Thanks,
Kate McDonald

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