Migration of a NetVault:Backup server from one machine to another can be performed, however the following pre-requisites conditions must be met.
Pre-requisites:
If you intend to do a cross-platform migration please contact Technical support PRIOR to making the change for advice. For Cross-platform migrations, certain procedures must be followed.
The original and target machines should be running on the same platform - e.g. both running on Windows-based operating systems or both on Linux-based operating systems.
The original and target NetVault Backup servers MUST have the SAME version of NetVault Backup installed, e.g. 11.x
1) Perform a backup of the original server’s NetVault database using the NetVault Database plugin.
2) Install NetVault onto the target machine as server making sure it has the same NetVault name as the previous server and the same version. If there are any NetVault client versions present on the target machine then uninstall those first. The pre-requisite conditions mentioned above must be met during the install, or NetVault will not function correctly.
3) Add the device to the target NetVault server from the Manage Devices WebUI
4) If tape: load and import the tape containing the backup taken in step 1. Once read, the tape will show up as "foreign" on the new server. Select the tape and "scan" it.
If disk device (like DR, QoreStore) after adding scan the container.
5) Open the Create Restore WebUI window and locate the backup session imported in step 4.
6) Select all fields excluding Keys (you can exclude Logs if needed a faster migration) then press next.
7) Note that "Keys" should not be selected when doing a migration, as keys are machine locked and will not be valid on the new server. Make sure that you are selecting the new server in the target client.
8) NetVault Database restore will close the WebUI session (please do not login again), in order to monitor the restore monitor the nv* processes, when they are gone the restore has completed and you need to start NetVault services.
9)Remove and re-add the devices in Manage Devices window. This is required because the Media Manager database restore will have overwritten the device entries added in step 3 with those of the original server, which are likely not connected to the new server or need a connection refresh.
10) If necessary, re-add missing clients in Manage Client WebUI window.
If the NetVault machine ID has changed, then you will have to change your NetVault Server license key over.
You can now manage your license keys yourself by navigating to the following site; https://support.quest.com/my-account/licensing, register the Server License Number if it hasn't been registered, and transfer license from Retrieve Key tab.
You can also request new keys or get licensing assistance from the following URL:
https://support.quest.com/licensing-assistance
If the machine id is the same as the original server, you can apply your original license keys.
WARNING: Do not keep the old NetVault server running after migrating. Having two servers with the same NetVault name running will cause many communication problems. If you need to keep the NetVault server running as a client, remove the NetVault server installation and install the NetVault client software. You can then specify a different NetVault name during the installation or use the nvclientname utility to change the name of the client after the installation.
