In order for your older Backup file indexes and media database to be compatible with the new indexes created with newer releases of Backup, they must first be converted.
Although the indexes are automatically converted the first time you start the Backup daemons, do not use the automatic conversion when you update from older releases. Instead, the following procedure is more efficient:
In order for your older Backup indexes to be compatible with the new indexes created with this release of Backup, an automatic conversion process is invoked during installation of the software. This conversion process may, in some instances, cause corruption of your index files.
The conversion process is lengthier than a straightforward conversion from the 4.2 release, since the indexes must first go through a process to convert them to 4.2 compatibility before final conversion to this release.
If you are updating your Backup software from a release prior to 4.2, you may choose to avoid the longer index conversion process that is required to bring your indexes up to be compatible to this release. To bypass the automatic index conversion that takes place when you install the Backup software, we recommend that you follow this procedure:
Before you install the Backup software, make sure that you have a recent, full backup of the file indexes (/nsr/index) and media database (/nsr/mm) available.
Issue the nsr_shutdown command at the shell prompt.
Delete the /nsr/mm and /nsr/index directories on the Backup server.
Remove the earlier version of Backup, using the instructions that were included with the software.
Install the new release of the Backup software.
The Backup daemons are typically restarted by default when the installation process is completed. If you do not automatically restart the daemons after installation, you must restart them manually before you proceed to the next step. To restart the daemons manually, enter nsrd and nsrexecd at the shell prompt.
Use the mmrecov program to recover the 4.1.x version of the server index and media database.
See "How to Recover the Server Index and Media Database" for information on how to use the mmrecov program.
After you recover the server's 4.1.x version of the server index and media database, you can recover the remainder of the server data that includes the 4.1.x version of the client indexes, using the nwrecover program.
In the nwrecover program, select all of the files and directories except the server index (/nsr/index/server-name by default) and media database (/nsr/mm by default), because you already recovered them with the mmrecov program. Also, do not recover the resource database directory (/nsr/res by default) because it would overwrite your new device configurations.