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
- About CloudPoint support for AWS IAM roles
- About the CloudPoint AWS CloudFormation template
- 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
- Setting up email and adding users
- Assigning roles to users for greater efficiency
- 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
- Storage array support
- Dell EMC Unity arrays
- Pure Storage FlashArray
- Working with CloudPoint using APIs
- Storage array support
About snapshot restore
The types of snapshots you can restore and where you can restore them varies depending on the asset type.
Table: Assets and supported restore options
Supported restore options
Dell EMC Unity array
Restore a copy-on-write (COW) LUN snapshot to the same LUN with theoption.
HPE storage arrays
Restore a COW volume snapshot to the same volume with theoption.
Pure Storage FlashArray
Restore a clone volume snapshot to the same volume with theoption.
NetApp storage arrays
Restore the LUN snapshot to the same LUN (SAN deployment) or restore the NetApp NFS shares (NAS deployment).
Hitachi storage arrays
Restore the LDEV snapshot to the same LDEV with theoption.
InfiniBox storage arrays
Restore the SAN volume snapshot to the same volume with theoption.
When you restore a snapshot, keep in mind the following:
You can restore an encrypted snapshot. To enable the restoring of encrypted snapshots, add a Key Management Service (KMS) policy, and grant the CloudPoint user access to KMS keys so that they can restore encrypted snapshots.
If you are restoring a replicated host snapshot to a location that is different from the source region, then the restore might fail as the key is not available at the target location.
As a prerequisite, create a key-pair with the same name as the source of the snapshot, or import the key-pair from the source to the target region.
Then, after the restore is successful, change the security groups of the instance from the network settings for the instance.
When you have created a snapshot of a disk of supported storage arrays from 'Disk' section in CloudPoint dashboard, which has a file system created and mounted on it, you must first stop any application that is using the file system and then unmount the file system and perform restore.
For AWS/Azure/GCP cloud disk/volume snapshots, you must first detach the disk from the instance and then restore the snapshot to original location.
(Applicable to AWS only) When you restore a host-level application snapshot, the name of the new virtual machine that is created is the same as the name of the host-level snapshot that corresponds to the application snapshot.
For example, when you create an application snapshot named
OracleAppSnap, CloudPoint automatically creates a corresponding host-level snapshot for it named
OracleAppSnap-<number>. For example, the snapshot name may resemble
Now, when you restore the application snapshot (
OracleAppSnap), the name of the new VM is
Using the example cited earlier, the new VM name may resemble
OracleAppSnap-15 (restored Nov 20 2018 09:24).
Note that the VM name includes "Oracle-AppSnap-15" which is the name of the host-level snapshot.
(Applicable to AWS only) When you restore a disk-level application snapshot or a disk snapshot, the new disk that is created does not bear any name. The disk name appears blank.
You have to manually assign a name to the disk to be able to identify and use it after the restore.
When you restore a snapshot of a Windows instance, you can log in to the newly restored instance using original instance's username/password/pem file.
By default, AWS disables generating a random encrypted password after launching the instance from AMI. You must set Ec2SetPassword to
config.xmlto generate new password every time. For more information on how to set the password, see the following link.
The volume type of newly created volumes for replicated snapshots is according to the region's default volume type.
If volume type is not specified, the following default values are used:
Table: Default volume types
Default volume type
us-east-1, eu-west-1, eu-central-1, us-west-1, us-west-2
ap-northeast-1, ap-northeast-2, ap-southeast-1, ap-southeast-2, ap-south-1
sa-east-1, us-gov-west-1, cn-north-1
All other regions
If you are performing a disk-level snapshot restore to the same location, then verify that the original disk is attached to the instance, before you trigger a restore.
If the existing original disk is detached from the instance, then the restore operation might fail.
You can perform only one restore operation on a snapshot at any given time. If multiple operations are submitted on the same asset, then only the first operation is triggered and the remaining operations will fail.
This is applicable for all CloudPoint operations in general. CloudPoint does not support running multiple jobs on the same asset simultaneously.
If you intend to restore multiple file systems or databases on the same instance, then Veritas recommends that you perform these operations one after the other, in a sequential manner.
Running multiple restore operations in parallel can lead to an inconsistency at the instance level and the operations might fail eventually.
If a region or zone is removed from the AWS or GCP plug-in configuration, then all the discovered assets from that region or zone are also removed from the CloudPoint assets database. If there are any active snapshots that are associated with the assets that get removed, then you may not be able perform any restore operations on those snapshots.
Once you add that zone back into the plug-in configuration, CloudPoint discovers all the assets again and you can resume the restore operations on the associated snapshots.