NetVault 13.1.2 - Installation Guide


	NOTE: While upgrading from NetVault Backup 12.3 to NetVault 13.1.2, you may face authentication issues at few places while performing various operations. This is due to a change in the algorithm from NetVault Backup 12.3 to NetVault 13.1.2. For more information, see Upgrading from NetVault Backup 12.3.


	IMPORTANT: NetVault Backup is now NetVault. With this name change comes a new license format. Instead of a license key, NetVault uses license files in the .dlv format that install on the NetVault Server machine. If you use a NetVault Client or licensed plug-in that is older than version 13.0, then you must obtain a license file to install on the NetVault Server, in addition to the old license located on Client or plug-in machine. For more information, see the related KB on the Support Portal.

Before you upgrade your NetVault system, review the following notes:

•

Go to My Account at www.quest.com, download the .dlv license files for NetVault Client and all licensed plug-ins used in your configuration, and then save the files to your current NetVault Backup Server’s \tmp folder.


	CAUTION: It is very important to copy all necessary license files to the \tmp folder of your NetVault Backup Server before you upgrade. f the installer does not find any .dlv license files in NetVault Backup Server's \tmp folder during upgrade, it installs the default 30-days trial license for NetVault. If you are using features and plug-ins not included or allowed or allowed under a trial license, the installation could cause unexpected changes in your NetVault configuration and failed backup jobs. To install the license files after an upgrade, go to the License Management page in the WebUI. Release Notes.

•

When you perform an upgrade, select the server or client version based on the current installation type.

•

Upgrade the NetVault Server before upgrading any client system.

•

If you have the NetVault Client installed on an HP-UX or macOS operating system, Quest recommends that you use a fresh install of NetVault 13.1 rather than upgrade from an older version.

•

A NetVault Server can only support clients of the same version as itself or older. The NetVault Client software version cannot be higher than the NetVault Server software version.

•

Starting with 10.0, the NetVault Server installation is only supported on Windows and Linux operating systems. You can no longer install the NetVault Server on UNIX and Mac OS X operating systems.

For information about supported operating system versions, see the Quest NetVault Compatibility Guide available at https://support.quest.com/technical-documents.

•

Upgrade to NetVault 13.1.2 is only supported from NetVault 11.4.5 and later.

•

When you upgrade NetVault on Linux-based systems, it removes all start and stop links to the netvault init script before resetting them to the runlevels of the new version. If you want to retain any user-defined links to the init script after an upgrade, do not use the word “netvault” in the link name.

•

To simultaneously upgrade the NetVault Client software on multiple machines, you can use the push installation method of NetVault WebUI. You can use this method for both new and upgrade installations. For more information about this method, see the Quest NetVault Administrator's Guide.

•

During upgrade, the language must be the same as the original language when NetVault was first installed. If the language during upgrade differs from the original language, the default administrator account will not migrate successfully and the NetVault instance may get locked.

•

Before upgrading NetVault, you must upgrade the attached DR appliance to version 4.0.3 or later.

•

If an external installation of RDA version 3.2 is present, either remove it or upgrade it to the RDA version 4.0.3041.0 or later.

•

All the DR devices that were attached to the previous version NetVault, must be reachable and online during the upgrade process.

•

DR devices that are either not reachable or running on DR OS version less than 4.0.3 are grouped under Orphan Devices. Remove these devices first and then re-add to NetVault after the upgrade.

•

To ensure the smooth operation of NetVault, after upgrading NetVault to version 13.1.2, you must clear the browser cache.

•

When you upgrade NetVault Server, NetVault requires that you log in with the same user account that you used for installing the previous version of the NetVault, and run the setup. The upgrade fails if you upgrade NetVault using a different user account.

•

There is an expected latency of a few minutes to load NetVault WebUI pages such as Dashboard, View Reports, and Create Backup Job, immediately after NetVault installation or upgrade.

Upgrading from NetVault Backup 12.3

Due to a change in the encryption and decryption algorithm in NetVault Backup 12.3, you may experience authentication-related issues after upgrading from NetVault Backup 12.3.0.15 to NetVault 13.1.2.

See the following table for known issues and their possible workarounds.

