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
Restoring a snapshot
To restore a snapshot
- Navigate to your list of assets.
On the CloudPoint dashboard, in the Environment card, select the asset type you want to work with, and click Manage. This example restores an application snapshot.
- On the Asset Management page, select the application whose snapshot you want to restore.
- On the Details page click View Snapshots.
- On the Snapshot Management page, select the snapshot you want to restore and then click Restore.
- On the Restore page, complete the following.
Specify a Restore Job Name and Description.
Select one of the following restore options, depending on the snapshot type:
Snapshot type
Restore option
Description
Cloud snapshot
Host / instance
Disk
Application (host, disk)
Overwrite existing
Replaces the current asset with the snapshot.
Following is the behavior for this option:
CloudPoint creates new EBS volumes from the VM (disk) snapshots and stops the original instance. It detaches the existing volumes and attaches them to the stopped instance to start the instance.
VM or instance ID remain the same, but as new disks are created from the snapshots, the disk IDs are different.
Instance and volume tags are copied properly.
Policies assigned to hosts are preserved.
Notes:
This restore option is supported on AWS only.
CloudPoint does not remove or delete the older volumes in any restore scenario.
If an instance is corrupted, Veritas recommends that you revert that instance to a previous working state instead of spinning up a new instance by restoring an existing snapshot. This helps in avoiding any orchestration tasks that may be needed to integrate the instance into other workflows.
Original Location
Restores the snapshot to the same location as the asset, without overwriting the existing asset.
New location
Restores the snapshot to a completely different location in the cloud.
You can select a target destination from the list of available options displayed in the drop-down list. For example, in case of AWS cloud, the list displays all the subnets in the AWS region where the asset resides.
Array snapshot
Disk
Overwrite existing
Replaces the current asset with the snapshot.
CloudPoint sends a snapshot restore request to the underlying storage array and presents it with the selected snapshot. The storage array then performs the actual snapshot restore operation.
- Click Restore.
(Applicable for AWS only) If you are performing a disk-level snapshot restore, then the new disk that is created after the restore does not bear a name. The disk name appears blank. In such a case, you have to manually assign a name to the disk to be able to identify and use the disk after the restore is complete.
Note:
Starting with release 2.0.2, you can restore an Azure instance snapshot to a private network. The instance does not require a public IP address.