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
Assigning a policy to an asset
After you create a policy, you assign it to one or more assets. For example, you can create a policy to create weekly snapshots and assign the policy to all your database applications. Also, an asset can have more than one policy. For example, in addition to weekly snapshots, you can assign a second policy to your database applications to snapshot them once a month.
Before you assign policies to assets, keep in mind the following:
The steps for assigning a policy are the same regardless of the type of asset you assign it to.
You can follow the same steps to change the policy that is associated with an asset or to un-assign a policy from an asset.
Do not assign a host-level protection policy to a disk asset. Doing so may lead to the creation of several unnamed snapshots that include snapshot of the disk itself, snapshot of the host to which that disk is attached, and snapshot of all the other disks that are attached to the host.
CloudPoint currently does not block you from assigning a host-level policy to a non-host entity such as a disk. But doing so can lead to unintended snapshot creation.
Do not assign a host-level policy to file system assets belonging to the same instance. CloudPoint currently does not block you from assigning a host-level policy to a file system asset, but doing so can lead to errors during snapshot creation.
For protecting file system and disk assets, always assign a disk-level protection policy; that is, a policy where the Storage Level option is set to Disk.
CloudPoint does not support running multiple operations on the same asset simultaneously. If you have an asset in multiple policies and the policy run times overlap, one of the policies may fail.
For example, suppose an asset is in both Policy 1 and Policy 2. If Policy 1 is running when Policy 2 starts, Policy 2 may fail. It takes an average of 10 minutes to create an Oracle snapshot. Allow at least a 10 minute gap between two policies that have the same asset.
Do not assign the policy to internal-only disk objects.
While installing and configuring agents and plug-ins on the protected hosts, CloudPoint creates internal volume objects that are required for performing CloudPoint operations. The CloudPoint UI incorrectly displays these internal-only volumes as disk assets and allows you to select these objects for snapshot and restore operations.
The objects appear as disk assets and are typically named as follows:
Disk /dev/<diskmount> on <hostname>.internal
To assign a policy to an asset
- On the CloudPoint dashboard, in the Environment area, find the asset type you want to protect, and click Manage. This example protects an application.
- On the Asset Management page, select the application you want to protect. On the Details page, click Policies.
- On the Policies for asset name screen assign one or more policies to the asset. In the Available Policies column, select the policy you want to assign and click Assign Selected.
You can also assign or remove multiple policies at the same time.
- Click Save.