Veritas NetBackup™ CloudPoint Install and Upgrade Guide

To install CloudPoint

1. Download the CloudPoint image to the system on which you want to deploy CloudPoint.

   The CloudPoint image name resembles the following format:

   VRTScloudpoint-podman-10.x.x.x.x.tar.gz

2. Change directories to where you have downloaded the CloudPoint image.
3. Un-tar the image file and list the contents:

   # gunzip VRTScloudpoint-podman-10.x.x.x.x.tar.gz

   # ls

   The output resembles the following:

   # gunzip VRTScloudpoint-podman-10.x.x.x.x.tar.gz
   
   # tar -xvf VRTScloudpoint-podman-10.x.x.x.x.tar
   VRTScloudpoint-podman-10.x.x.x.9803.img.gz
   flexsnap-podman-api.service
   flexsnap_preinstall.sh
   flexsnap-podman-containers.service
   dnsname
   
   # ls
   VRTScloudpoint-podman-10.x.x.x.9803.img.gz
   flexsnap-podman-api.service
   flexsnap_preinstall.sh
   flexsnap-podman-containers.service
   dnsname

4. Run the following command to prepare the CloudPoint host for installation:

   # ./flexsnap_preinstall.sh

   The output resembles the following:

   Executing the following changes on this node to prepare the CloudPoint
   server for installation:
   1) Loading CloudPoint service images.
   2) Copying dnsname plugin to the /usr/libexec/cni folder.
   3) Check if dnsmasq rpm is installed on the host, if not,
      installation is done automatically.
   4) Creating and starting the systemd service for the Podman API server.
   Do you want to continue? (Yes/No): Yes
   Loaded image(s): localhost/veritas/flexsnap-agent:9.x.x.x.x
   Loaded image(s): localhost/veritas/flexsnap-api-gateway:9.x.x.x.x
   Loaded image(s): localhost/veritas/flexsnap-certauth:9.x.x.x.x
   ............
   ............
   Loaded image(s): localhost/veritas/flexsnap-workflow:9.x.x.x.x
   Copying dnsname plugin...done
   Starting Podman API service...done
   Enabling Podman Containers service...done

5. Install NetBackup CloudPoint with the following command:

   # podman run -it --rm --privileged -v /cloudpoint:/cloudpoint -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-cloudpoint:10.x.x.x.x install

   Note:

   This is a single command. Ensure that you enter the command without any line breaks.

   In this step, CloudPoint does the following:

   • Creates and runs the containers for each of the CloudPoint services.

   • Creates self-signed keys and certificates for nginx

   The output resembles the following:

   Installing the services
   Configuration started at time: Thu Feb 18 09:20:12 UTC 2021
   podman server version: 2.2.1 or 3.3.1 Supported: true
   This is a fresh install of NetBackup CloudPoint 9.x.x.x.x
   CloudPoint currently is not configured.
   Starting initial services before configuration.
   Creating network: flexsnap-network ...done
   Starting container: flexsnap-fluentd ...done
   Creating container: flexsnap-mongodb ...done
   Creating container: flexsnap-rabbitmq ...done
   Creating container: flexsnap-certauth ...done
   Creating container: flexsnap-api-gateway ...done
   Creating container: flexsnap-coordinator ...done
   Creating container: flexsnap-listener ...done
   Creating container: flexsnap-agent ...done
   Creating container: flexsnap-onhostagent ...done
   Creating container: flexsnap-scheduler ...done
   Creating container: flexsnap-policy ...done
   Creating container: flexsnap-notification ...done
   Creating container: flexsnap-idm ...done
   Starting container: flexsnap-config ...done
   Creating self signed keys and certs for nginx ...done
   Please provide CloudPoint admin credentials for configuration:

   If the CloudPoint host is behind a proxy server, use the following command instead:

   # podman run -it --rm --privileged 
   -v /<full_path_to_volume_name>:/<full_path_to_volume_name> 
   -e VX_HTTP_PROXY=<http_proxy_value>
   -e VX_HTTPS_PROXY=<https_proxy_value>
   -e VX_NO_PROXY=<no_proxy_value>
   -v /run/podman/podman.sock:/run/podman/podman.sock
   veritas/flexsnap-cloudpoint:10.x.x.x.x install

   Replace the following parameters as per your environment:

   Parameter	Description
   <http_proxy_value> (required only if the instance uses a proxy server)	Represents the value to be used as the HTTP proxy for all connections. For example, "http://proxy.mycompany.com:8080/".
   <https_proxy_value> (required only if the instance uses a proxy server)	Represents the value to be used as the HTTPS proxy for all connections. For example, "https://proxy.mycompany.com:8080/".
   <no_proxy_value> (required only if the instance uses a proxy server)	Represents the addresses that are allowed to bypass the proxy server. You can specify host names, IP addresses, and domain names in this parameter. Use commas to separate multiple entries. For example, "localhost,mycompany.com,192.168.0.10:80". Note: If CloudPoint is being deployed in the cloud, ensure that you set the following values in this parameter: For an AWS instance, add the following: 169.254.169.254 For a GCP virtual machine, add the following: 169.254.169.254,metadata,metadata.google.internal For an Azure virtual machine, add the following: 169.254.169.254 CloudPoint uses these addresses to gather instance metadata from the instance metadata service.

6. Provide the following details when prompted on the command prompt:

   Parameter	Description
   Admin username	Specify a user name for the CloudPoint administrator user account.
   Admin password	Specify a password for the admin user.
   Confirm Admin password	Confirm the admin user password.
   Host name for TLS certificate	Specify the IP address or the Fully Qualified Domain Name (FQDN) of the CloudPoint host. If you connect to the host using different names (for example, myserver, myserver.mydomain, or myserver.mydomain.mycompany.com), then ensure that you add all the names here if you want to enable CloudPoint access using those names. Use commas to specify multiple entries. The names you specify here must point to the same CloudPoint host. The specified names or IP address are added to the list of host names to use for configuring CloudPoint. The installer uses these names to generate a server certificate for the CloudPoint host.
   Port	Specify the port through which the CloudPoint server can communicate. Default is port 443.

   The installer then displays messages similar to the following:

   Starting container: flexsnap-nginx ...done
   Waiting for CloudPoint configuration to complete (22/22) ...done
   Configuration complete at time Thu Feb 18 09:26:36 UTC 2021!

7. This concludes the CloudPoint deployment process. The next step is to register the CloudPoint server with the Veritas NetBackup primary server.

   If CloudPoint is deployed in the cloud, refer to the NetBackup Web UI Cloud Administrator's Guide for instructions. If CloudPoint is deployed on-premise, refer to the NetBackup Snapshot Client Administrator's Guide for instructions.