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.
You need to be signed in and under a current maintenance contract to view premium knowledge articles.