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
Replicating a snapshot manually
When you replicate a snapshot, you save a copy of the snapshot to another physical location. Replication gives your data extra protection in case of a disaster at the original site.
The most efficient way to use replication is to define replication rules and then apply the rules to your snapshot policies. That way, replication takes on a regular schedule. Setting up replication rules is described in the chapter titled "Replicating snapshots for added protection."
See About snapshot replication.
However, you can also replicate a snapshot manually. That is, you can navigate to a particular snapshot at any time, specify an alternate location, and replicate it.
Regardless of the asset type you work with, the steps for replicating a snapshot are the same.
To replicate a snapshot manually
- 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 procedure uses an application snapshot for replication as an example.
- On the Asset Management page, select the application whose snapshot you want to replicate.
- On the Details page click View Snapshots
- On the Snapshot Management page, select the snapshot you want to replicate. You can only select one.
- Depending on the structure for the snapshot, do one of the following:
If the snapshot does not have any sub-assets, click Replicate.
If the snapshot has sub-assets, a Snapshot Assets page is displayed. By default, all sub-assets are checked. Select the sub-assets you want to replicate and click Replicate.
- On the Replicate page, use the Target Destination drop-down list to select an alternate physical location.
For cross-account replication, ensure that you select a different AWS account where you want to replicate the snapshot to.
- Click Replicate.
- On the Please Confirm ... dialog box, click Replicate.
A message on the CloudPoint UI confirms that the replication job has been triggered. You can view the details of the replication job in the Job Log panel.
After the replication is completed, open the Asset Management pane to view the replicated snapshot. The Snapshot Details panel displays additional information such as the creation time, the type, and the source AWS account. The Replicated field value is displayed as Yes, indicating that it is a replicated snapshot.