Veritas NetBackup™ CloudPoint Install and Upgrade Guide

Last Published:
Product(s): NetBackup (8.3.0.1, 8.3)
Platform: Linux,UNIX,Windows
  1. Section I. CloudPoint installation and configuration
    1. Preparing for CloudPoint installation
      1.  
        About the deployment approach
      2.  
        Deciding where to run CloudPoint
      3.  
        About deploying CloudPoint in the cloud
      4.  
        Meeting system requirements
      5.  
        CloudPoint host sizing recommendations
      6.  
        Creating an instance or preparing the physical host to install CloudPoint
      7.  
        Installing Docker
      8.  
        Creating and mounting a volume to store CloudPoint data
      9.  
        Verifying that specific ports are open on the instance or physical host
    2. Deploying CloudPoint using the Docker image
      1.  
        Installing CloudPoint
      2.  
        Verifying that CloudPoint installed successfully
      3.  
        Configuring AWS KMS in CloudPoint
    3. CloudPoint cloud plug-ins
      1. AWS plug-in configuration notes
        1.  
          Prerequisites for configuring the AWS plug-in
        2.  
          Configuring AWS permissions for CloudPoint
        3.  
          AWS permissions required by CloudPoint
        4.  
          Before you create a cross account configuration
      2. Google Cloud Platform plug-in configuration notes
        1.  
          Google Cloud Platform permissions required by CloudPoint
        2.  
          Configuring a GCP service account for CloudPoint
        3.  
          Preparing the GCP service account for plug-in configuration
      3. Microsoft Azure plug-in configuration notes
        1.  
          Configuring permissions on Microsoft Azure
      4.  
        How to configure the CloudPoint cloud plug-ins?
    4. CloudPoint storage array plug-ins
      1. NetApp plug-in configuration notes
        1.  
          NetApp plug-in configuration parameters
        2.  
          Configuring a dedicated LIF for NetBackup access
        3.  
          Supported CloudPoint operations on NetApp storage
      2. Nutanix Files plug-in configuration notes
        1.  
          Nutanix Files plug-in configuration prerequisites
        2.  
          Nutanix Files plug-in considerations and limitations
        3.  
          Supported CloudPoint operations on Nutanix Files File Server
        4. Troubleshooting NetBackup issues for Nutanix Files
          1.  
            Backup jobs for Nutanix Files fail due to snapshot import and export operations failures
          2.  
            Plug-in configuration may fail if the Nutanix Files version is unsupported
      3. Dell EMC Unity array plug-in configuration parameters
        1.  
          Supported Dell EMC Unity arrays
        2.  
          Supported CloudPoint operations on Dell EMC Unity arrays
      4. Pure Storage FlashArray plug-in configuration notes
        1.  
          Supported Pure Storage FlashArray models
        2.  
          Supported CloudPoint operations on Pure Storage FlashArray models
      5. HPE RMC plug-in configuration notes
        1.  
          RMC plug-in configuration parameters
        2.  
          Supported HPE storage systems
        3.  
          Supported CloudPoint operations on HPE storage arrays
      6. Hitachi plug-in configuration notes
        1.  
          Hitachi plug-in configuration parameters
        2.  
          Supported Hitachi storage arrays
        3.  
          Supported CloudPoint operations on Hitachi arrays
      7. InfiniBox plug-in configuration notes
        1.  
          InifiniBox plug-in configuration parameters
        2.  
          Supported CloudPoint operations on InfiniBox arrays
      8.  
        How to configure the CloudPoint storage array plug-ins?
    5. CloudPoint application agents and plug-ins
      1.  
        Microsoft SQL plug-in configuration notes
      2. Oracle plug-in configuration notes
        1.  
          Optimizing your Oracle database data and metadata files
      3.  
        MongoDB plug-in configuration notes
      4.  
        About the installation and configuration process
      5.  
        Preparing to install the Linux-based agent
      6.  
        Preparing to install the Windows-based agent
      7.  
        Downloading and installing the CloudPoint agent
      8.  
        Registering the Linux-based agent
      9.  
        Registering the Windows-based agent
      10.  
        Configuring the CloudPoint application plug-in
      11.  
        Configuring VSS to store shadow copies on the originating drive
      12.  
        Creating a NetBackup protection plan for cloud assets
      13.  
        Subscribing cloud assets to a NetBackup protection plan
      14. About snapshot restore
        1.  
          Process for restoring SQL AG databases
      15.  
        Restore requirements and limitations for Microsoft SQL Server
      16.  
        Restore requirements and limitations for Oracle
      17.  
        Restore requirements and limitations for MongoDB
      18.  
        Steps required before restoring SQL AG databases
      19.  
        Recovering a SQL database to the same location
      20.  
        Recovering a SQL database to an alternate location
      21. Additional steps required after a SQL Server snapshot restore
        1.  
          Steps required after a SQL Server disk-level snapshot restore to new location
      22.  
        Additional steps required after restoring SQL AG databases
      23.  
        SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the CloudPoint host
      24.  
        Disk-level snapshot restore fails if the original disk is detached from the instance
      25.  
        Additional steps required after a MongoDB snapshot restore
      26.  
        Additional steps required after an Oracle snapshot restore
      27.  
        Additional steps required after restoring an AWS RDS database instance
    6. Protecting assets with CloudPoint's agentless feature
      1.  
        About the agentless feature
      2.  
        Prerequisites for the agentless configuration
      3.  
        Granting password-less sudo access to host user account
      4.  
        Configuring the agentless feature
  2. Section II. CloudPoint maintenance
    1. CloudPoint logging
      1.  
        About CloudPoint logging mechanism
      2. How Fluentd-based CloudPoint logging works
        1.  
          About the CloudPoint fluentd configuration file
        2.  
          Modifying the fluentd configuration file
      3.  
        CloudPoint logs
    2. Troubleshooting CloudPoint
      1.  
        Restarting CloudPoint
      2.  
        Troubleshooting CloudPoint logging
      3.  
        CloudPoint agent fails to connect to the CloudPoint server if the agent host is restarted abruptly
      4.  
        CloudPoint agent registration on Windows hosts may time out or fail
      5.  
        Disaster recovery when DR package is lost or passphrase is lost
    3. Upgrading CloudPoint
      1.  
        About CloudPoint upgrades
      2.  
        Supported upgrade path
      3.  
        Upgrade scenarios
      4.  
        Preparing to upgrade CloudPoint
      5.  
        Upgrading CloudPoint
    4. Uninstalling CloudPoint
      1.  
        Preparing to uninstall CloudPoint
      2.  
        Backing up CloudPoint
      3.  
        Unconfiguring CloudPoint plug-ins
      4.  
        Unconfiguring CloudPoint agents
      5.  
        Removing the CloudPoint agents
      6.  
        Removing CloudPoint from a standalone Docker host environment
      7.  
        Restoring CloudPoint

