Veritas CloudPoint Administrator's Guide
- Getting started with CloudPoint
- Section I. Installing and configuring CloudPoint
- Preparing for installation
- 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
- HPE RMC plug-in configuration notes
- NetApp plug-in configuration notes
- Hitachi plug-in configuration notes
- InfiniBox plug-in configuration notes
- About CloudPoint plug-ins and assets discovery
- Configuring the on-host agents and plug-ins
- Oracle plug-in configuration notes
- 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
- Managing your assets
- About snapshot restore
- Single file restore requirements and limitations
- Additional steps required after a SQL Server snapshot restore
- Monitoring activities with notifications and the job log
- Protection and disaster recovery
- Section IV. Maintaining CloudPoint
- CloudPoint logging
- Troubleshooting CloudPoint
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Additional steps required after restoring disk-level snapshots
When you trigger an application or file system's disk-level snapshot restore using the Original location option, CloudPoint creates new disks from the disk snapshot, detaches the original disks from the host, and attaches the new disks to the host. The original disk assets get deleted automatically.
If you had assigned any CloudPoint policies to those original disks, then the policy association is lost after the restore. The policies do not automatically apply to the newly restored disks. The restored disk assets are no longer being protected by the respective CloudPoint policies.
This is applicable even if you perform a host-level restore. When you restore a host-level snapshot using the Overwrite existing option, the policy that is assigned to the host remains attached to the newly created host. However, any policy that is attached to the application, disk, or file system asset that belongs to that host is no longer associated with the asset, after the host-level restore.
Perform the following step after the restore:
You must manually reassign the respective policies to each of the disk-level assets after the restore operation is completed successfully.