Veritas NetBackup™ Flex Scale Administrator's Guide

Last Published:
Product(s): Appliances (3.1)
Platform: NetBackup Flex Scale OS
  1. Product overview
    1.  
      About Veritas NetBackup™ Flex Scale
  2. Viewing information about the NetBackup Flex Scale cluster environment
    1.  
      Accessing NetBackup Flex Scale and NetBackup
    2.  
      Accessing the NetBackup web user interface on the appliance
    3.  
      About the NetBackup Flex Scale web UI
    4.  
      About the NetBackup Flex Scale infrastructure management UI
    5. About the Dashboard view
      1.  
        Viewing all the activities
    6.  
      Working with NetBackup Flex Scale APIs
  3. NetBackup Flex Scale infrastructure management
    1. User management
      1.  
        Considerations for managing NetBackup Flex Scale users
      2.  
        Adding users
      3.  
        Changing user password
      4.  
        Removing users
      5.  
        Modifying user roles
      6.  
        Considerations for configuring AD/LDAP
      7.  
        Configuring AD server for Universal shares and Instant Access
      8.  
        Configuring AD/LDAP servers for NetBackup services
      9.  
        Configuring additional AD/LDAP servers for managing NetBackup services/Universal Shares/Instant Access
      10.  
        Configuring AD/LDAP servers on clusters deployed with only media servers
      11.  
        Directory services and certificate management
    2.  
      Region settings management
    3.  
      About NetBackup Flex Scale storage
    4. About Universal Shares
      1.  
        Creating a Protection Point for a Universal Share
    5.  
      Cloud bucket support for NetBackup Flex Scale
    6. Node and disk management
      1.  
        NetBackup Flex Scale network cabling
      2. Adding a node to the cluster using the NetBackup Flex Scale web interface
        1.  
          Considerations for adding a node when disaster recovery is configured
      3.  
        Adding a node using the REST APIs
      4.  
        Replacing a node in a cluster
      5.  
        Starting and stopping nodes
      6.  
        Rebooting a node
      7.  
        Adding an excluded node to the cluster
      8.  
        Replacing a disk
      9.  
        Adding an excluded disk to the cluster
      10.  
        Viewing the disk sync status
      11.  
        Viewing disk details
      12.  
        Viewing node details
      13.  
        Switching management console to another cluster node
    7. License management
      1.  
        Adding or removing storage licenses
      2.  
        Adding NetBackup licenses
    8.  
      Stopping NetBackup service containers
    9.  
      Starting NetBackup service containers
    10. Managing hardware vendor packages
      1.  
        Upgrading vendor packages
      2.  
        Uninstalling vendor packages
  4. NetBackup Flex Scale network management
    1.  
      About network management
    2.  
      Modifying DNS settings
    3.  
      About bonding Ethernet interfaces
    4. Bonding operations
      1. Bonding operations on data network
        1.  
          Creating a bond
        2.  
          Modifying a bond
        3.  
          Removing a bond
    5.  
      Configuring NetBackup Flex Scale in a non-DNS environment
    6. Data network configurations
      1.  
        Choosing the correct input method for data network configuration
      2. Network configuration on plain device (eth5)
        1.  
          Adding a data network
        2.  
          Modifying a data network
        3.  
          Deleting a data network
      3.  
        Network configuration on VLAN (eth5)
      4. Network configuration on bonded interfaces (bond0 on eth5 and eth7)
        1.  
          Adding a data network
      5.  
        VLAN on bond of eth5 and eth7 (bond0)
      6.  
        Network configuration on management interface (eth1)
      7.  
        Network configurations for adding a partial data network
      8.  
        Support for multiple VLAN when disaster recovery is configured
    7.  
      Configuring static routes on a NetBackup Flex Scale cluster
  5. NetBackup Flex Scale infrastructure monitoring
    1. About alert management
      1.  
        Viewing information about alerts
      2.  
        Managing alerts
    2. About event notification
      1.  
        Purging events
    3. About AutoSupport and Call Home
      1.  
        Setting up email alerts
      2.  
        Setting up SNMP alerts
      3.  
        Configuring Call Home settings
    4. Monitoring hardware components
      1.  
        Monitoring deviations in firmware, driver, and utilities
    5.  
      Performing health check for the cluster
    6.  
      Locating the disks
    7.  
      Monitoring usage and licensed capacity using Veritas NetInsights Console
  6. Resiliency in NetBackup Flex Scale
    1.  
      Erasure coding in NetBackup Flex Scale
    2.  
      Handling split-brain scenario in NetBackup Flex Scale
    3.  
      High availability of the NetBackup primary service
    4.  
      High availability of NetBackup services
    5.  
      NetBackup catalog protection
    6. NetBackup primary service catalog protection using checkpoints
      1.  
        Performing a recovery of the catalog file system using GUI
      2.  
        Performing a recovery of the catalog file system using REST APIs
  7. EMS server configuration
    1.  
      Configuring an external BYOS media server
    2.  
      Configuring an external NBA media server
  8. Site-based disaster recovery in NetBackup Flex Scale
    1.  
      About site-based disaster recovery in NetBackup Flex Scale
    2.  
      Configuring disaster recovery using GUI
    3.  
      Clearing the host cache
    4.  
      Automated NetBackup SLP management
    5.  
      DNS key management
    6.  
      Managing disaster recovery using GUI
    7. Performing disaster recovery using RESTful APIs
      1.  
        Establishing trust and setting up authentication
      2.  
        Configuring disaster recovery
      3.  
        Managing disaster recovery
    8.  
      Active-Active disaster recovery configuration
    9.  
      NetBackup optimized duplication using Storage Lifecycle Policies
  9. NetBackup Flex Scale security
    1. STIG overview for NetBackup Flex Scale
      1.  
        STIG-compliant password policy rules
      2.  
        Enabling STIG for NetBackup Flex Scale
      3.  
        Viewing the NetBackup Flex Scale STIG status
    2. FIPS overview for NetBackup Flex Scale
      1.  
        Viewing the NetBackup Flex Scale FIPS status
    3.  
      Managing the login banner
    4.  
      Changing the password policy
    5. Support for immutability in NetBackup Flex Scale
      1.  
        About lockdown modes
      2.  
        Selecting or changing the lockdown mode
      3.  
        Restricted access to Remote Management Platform (HPe iLO)
      4.  
        Configuring immutability using GUI
    6.  
      Authenticating users using digital certificates or smart cards
    7.  
      About system certificates on NetBackup Flex Scale
    8. Deploying external certificates on NetBackup Flex Scale
      1.  
        Deploying ECA using the GUI
      2.  
        Log locations
      3.  
        Considerations for performing other operations when ECA is deployed
  10. Troubleshooting
    1.  
      Services management
    2.  
      Audit logs
    3. Collecting logs for cluster nodes
      1.  
        Uploading logs to Veritas Support
      2.  
        Downloading logs
    4. Troubleshooting NetBackup Flex Scale issues
      1.  
        If cluster configuration fails (for example because an IP address that was already in use is specified) and you try to reconfigure the cluster, the UI displays an error but the configuration process continues to run
      2.  
        Validation error while adding VMware credentials to NetBackup
      3.  
        NetBackup Web UI incorrectly displays some NetBackup Flex Scale processes as failed
      4.  
        Unable to create BMR Shared Resource Tree (SRT) on NetBackup Flex Scale Appliance
      5.  
        NetBackup configuration files are not persistent across operations that require restarting the system
  11. Appendix A. Maintenance procedures for HPE servers
    1.  
      Replacement procedure for a chassis fan
    2.  
      Replacement procedure for power supply
    3.  
      Replacement procedure for a single OS disk
    4.  
      Replacement procedure for both OS disks on the management console node
    5.  
      Replacement procedure for both OS disks on a non- management console node
    6.  
      Replacement procedure for NVMe disks (SSDs)
    7.  
      Replacement procedure for RAID controller
    8.  
      Replacement procedure for an Integrated Lights-Out (iLO) port
    9.  
      Replacement procedure for quad-port NIC
    10.  
      Procedure for memory expansion (DIMMs)
    11.  
      Replacement procedure for memory (DIMMs)
    12.  
      Replacement procedure for Mellanox port
  12. Appendix B. Configuring NetBackup optimized duplication
    1. Configuring a Storage Lifecycle Policy for optimized duplication
      1.  
        Creating a Storage Lifecycle Policy for optimized duplication
      2.  
        Configuring a policy to use an SLP
      3.  
        Updating the policy to reverse the replication direction
  13. Appendix C. Disaster recovery terminologies
    1.  
      VVR technology in disaster recovery
    2.  
      About response fields in the GET disaster recovery API
  14. Appendix D. Configuring Auto Image Replication
    1.  
      Auto Image Replication configuration

