Veritas NetBackup™ CloudPoint Install and Upgrade Guide
- Section I. CloudPoint installation and configuration
- Preparing for CloudPoint installation
- About the deployment approach
- Deciding where to run CloudPoint
- About deploying CloudPoint in the cloud
- Meeting system requirements
- CloudPoint host sizing recommendations
- Creating an instance or preparing the physical host to install CloudPoint
- Installing Docker
- Creating and mounting a volume to store CloudPoint data
- Verifying that specific ports are open on the instance or physical host
- Deploying CloudPoint using the Docker image
- CloudPoint cloud plug-ins
- CloudPoint storage array plug-ins
- How to configure the CloudPoint storage array plug-ins?
- NetApp plug-in configuration notes
- Nutanix Files plug-in configuration notes
- Dell EMC Unity array plug-in configuration parameters
- Pure Storage FlashArray plug-in configuration notes
- HPE RMC plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- Dell EMC PowerScale (Isilon) plug-in configuration notes
- Qumulo plug-in configuration notes
- CloudPoint application agents and plug-ins
- Microsoft SQL plug-in configuration notes
- Oracle plug-in configuration notes
- MongoDB plug-in configuration notes
- About the installation and configuration process
- Preparing to install the Linux-based agent
- Preparing to install the Windows-based agent
- Downloading and installing the CloudPoint agent
- Registering the Linux-based agent
- Registering the Windows-based agent
- Configuring the CloudPoint application plug-in
- Configuring VSS to store shadow copies on the originating drive
- Creating a NetBackup protection plan for cloud assets
- Subscribing cloud assets to a NetBackup protection plan
- About snapshot restore
- Restore requirements and limitations for Microsoft SQL Server
- Restore requirements and limitations for Oracle
- Restore requirements and limitations for MongoDB
- Steps required before restoring SQL AG databases
- Recovering a SQL database to the same location
- Recovering a SQL database to an alternate location
- Additional steps required after a SQL Server snapshot restore
- Additional steps required after restoring SQL AG databases
- SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the CloudPoint host
- Disk-level snapshot restore fails if the original disk is detached from the instance
- Additional steps required after a MongoDB snapshot restore
- Additional steps required after an Oracle snapshot restore
- Additional steps required after restoring an AWS RDS database instance
- Protecting assets with CloudPoint's agentless feature
- Volume Encryption in NetBackup
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
- CloudPoint logging
- Troubleshooting CloudPoint
- Restarting CloudPoint
- Troubleshooting CloudPoint logging
- CloudPoint agent fails to connect to the CloudPoint server if the agent host is restarted abruptly
- CloudPoint agent registration on Windows hosts may time out or fail
- Disaster recovery when DR package is lost or passphrase is lost
- Agentless log file name changed
- Upgrading CloudPoint
- Uninstalling CloudPoint
Backing up CloudPoint
To back up CloudPoint when it is deployed in a cloud
- Stop CloudPoint services.
Use the following command:
# sudo docker run -it --rm -v /full_path_to_volume_name:/full_path_to_volume_name -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:version stop
Here, version represents the currently installed CloudPoint product version. You can retrieve the version using the following command:
# cat /cloudpoint/version
For example:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:8.3.0.8549 stop
Note:
This is a single command. Ensure that you enter the command without any line breaks.
- Make sure that all CloudPoint containers are stopped. This step is important because all activity and connections to and from CloudPoint must be stopped to get a consistent CloudPoint backup.
Enter the following:
# sudo docker ps | grep veritas
This command should not return any actively running CloudPoint containers.
- (Optional) If you still see any active containers, repeat step 2. If that does not work, run the following command on each active container:
# sudo docker kill container_name
For example:
# sudo docker kill flexsnap-api
- After all the containers are stopped, take a snapshot of the volume on which you installed CloudPoint. Use the cloud provider's snapshot tools.
- After the snapshot completes, restart CloudPoint services.
Use the following command:
# sudo docker run -it --rm -v /full_path_to_volume_name:/full_path_to_volume_name-v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:version start
Here, version represents the currently installed CloudPoint product version.
For example:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:8.3.0.8549 start
Note:
This is a single command. Ensure that you enter the command without any line breaks.
To backup CloudPoint when it is deployed on-premise
- Stop CloudPoint services.
Use the following command:
# sudo docker run -it --rm -v /full_path_to_volume_name:/full_path_to_volume_name -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:version stop
Here, version represents the currently installed CloudPoint product version.
For example:
# sudo docker run -it --rm -v /cloudpoint:/cloudpoint -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-cloudpoint:8.3.0.8549 stop
Note:
This is a single command. Ensure that you enter the command without any line breaks.
- Make sure that all CloudPoint containers are stopped. This step is important because all activity and connections to and from CloudPoint must be stopped to get a consistent CloudPoint backup.
Enter the following:
# sudo docker ps | grep veritas
This command should not return any actively running CloudPoint containers.
- (Optional) If you still see any active containers, repeat step 2. If that does not work, run the following command on each active container:
# sudo docker kill container_name
For example:
# sudo docker kill flexsnap-api
- Back up the folder
/cloudpoint. Use any backup method you prefer.For example:
# tar -czvf cloudpoint_dr.tar.gz /cloudpoint
This command creates a compressed archive file named
cloudpoint_dr.tar.gzthat contains the data in the/cloudpointdirectory.