Veritas NetBackup™ Virtual Appliance Getting Started Guide
- Product overview
- NetBackup Virtual Appliance product description
- Preparing the initial deployment
- Deploying and configuring the appliance
- How to deploy and configure a NetBackup Virtual Appliance combined master and media server
- How to deploy and configure a NetBackup Virtual Appliance media server
- How to deploy and configure a NetBackup Virtual Appliance master server
- How to deploy and configure a NetBackup Virtual Appliance combined master and media server
- Post initial configuration procedures
- Introduction to the NetBackup Virtual Appliance Shell Menu
Operational Notes for the NetBackup Virtual Appliance 4.0 release
This chapter contains the topics that explain important aspects of NetBackup Virtual Appliance 4.0 operations that may not be documented elsewhere in the documentation.
Because NetBackup Virtual Appliance 4.0 installs NetBackup 9.0 software, the operational notes that apply to NetBackup 9.0 also apply to NetBackup Virtual Appliance 4.0. For more information on the operational notes for NetBackup, refer to the NetBackup 9.0 Release Notes. The NetBackup Release Notes are available from the NetBackup Documentation page on the Veritas Support website.
The following list contains the notes and the known issues that apply for this release:
For this release, the VxUpdate command is incorrectly located under the Main > Manage view instead of the Main > Manage > Software view. The full command for this release is Main > Manage > VxUpdate, and the functionality remains the same.
Incorrect error message when adding new AD or LDAP users (software versions 4.0 and earlier)
When adding new AD or LDAP users from the appliance shell menu, the following error message may appear:
The user name that you have entered is not valid. Enter a valid user name.
This error message may not accurately reflect the actual cause of the failure. To determine the cause of the failure, see the following article:
https://www.veritas.com/content/support/en_US/article.100049282
Intermittent test email notification after upgrade
After upgrading to version 4.0, the test email may not always succeed. To workaround this issue, delete all of the SMTP server configuration information and then re-enter all of the information.
Upgrades to NetBackup Virtual Appliance version 3.3.0.1 or 4.0 from the Appliance Management Console fail with error "Preflight check has failed"
This issue can happen when the AMS repository contains two versions of the same NetBackup Appliance Upgrade Readiness Analyzer tool. For example, the analyzer tool package has two file name formats as follows:
SYMC_NBAPP_update_ReadinessAnalyzer-3.3.0.1-20200713.noarch.rpm
VRTS_NBAPP_update_ReadinessAnalyzer-3.3.0.1-20200713.noarch.rpm
This issue occurs if both of the above packages exist in the AMS repository. To workaround this issue, remove one of the packages from the repository.
"Fail Lock" STIG rule only supports local users, not remote users
When STIG is enabled, one of the enforced remediation rules is
xccdf_org.ssgproject.content_rule_accounts_passwords_pam_faillock_deny
. This "Fail Lock" rule is intended to lock an account and prevent login access to it if multiple and successive incorrect passwords have been entered. The current implementation for NetBackup appliances enforces this rule for local users. However, authentication by AD, LDAP, or Kerberos users is not supported when this rule is put into effect when STIG is enabled. Those authentication methods can be re-enabled with the appropriate shell menu commands. If you plan to enable STIG, it is recommended to enable it before configuring remote access.For details about how to work around this issue, see the following article:
https://www.veritas.com/content/support/en_US/article.100048258
DR catalog recovery error if catalog is on a remote server
If you mount a remote DR path on an appliance (MountPoints > Mount) and then configure a catalog backup policy from the NetBackup Java console, the backup job to the mounted remote path results in the following error:
exit status 35 cannot make required directory
To resolve this issue, use the Policy Configuration Wizard in the NetBackup Java console to create a DR catalog backup policy for a NetBackup Appliance. For details, see the following article:
https://www.veritas.com/content/support/en_US/article.100048250
Preflight upgrade self-test fails on attempted upgrades to 3.2 and 3.3.0.1
The following issues may cause the preflight upgrade self-test to fail on attempted upgrades to versions 3.2 and 3.3.0.1
If the current job IDs used by NetBackup are 1 million or higher, the preflight upgrade self-test incorrectly indicates that active jobs are in progress. Although no jobs are in progress, this issue prevents the upgrade. To resolve this issue, see the following article:
https://www.veritas.com/content/support/en_US/article.100046691
If the client name includes the word
Active
, the preflight upgrade self-test incorrectly interprets "Active" as an active backup job. To resolve this issue, see the following article:https://www.veritas.com/content/support/en_US/article.100048337
Error message appears when configuring MSDP storage during initial configuration
For new deployments of version 3.3.0.1, the following error message may appear during the initial configuration after setting the role and configuring MSDP storage:
- [Error] Failed to enable optimized synthetic full backups (Storage Server Attribute). This appliance may not be used for synthetic full backups. [status: 20; stdout: ; stderr: Could not connect to storage server. Please verify that <server_name> is a valid storage server of the required type and is reachable on the network. If an OpenStorage plug-in is required for this storage server, verify it is installed. Attribute flag OptimizedImage was not set.
Failed to change storage server eagappflx056, invalid command parameter]
The failed process automatically makes a second attempt to enable optimized synthetic full backups which is successful. You can ignore the error message.
Settings > SNMP polling Enable command fails from remote sessions
When you log in to the appliance from a remote machine and run this command, the message Timeout: No Response from <server_name> may occur. To resolve this issue, see the following article:
https://www.veritas.com/content/support/en_US/article.100048415
No email alert for backup failures when MSDP usage shows 92%
Appliances may not generate email alert V-475-103-1000 if backup jobs are failing when MSDP usage is at 92%. Refer to the appliance interfaces to check the disk usage if backup jobs start to fail.
After an upgrade to software version 4.0, 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.
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.
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:
NetBackup Virtual Appliance Shell Menu
This interface does not recognize Active Directory (AD) user names as case sensitive.
NetBackup Java Console
This interface does recognize Active Directory (AD) user names as case sensitive. When you enter these user names with all lowercase letters, access to the NetBackup Administrator's Console is granted. If you enter these user names with any or all uppercase letters, access to the NetBackup Backup, Archive, and Restore interface is granted.
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.