Managing hardware vendor packages

You are required to install the hardware vendor packages that are compatible with your hardware vendor platform. The vendor packages are not installed with the ISO and you need to install the vendor packages separately for the nodes to be healthy. The list of required vendor packages for each hardware vendor platform is maintained in the vendor_utilities.json file. The file is included in the ISO that is pre-installed on the nodes. You can edit this file if the vendor requires you to include additional vendor packages or to support a new model or vendor platform.

Instead of downloading the vendor_utilities.json file to view the list of required vendor packages, you can also use the system list hw-vendor-packages command to list the required vendor-packages.

The following example shows the list of required vendor packages for an HPE platform:

system list hw-vendor-packages

Name           Version             Arch
=============  ==================  ======
ssacli         4.21-7.0            x86_64
ssaducli       4.21-7.0            x86_64
ilorest        3.2.2-32            x86_64
kmod-smartpqi  2.1.12-055.rhel7u9  x86_64

You must download the required vendor packages from the hardware vendor site. You can uninstall or upgrade the vendor packages after they are installed.

To install vendor packages after the cluster is configured:

  1. Use any one of the following options to log on using the user account that you created when you configured the cluster:

    • Use a user account with both Appliance Administrator and NetBackup Administrator role, or a user account with only an Appliance administrator role to log on to the NetBackup Flex Scale web UI https://ManagementServerIPorFQDN/webui where ManagementServerIPorFQDN is the public IP address or the FQDN that you specified for the NetBackup Flex Scale management server during the cluster configuration, and then in the left pane click Cluster Management > Cluster settings > Software management.

    • Use a user account with an Appliance Administrator role to log on to the NetBackup Flex Scale infrastructure management UI https://ManagementServerIPorFQDN:14161 where ManagementServerIPorFQDN is the public IP address or the FQDN that you specified for the NetBackup Flex Scale management server during the cluster configuration, and then in the left pane click Settings > Software management.

    Note:

    If you access the NetBackup Flex Scale infrastructure management UI by using the short host name from a node, set the DNS settings (name server, domain name, and search domain) or ensure that the entry for mapping the short host name to an IP address exists in the hosts file of the node.

  2. On the Software management page, click Vendor packages.
  3. On the Vendor packages tab click Verify.
  4. Do one of the following:

    • If there is a change in required vendor packages, download the existing vendor_utilities.json file, edit the file to update the vendor package list, and then upload the updated JSON file. The uploaded JSON file replaces the existing file and is now used a reference for the list of vendor packages that must be present on the node. To download the JSON file, on the Vendor packages tab click Download JSON file. Edit the downloaded file. To upload the updated file, click Next > Upload JSON file. Click Verify.

    • If there is no change in the required vendor packages, click Next > Verify

  5. If the required vendor packages are missing or the installed package version is earlier than what is listed in the JSON file, the node is marked as unhealthy and the details about the missing packages are displayed for each node. Click Add.
  6. Download the required vendor packages from the vendor site.
  7. Upload the vendor packages to the driver node. On the Vendor packages tab, click Add and select the vendor packages that you downloaded. The selected vendor packages are uploaded to the /system/inst/patch/incoming location of the driver node and their status in the UI is shown as Available.
  8. Optionally, to remove the uploaded vendor packages, select the vendor packages and click Remove.
  9. If the vendor packages are required to be installed in a specific sequence, click the arrows in the Reorder column to change the installation sequence.
  10. Install the uploaded vendor packages. Select all the vendor packages and click Install. Each package is installed on all the nodes. If the packages are installed successfully on all the nodes, a notification is displayed on the top of the page and the package status changes to Installed. If the installation fails on one of the nodes, the vendor package is rolled back on all the nodes and the package status is shown as Available.

See Upgrading vendor packages.

See Uninstalling vendor packages.