Veritas NetBackup™ Virtual Appliance Getting Started Guide

Last Published:
Product(s): Appliances (3.3.0.1)
Platform: NetBackup Virtual Appliance
  1. Product overview
    1. NetBackup Virtual Appliance product description
      1.  
        About the NetBackup Virtual Appliance master server role
      2.  
        About the NetBackup Virtual Appliance combined master and media server role
      3.  
        About the NetBackup Virtual Appliance media server role
    2.  
      NetBackup Virtual Appliance supported features
    3.  
      About the NetBackup Virtual Appliance documentation
    4.  
      NetBackup Virtual Appliance 3.3.0.1 new features, enhancements, and changes
    5.  
      Known limitations of the NetBackup Virtual Appliance 3.3.0.1 release
    6.  
      Operational Notes for the NetBackup Virtual Appliance 3.3.0.1 release
  2. Preparing the initial deployment
    1.  
      NetBackup Virtual Appliance product files (OVF templates)
    2.  
      NetBackup Virtual Appliance deployment methods
    3. NetBackup Virtual Appliance deployment guidelines
      1.  
        Configuration overview for NetBackup Virtual Appliance MSDP cloud applications
      2.  
        NetBackup Virtual Appliance initial deployment checklist
    4.  
      Troubleshooting NetBackup Virtual Appliance initial deployment issues
  3. Deploying and configuring the appliance
    1. How to deploy and configure a NetBackup Virtual Appliance combined master and media server
      1.  
        Using the vSphere Client to deploy a combined master and media server appliance
      2.  
        Using the OVF Tool to deploy a combined master and media server appliance
      3.  
        Performing the initial configuration on a NetBackup Virtual Appliance combined master and media server
      4.  
        Completing the initial configuration of the NetBackup Virtual Appliance combined master and media server
    2. How to deploy and configure a NetBackup Virtual Appliance media server
      1.  
        Using the vSphere Client to deploy a media server appliance
      2.  
        Using the OVF Tool to deploy a media server appliance
      3.  
        Configuring a master server to communicate with an appliance media server
      4.  
        Performing the initial configuration on a NetBackup Virtual Appliance media server
    3. How to deploy and configure a NetBackup Virtual Appliance master server
      1.  
        Using the vSphere Client to deploy a NetBackup Virtual Appliance master server
      2.  
        Using the OVF Tool to deploy a master server
      3.  
        Performing the initial configuration on a NetBackup Virtual Appliance master server
  4. Post initial configuration procedures
    1.  
      About modifying the NetBackup Virtual Appliance settings
    2.  
      Adding a permanent license key if an evaluation license key expires
    3.  
      Managing license keys on the NetBackup Virtual Appliance
  5. Introduction to the NetBackup Virtual Appliance Shell Menu
    1.  
      Using the NetBackup Virtual Appliance Shell Menu
    2.  
      About the NetBackup Virtual Appliance Shell Menu command views

Operational Notes for the NetBackup Virtual Appliance 3.3.0.1 release

This chapter contains the topics that explain important aspects of NetBackup Virtual Appliance 3.3.0.1 operations that may not be documented elsewhere in the documentation.

Because NetBackup Virtual Appliance 3.3.0.1 installs NetBackup 8.3.0.1 software, the operational notes that apply to NetBackup 8.3.0.1 also apply to NetBackup Virtual Appliance 3.3.0.1. For more information on the operational notes for NetBackup, refer to the NetBackup 8.3.0.1 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:

  • "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

  • IPsec channel configuration failures

    For appliances that use versions 3.1.2 and later, IPsec channel configuration between appliances may fail and show the following errors:

    [Error] Remote host <appliance_name> does not have valid IPsec configuration.

    [Error] Unable to execute sudo /opt/NBUAppliance/scripts/ipsec_utils.pl -check.

    [Error] Failed to create HostInfo object for host <appliance_name>.

    [Error] SSH command execution failed.

    To resolve this issue, contact Veritas Support and refer them to article 100048279.

  • 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

  • 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 3.3.0.1, 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.

  • 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.

  • 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.