Table 1. Authentication error workarounds
Impacted Area	Resolution
If “Bulk Blank” for Tape Library or Virtual Tape Library (VTL) fails with an authentication error...	Reset the password using the same existing password. For more information, see “Changing NetVault password” in the NetVault 13.1.2 Administration Guide.
If “Expire All” for DR fails with an authentication error...	Reset the password using the same existing. For more information, see “Changing NetVault password” in the NetVault 13.1.2 Administration Guide.
If backups are not cataloged after an upgrade...	Reconfigure catalog search with the same existing password. For more information, see “Configuring catalog search” in the NetVault 13.1.2 Administration Guide.
If CLI utilities fails with an authentication error...	Reset the password of the NetVault user that you used for CLI using the same existing password. For more information, see “Modifying a user account” in the NetVault 13.1.2 Administration Guide.
If VMware backups or restores fail with an authentication error in the logs...	Reset the password for vCenter or ESX Server using the Edit Server dialog box. For more information, see “Reconfiguring a server” in the NetVault Plug-in for VMware 12.3 User’s Guide.

If you experience authentication issues in other areas of NetVault, reconfigure the password and perform the action again. If the issue continues, contact NetVault Support.

Preparing for an upgrade

•

Back up the NetVault Database: The first step in preparing for an upgrade of NetVault Server is to perform a backup of the existing NetVault Database. If an upgrade is unsuccessful, you can reinstall the previous version of NetVault and recover the NetVault Database to enable troubleshooting of the failed upgrade without interfering with an existing backup schedule.

For more information about backing up the NetVault Database with the Plug-in for Databases, see Quest NetVault Built-in Plug-ins User’s Guide.

When you restore data from the NetVault Database, the logs are restored to the directory logs_restored_<YYYYMMDD>.

•

Collect machine IDs: When upgrading from release 12.4 or earlier, collect the machine ID of each protected machine. NetVault machine IDs are required to obtain the new license files. If you have a Capacity license, then only your NetVault Server machine ID is required. If you have a Component license, then you need the machine IDs of all Clients machines with licensed plug-ins.

•

Download license files: When upgrading from release 12.4 or earlier, download the .dlv license files for NetVault Server and all licensed plug-ins used in your configuration, and then save the files to your current NetVault Backup Server’s \tmp folder.


	CAUTION: It is very important to copy all necessary license files to the \tmp folder of your NetVault Backup Server before you upgrade. f the installer does not find any .dlv license files in NetVault Backup Server's \tmp folder during upgrade, it installs the default 30-days trial license for NetVault. If you are using features and plug-ins not included or allowed or allowed under a trial license, the installation could cause unexpected changes in your NetVault configuration and failed backup jobs. To install the license files after an upgrade, go to the License Management page in the WebUI. Release Notes.

•

Close all other NetVault applications: Before starting the upgrade procedure, close all other NetVault applications, such as NetVault Configurator, Workstation Client, and PostgreSQL pgAdmin. If you have opened any configuration file, make sure that the file is closed before you start the upgrade procedure. On Windows, it may also be necessary to close Event Viewer before performing an upgrade. On Windows, close all the command prompts where any of the NetVault directories are browsed.

•

Disable anti-virus software: We recommend that you disable the anti-virus software before installing or upgrading NetVault. The installation process may conflict with the anti-virus software and various NetVault operations may fail to function properly after the installation if you do not disable the anti-virus software.

Upgrading NetVault in GUI mode

The graphical mode is available on all supported operating systems that provide a graphical environment. This mode requires GTK packages or X Window System libraries on Linux- and UNIX-based systems.

To upgrade NetVault Server or Client in graphical mode:

Log on to the system with administrator or root-level access, and navigate to the directory in which the installation file resides.

Double-click the installation file.

In the Language Selection dialog box, select the language to be used in the upgraded installation. Click OK.


	NOTE: By default, in the Language Selection dialog box, the language of an existing NetVault installation is displayed and the same language is displayed for upgraded installation as well.The language must be the same as the original language when NetVault was first installed. If the language during upgrade differs from the original language, the default administrator account will not migrate successfully and the NetVault instance may get locked.