In a standard NVSD installation, the NVSD software binaries are installed on a volume that is separate from the NVSD Storage Pools. Reinstalling the NVSD software binaries is required in one of the following scenarios:
* NVSD is inoperable because a media failure occurred on the volume where the NVSD software binaries are installed.
* The OS of the machine where the NVSD Instance is running has become corrupted.
* NVSD was removed from a Windows or Solaris machine. During the uninstall, the software binaries were removed, but the data stored in the NVSD Storage Pools was left intact.
* NVSD was removed from a Linux or Mac OS X machine. Before the software binaries were uninstalled, the data in the NVSD Storage Pools was preserved as described in Preserving Data Before Removing NVSD (see below).
In the preceding scenarios, the data in the NVSD Storage Pools is still intact and can be used by a new installation of the NVSD software binaries. Each NVSD installation of the software binaries creates a unique identity that is referenced in the NVSD Content Index and the NVBU savesets; therefore, it is critical that you use the following procedures to ensure that the new NVSD installation of the software binaries points to the original NVSD Storage Pools. Failure to follow these steps will render NVSD unable to read or restore from the original NVSD Storage Pools.
Preserving Data Before Removing NVSD:
When you remove NVSD from a Windows or Solaris system, the data in the Staging Store and the Chunk Store is retained after removal of the NVSD software binaries.
For all other Linux- and UNIX-based systems and Mac OS X, the data in the Staging Store and the Chunk Store is deleted if the default directory was used during installation. If you want to retain the data in the Staging Store and the Chunk Store after you remove the NVSD software binaries, you must move the Staging Store and the Chunk Store to a secure location before removing the NVSD software binaries.
If you specified a different file-system path during installation (that is, you did not use the defaults), the data in the Staging Store and the Chunk Store is retained after removal of the NVSD software binaries.
Prerequisites for Reinstalling NVSD
Ensure that the following prerequisites are met before reinstalling the NVSD software binaries.
* All the original Storage Pool directories, which include the directories for the Content Index, Staging Store, Chunk Index, and Chunk Store, are available in their entirety and are not corrupted.
* All the original Storage Pool directories have been moved or copied to a
different directory via OS commands.
* All the original Storage Pool directories, which are now empty, are available for the new NVSD software binary installation and there is sufficient available disk space to store all the data that originally resided in these directories.
* The original "identity.cfg" configuration file is available. This file is located in the following directory:
* For Linux, UNIX, or Mac OS X:
.../diskmanager/etc
* For Windows:
...\diskmanager\etc
***Reinstalling NVSD if identity.cfg IS Available***
If the original "identity.cfg" configuration file is available, reinstall the NVSD software binaries by performing the following steps:
1. Ensure that the NVSD non-privileged user account has full access to the original NVSD Storage Pool directories.
2. Install the same version of the NVSD software that was originally running. During the installation, make sure that you enter the original values for the following options:
- Non-privileged User Account
- Staging Path Folder or Staging Store Directory
- Store Path Folder or Chunk Store Directory
3. Update the NVSD Configuration to ensure that the directory structure for the Content Index, Staging Store, Chunk Index, and Chunk Store matches the original NVSD installation.
4. Stop the NVSD Services.
5. Replace the "identity.cfg" file with the original file.
This file is located is located in the following directory:
- For Linux, UNIX, or Mac OS X:
.../diskmanager/etc
- For Windows:
...\diskmanager\etc
6. Use OS commands to copy the contents of the original Storage Pool
directories, which were moved to a different directory, back to the original
corresponding directories.
7. Start the NVSD Services.
8. If a media failure occurred on the volume where the NVBU Server software binaries are installed, thus rendering NVBU Server inoperable, reinstall NVBU with the identical NVBU Machine Name.
For more information, refer to the NetVault: Backup Installation Guide.
9. If the original NVBU installation is still operational, use the NVBU Console toremove the corresponding NVSD Device from the Device Management window by using the Force Removal option.
This changes the device-status indicator for the NVSD Device to Offline. For more information, refer to the NetVault: Backup Administrator's Guide.
10.In the NVBU Console, use the Device Management window to add the new NVSD Instance to NVBU.
For more information, refer to the NetVault: Backup Administrator's Guide.
11. In the NVBU Console, right-click the NVSD Device on the Devices tab, and select Scan.
Scanning an NVSD Device queries all the backups stored on the NVSD Device and makes them available for restores. For more information, refer to the NetVault: Backup Administrator's Guide.
****Reinstalling NVSD if identity.cfg is NOT Available****
If the original "identity.cfg" configuration file is not available, reinstall the NVSD software binaries by performing the following steps:
1. Ensure that the NVSD non-privileged user account has full access to the original NVSD Storage Pool directories.
2. Install the same version of the NVSD software that was originally running. During the installation, make sure that you enter the original values for the following options:
- Non-privileged User Account
- Staging Path Folder or Staging Store Directory
- Store Path Folder or Chunk Store Directory
3. Update the NVSD Configuration to ensure that the directory structure for the Content Index, Staging Store, Chunk Index, and Chunk Store matches the original NVSD installation.
4. Stop the NVSD Services.
5. Use OS commands to copy the contents of the original Storage Pool
directories, which were moved to a different directory, back to the original
corresponding directories.
6. Start the NVSD Services.
7. If a media failure occurred on the volume where the NVBU Server software binaries are installed, thus rendering NVBU Server inoperable, reinstall NVBU with the identical NVBU Machine Name.
8. If the original NVBU installation is still operational, use the NVBU Console to remove the corresponding NVSD Device from the Device Management window by using the Force Removal option.
This changes the device-status indicator for the NVSD Device to Offline.
9. In the NVBU Console, use the Device Management window to add the new NVSD Instance to NVBU.
10.In the NVBU Console, right-click the NVSD Device on the Devices tab, and select Scan.
Scanning an NVSD Device queries all the backups stored on the NVSD
Device and makes them available for restores.
11.Stop the NVBU Service.
12.Stop the NVSD Services.
13.In the NVBU Command Line Interface (CLI), run the NVDB Checker using the nvmeddbcheck list command. See KB 4411 or the NetVault Command Line Interface (CLI) Reference guide for futher instructions.
14.Use the NVDB Checker output to identify the NVSD identity.
For example, if the output from the NVDB Checker includes an error similar
to:
Failed to locate RAS device object for Mid
770400003a9a164b225fada7380e000001000000
it indicates that the NVSD identity is
770400003a9a164b225fada7380e000001000000.
15.Edit the “identity.cfg" file to replace the current value for the Identity field
with the one displayed in the NVDB Checker output.
This file is located is located in the following directory:
-For Linux, UNIX, or Mac OS X:
.../diskmanager/etc
- For Windows:
...\diskmanager\etc
16.Start the NVSD Services.
17.Start the NVBU Service.
18.Use the NVBU Console to remove the original corresponding NVSD Device from the Device Management window by using the Force Removal option.
This changes the device-status indicator for the NVSD Device to Offline.
19.In the NVBU Console, right-click the NVSD Device on the Devices tab, and select Force Add to add the new NVSD Instance to NVBU.
20.In the NVBU Console, right-click the NVSD Device on the Devices tab, and select Scan. Scanning an NVSD Device queries all the backups stored on the NVSD Device and makes them available for restores.
BakBone SFDC Solution Number: 00005641
