test

Solstice Backup 5.1 Installation and Release Notes

Updating from Earlier Releases

If you are upgrading your software, follow these instructions. If your are installing Backup for the first time, ignore these instructions.

Note -

To ensure compatibility, update both servers and clients to the same Backup release.

How to Update from Release 5.0.1

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.

The indexes are automatically converted the first time you start the Backup daemons. Before you install the Backup software:

  1. Make sure that you have a recent, full backup of the file indexes (/nsr/index), server resource files (/nsr/res), and media database (/nsr/mm).

    Caution - Caution -

    For automatic index conversion, make sure the amount of free disk space is double the size of your largest index. If you do not have enough free disk space, remove the indexes when you remove Backup, and recover and convert them according to the instructions in "How to Recover the Server Index and Media Database".

  2. Remove the earlier version of Backup (but not the indexes) using the instructions in "How to Remove the Backup Software".

  3. Install the Backup software.

    You do not need an update enabler code to update from version 5.0.1 to 5.1.

How to Update from Release 4.2.x

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.

The indexes are automatically converted the first time you start the Backup daemons. Before you install the Backup software:

  1. Make sure that you have a recent, full backup of the file indexes (/nsr/index), server resource files (/nsr/res), and media database (/nsr/mm).

    Caution - Caution -

    For automatic index conversion, make sure the amount of free disk space is double the size of your largest index. If you do not have enough free disk space, remove the indexes when you remove Backup, and recover and convert them according to the instructions in "How to Recover the Server Index and Media Database".

  2. Remove the earlier version of Backup (but not the indexes) using the instructions in "How to Remove the Backup Software".

  3. Install the Backup software.

  4. Enable and register your Backup software using the instructions in "Enabling and Registering Backup".

    You must use the enabler code that was included in the update kit.

How to Update from Release 4.1.x

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:

  1. 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.

  2. Issue the nsr_shutdown command at the shell prompt.

  3. Delete the /nsr/mm and /nsr/index directories on the Backup server.

  4. Remove the earlier version of Backup, using the instructions that were included with the software.

  5. 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.

  6. 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.

  7. 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.

How to Recover the Server Index and Media Database

With the new version of the Backup software installed, recover the 4.1.x version of the server index, media database, and configuration files from the backup media as follows:

  1. Find the bootstrap information.

    The mmrecov program asks you for the bootstrap save set identification number (ssid). If you perform regular scheduled backups that include the server, you should have a copy of the bootstrap file (either as hardcopy or an electronic file) with the name of the backup media you need and the bootstrap ssid. If you do not have this information available, you can invoke the scanner -B command at the shell prompt to obtain the bootstrap ssid.

  2. Retrieve the backup media that contains the most recent backup named bootstrap and load it into the server's backup device.

  3. Use the mmrecov command to extract the contents of the bootstrap backup.

    The mmrecov program prompts you for the bootstrap ssid, the starting file number (if known), and the starting record number (if known).

    If you have more than one backup device available, the mmrecov program also prompts you to enter the name of the device you want to use. You can press [Return] to accept any default values that Backup provides in each prompt.

    After the mmrecov program completes extraction, the following message appears:


    The on-line index for `server-name' is now fully recovered.

    You can use Backup commands such as nsrwatch or nwadmin to watch the progress of the server during the recovery of the index and configuration files. Open a new window (shell tool) to monitor the recovery so that the mmrecov output is not displayed on top of the nsrwatch output.

    Unlike the /nsr/index directory, the /nsr/res directory containing the configuration files cannot be reliably overwritten while Backup is running. Therefore, mmrecov recovers the /nsr/res directory as /nsr/res.R. Delete the /nsr/res.R file after the recovery process is completed.

    For more information about the mmrecov command and examples of its output, refer to the Solstice Backup 5.1 Disaster Recovery Guide or the mmrecov man page.