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
- 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
- How to configure the CloudPoint storage array plug-ins?
- 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
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
Troubleshooting CloudPoint logging
You can retrieve the logs of a CloudPoint service from the /cloudpoint/logs/flexsnap.log file by running the following command:
# sudo cat /cloudpoint/logs/flexsnap.log | grep <flexsnap-service name>
Consider the following if you are upgrading from CloudPoint version 2.2.x:
You cannot retrieve the CloudPoint logs using Docker command (
# sudo docker exec flexsnap-coordinator flexsnap-log). If you run this command, you will see the following error message:flexsnap-log is deprecated. Retreive current logs from /cloudpoint/logs/flexsnap.log
You can retrieve all the logs from the MongoDB database to a file on disk by running the following command:
# sudo docker exec flexsnap-coordinator flexsnap-log --file /cloudpoint/logs/<previousversion_logs>.log
If the MongoDB database is taking up more disk space due to the logs, you can drop the database using the following command:
# sudo docker exec flexsnap-coordinator flexsnap-log --purge