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
Creating a snapshot manually
One of CloudPoint's most important features is the ability to create snapshot policies. These policies let you take snapshots of specific assets on a regular schedule.
However, you can also take a snapshot of an asset manually. That is, you can navigate to a particular asset at any time and create a snapshot.
The types of snapshots you can create vary depending on the asset type. Review the following table:
Table: Assets and supported snapshot types
Asset | Supported snapshot types |
|---|---|
Dell EMC Unity array | Copy-on-write (COW) snapshots on LUNs |
HPE storage arrays | COW and clone snapshot types Note the following:
|
Pure Storage FlashArray | Clone snapshots of volumes |
NetApp storage arrays | COW snapshots of LUNs (SAN deployment) or NetApp NFS shares (NAS deployment) |
Before you proceed, keep in mind the following:
Regardless of the asset type you work with, the steps for creating a snapshot are the same. Depending on the asset, some parameters you enter may be slightly different. They are explained in the procedure.
CloudPoint does not support running multiple operations on the same asset simultaneously. You can perform only one operation at any given time. If multiple operations are submitted for the same asset, then only the first operation is triggered and the remaining operations will fail.
To create 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 example creates an application snapshot.
- On the Asset Management page, select the application for which you want to create a snapshot.
- On the asset's Details page, click Create Snapshot
- On the Create Snapshot page, complete the following fields.
Field
Description
Snapshot name
A 2- to 32-character string.
Cloud vendors have additional restrictions on the snapshot name.
In Amazon Web Services, an RDS snapshot or Aurora cluster snapshot name has the following restrictions:
The name cannot be null, empty, or blank.
The first character must be a letter.
The name cannot end with a hyphen or contain two consecutive hyphens.
In Google Cloud, an application snapshot name has the following restrictions:
The name can only contain lower case letters, numbers, and hyphens. You cannot use an underscore.
The name should begin and end with a letter.
Description
This field is optional. You can create a summary to remind you of the snapshot content.
Storage level
This option only displayed for application snapshots.
host takes a snapshot of all the disks that are associated with the instance. You cannot restore an application snapshot that has the host protection level.
disk takes a snapshot of the disks the application uses.
Applicaiton Consistent
Click this option to enable an application-consistent snapshot.
In an application consistent snapshot, CloudPoint notifies the application that it is about to take a snapshot. The application completes its transactions and writes data to memory. It is then briefly frozen and CloudPoint takes the snapshot. The application resumes activity after the snapshot is taken.
The default is to create a crash-consistent snapshot. This snapshot type does not capture data in memory or pending operations. An application-consistent snapshot is recommended for database applications. A crash-consistent snapshot is acceptable for other types of assets
Note:
CloudPoint does not support application-consistent snapshots on ext2 file systems.
The following example creates a disk level snapshot with application consistency.
- Click Save.
CloudPoint displays a message that the snapshot is created.
By default, AWS allows up to a 100 RDS manual snapshots per region. You may get an error if you try to take more than a 100 snapshots.
https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Limits.html#RDS_Limits.Limits
You can work around this issue using any of the following options:
Contact AWS support and request them for an increase in the number of snapshots allowed. Once they do that, you will not get an error until you reach the new limit.
Reduce the retention in your policies so as to keep the snapshots count within the maximum limit.