Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint- Preparing for installation- About the deployment approach
- Deciding where to run CloudPoint
- 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
- Deploying CloudPoint in the AWS cloud
- Using plug-ins to discover assets
- Configuring off-host plug-ins- AWS plug-in configuration notes
- Google Cloud Platform plug-in configuration notes
- Microsoft Azure plug-in configuration notes
- Dell EMC Unity array plug-in configuration notes
- Pure Storage FlashArray plug-in configuration notes
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Configuring an off-host plug-in
- About CloudPoint plug-ins and assets discovery
 
- Configuring the on-host agents and plug-ins- About agents
- Oracle plug-in configuration notes
- MongoDB plug-in configuration notes
- Microsoft SQL plug-in configuration notes
- About the installation and configuration process
- Preparing to install the Linux-based on-host agent
- Preparing to install the Windows-based on-host agent
- Downloading and installing the on-host agent
- Configuring the Linux-based on-host agent
- Configuring the Windows-based on-host agent
- Configuring the on-host plug-in
- Configuring VSS to store shadow copies on the originating drive
 
- Protecting assets with CloudPoint's agentless feature
 
- Preparing for installation
- Section II. Configuring users
- Section III. Protecting and managing data- User interface basics
- Indexing and classifying your assets
- Protecting your assets with policies
- Tag-based asset protection
- Replicating snapshots for added protection- About snapshot replication
- About cross-account snapshot replication in the AWS cloud
- Requirements for replicating snapshots
- Cross-account snapshot replication support matrix
- Cross-account snapshot replication limitations
- Configuring replication rules
- Editing a replication rule
- Deleting a replication rule
 
- Managing your assets- Creating a snapshot manually
- Displaying asset snapshots
- Replicating a snapshot manually
- About snapshot restore
- About single file restore (granular restore)
- Single file restore requirements and limitations
- Restoring a snapshot
- Additional steps required after a SQL Server snapshot restore
- Additional steps required after an Oracle snapshot restore
- Additional steps required after a MongoDB snapshot restore
- Additional steps required after restoring an AWS RDS database instance
- Restoring individual files within a snapshot
- Deleting a snapshot
 
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
 
- Section IV. Maintaining CloudPoint- CloudPoint logging
- Troubleshooting CloudPoint- Restarting CloudPoint
- Docker may fail to start due to a lack of space
- CloudPoint installation fails if rootfs is not mounted in a shared mode
- Some CloudPoint features do not appear in the user interface
- Off-host plug-in deletion does not automatically remove file system and application assets
- Disk-level snapshot restore fails if the original disk is detached from the instance
- Snapshot restore for encrypted AWS assets may fail
- Error while adding users to CloudPoint
- CloudPoint fails to revert restored snapshots if indexing, classification, or restore operations fail
- SQL snapshot or restore and SFR operations fail if the Windows instance loses connectivity with the CloudPoint host
- Troubleshooting CloudPoint logging
 
- Working with your CloudPoint license
- Upgrading CloudPoint
- Uninstalling CloudPoint
 
- Section V. Reference
Viewing CloudPoint logs
CloudPoint provides a MongoDB client helper utility (flexsnap-log) that is located within the flexsnap-coordinator service. This utility allows you to access the MongoDB logs collection.
The general command syntax for using the flexsnap-log utility is as follows:
# sudo docker exec flexsnap-coordinator flexsnap-log <options>
Table: Flexsnap-log command options
| Command option | Description | 
|---|---|
| <service> | The CloudPoint service name. The command displays the logs of the specified service. | 
| - h | --help | Displays the command syntax and a description of the available options. | 
| -n <N> | --limit <N> | Displays the last "N" number of log messages. For example, to view the last 50 log messages, specify the following: 
 | 
| -t | --tail | Use this option to follow and monitor the log messages in real time. | 
| -F <format> | --format <format> | Displays the log messages in the specified output format. For example,  | 
| -v | --verbose | Displays the command output in a verbose mode. | 
| -j | --json | Displays the logs in a JavaScript Object Notation (JSON) format. | 
| -d <days> | --days <days> | Displays the logs for the last "DAYS" number of days. For example, to view the logs for the last seven days, specify the following: 
 | 
| -f <filename> | --file <filename> | Dumps the logs to the file specified in  | 
You can view the CloudPoint logs using any of the following commands on the CloudPoint host:
- To obtain all the CloudPoint service logs, run the following command: - # sudo docker exec flexsnap-coordinator flexsnap-log 
- To obtain logs of a specific CloudPoint container service, run the following command: - # sudo docker exec flexsnap-coordinator flexsnap-log <flexsnap-service name> 
- To tail or follow log messages, run the following command: - # sudo docker exec flexsnap-coordinator flexsnap-log -t 
- To obtain the last "N" number of log messages, run the following command: - # sudo docker exec flexsnap-coordinator flexsnap-log -n <N> 
- You can also combine these options to achieve a specific output. For example, to obtain the last 10 log messages for the - flexsnap-agentservice, run the following command:- # sudo docker exec flexsnap-coordinator flexsnap-log -n 10 flexsnap-agent - The command output displays messages similar to the following: - flexsnap-agent: flexsnap-agent-offhost[1] flexsnap.updates: INFO - find_files:netapp.zip flexsnap-agent: flexsnap-agent-offhost[1] flexsnap.updates: INFO - find_files:nutanix.zip flexsnap-agent: flexsnap-agent-offhost[1] flexsnap.updates: INFO - find_files:oracle.zip flexsnap-agent: flexsnap-agent-offhost[1] flexsnap.updates: INFO - find_files:purestg.zip flexsnap-agent: flexsnap-agent-offhost[1] flexsnap.updates: INFO - find_files:windows.zip flexsnap-agent: flexsnap-agent-offhost[1] INFO - Beginning registration with coordinator flexsnap-agent: flexsnap-agent-offhost[1] INFO - loaded plugin, sending configId status: {} flexsnap-agent: flexsnap-agent-offhost[1] INFO - Sending list of sources flexsnap-agent: flexsnap-agent-offhost[1] INFO Registration complete
The most recent CloudPoint logs are also available in the flexsnap-fluentd container logs. You can use standard Docker commands to obtain the logs.
Run the following command:
# sudo docker logs flexsnap-fluentd | grep flexsnap-agent | head -10
The command output displays messages similar to the following:
flexsnap-agent: {"container_name":"flexsnap-agent","source":"stdout","log":
"Mar 04 09:10:20 f5d1ae1c4808 flexsnap-agent-offhost[1] MainThread agent: 
INFO - Not generating certificate. Join token not passed for role agent"}
flexsnap-agent: {"container_name":"flexsnap-agent","source":"stdout","log":
"Mar 04 09:10:20 f5d1ae1c4808 flexsnap-agent-offhost[1] MainThread 
flexsnap.ca: INFO - Loading /opt/VRTScloudpoint/keys/agent.6c5c9.cert.pem 
/opt/VRTScloudpoint/keys/cacert.pem"}
flexsnap-agent: {"container_name":"flexsnap-agent","source":"stdout","log":
"Mar 04 09:10:20 f5d1ae1c4808 flexsnap-agent-offhost[1] MainThread 
flexsnap.connectors.rabbitmq: INFO - Starting service"}To view the flexsnap-fluentd container logs in real time, run the following command:
# sudo docker logs flexsnap-fluentd -f | grep <flexsnap-service-name>