Veritas NetBackup™ Virtual Appliance Documentation

If you perform a factory reset on a NetBackup Virtual Appliance media server and choose to keep the existing storage, the NetBackup Virtual Appliance Shell Menu does not prompt you to reuse the existing partition when you reconfigure the appliance. After you configure the appliance, refer to the following article for a workaround:

https://www.veritas.com/docs/100017201

This issue does not apply to the NetBackup Virtual Appliance CloudCatalyst.

Version 6.0 of the vSphere Client and vSphere Web Client does not support the SHA256 hashing algorithm, which NetBackup Virtual Appliance uses. If you have vSphere version 6.0, use the OVF Tool to deploy the appliance or refer to the following article for a workaround:

https://www.veritas.com/docs/100046577

Upgrades to version 3.2 do not support ECA deployment. After a successful upgrade, you can enable the ECA for NetBackup.

For upgrades from versions 2.7.3 and 3.0 to version 3.2, all customized tuning values are reverted back to default settings. After these upgrades are completed, you must manually reapply any previously customized tuning values.

After an upgrade to software version 3.2, NetBackup CLI users may not be able to log in to the appliance. To resolve this issue, log in to the appliance as the administrator and run the following command:

Support->Service Restart nbapp-nbcli.

For appliances that use the NetBackup Auto Image Replication feature, upgrades to version 3.2 may cause these replication jobs to fail due to an issue in NetBackup version 8.2.

To resolve this issue, contact Veritas Support and ask the representative to provide you with the following EEB:

NBAPP_EEB_ET3091133_3.2.0.0-4/x86_64.rpm

If IPSec functionality is configured on any appliance that you plan to upgrade, the IPsec certificates may not be retained after the upgrade has completed. To avoid this issue, you must export the IPsec certificates before upgrading those appliances.

When you attempt to copy a software update to the share directory, do not initiate any other commands until the copy finishes. If you run a command during the copy process, you may see that the software update is listed and available. However, if you install that software update, it can fail.

If you receive an email stating "No license exists" during the initial configuration of a media server, you can safely disregard the email. The email is sent during host name configuration. The license key file is renamed when it is modified with the new host name, and the alert mechanism cannot locate the license temporarily. When the configuration completes, the license is set correctly. You can check the license key with the Main > Manage > License > List command in the NetBackup Virtual Appliance Shell Menu.

If you use NetBackup OpsCenter, the information that displays for the NetBackup Virtual Appliance on the Appliance Hardware page does not apply. The collected hardware information displays as question marks or as error messages similar to the following:

No <part(s)> detected

All of this information can be disregarded.

The Settings > Alerts > CallHome Registration Show command is available in the NetBackup Virtual Appliance Shell Menu. However, the NetBackup Virtual Appliance is not currently supported for registration. Visit the MyAppliance portal to see the latest information about supported appliance models.

An appliance self-test fails if the log in banner heading or a single line in the login banner message contains only the following text: ERROR:.

Windows 7/8.1 clients cannot automatically access the appliance CIFS shares. To work around this issue, run the following command from a Windows command prompt on the client:

net use /user:admin \\appliance-name *, where appliance-name is the fully qualified domain name (FQDN) of the appliance.

Enter your appliance administrator password at the prompt.

Once you have run this command, the client is able to access the CIFS shares.

For this release of NetBackup Virtual Appliance, Replication Director (RD) restores do not support dynamic multi-pathing (DMP) when the appliance is used as a backup or a recovery host.

The functionality of Active Directory (AD) user names is inconsistent, as described in the following scenarios:

The Main > Settings > Security > Authentication > LDAP > Certificate set path name command in the NetBackup Virtual Appliance Shell Menu does not allow any certificate path names that contain dashes.