Unconfiguring CloudPoint agents

To enable CloudPoint to protect assets on a remote host, you first need to establish a connection between the CloudPoint server and the remote host. Depending on how the connection is configured (either with agents or using the agentless feature), CloudPoint uses agents that manage the plug-ins that are used to discover all the assets and perform the operations on the host.

Whenever you configure a remote host for protection, the agent registration and the plug-in configuration information is added to the CloudPoint database on the CloudPoint server. You can, if required, remove an agent entry from the CloudPoint database by performing the disconnect operation from the NetBackup UI.

Before you unconfigure an agent, consider the following:

  • Once you unconfigure an agent, you cannot re-configure a CloudPoint plug-in on the same host, if you had installed the CloudPoint agent on that host. To be able to configure a plug-in on the host again, you must first uninstall the agent package from the host, connect the host and install and register the agent with the CloudPoint server again.

  • You must first unconfigure the CloudPoint plug-in from the host before you proceed with the disconnect operation. The disconnect option is not enabled if a CloudPoint plug-in is configured on the host.

  • Unconfiguring an agent entry from the CloudPoint server does not uninstall the agent package from the host. You have to manually remove the agent binaries from the host after completing the disconnect operation.

  • Once you unconfigure an agent, all the file system assets that belong to that host are removed from the CloudPoint configuration. The assets no longer appear in the NetBackup UI.

To unconfigure the agent entry from the CloudPoint server

  1. Sign in to the NetBackup UI.
  2. Remove CloudPoint plug-in configuration from the host that you wish to disconnect.

    See Unconfiguring CloudPoint plug-ins.

  3. From the menu on the left, click Workloads > Cloud and then click the Virtual machines tab.
  4. On the Virtual machines tab, select the host where you want unconfigure the agent and then from the menu bar that appears at the top, click Disconnect.

    CloudPoint begins to unconfigure the agent. Observe that the Disconnect button now changes to Connect. This indicates that the disconnect operation is successful and the agent has been unconfigured successfully.

    The agent registration and all the assets information about that host is completely removed from the database.

  5. The next step is to manually uninstall the agent from the host on which you performed the disconnect operation. This is required if you wish to protect this host and its assets using CloudPoint at a later time.

    See Removing the CloudPoint agents.