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
- Hitachi plug-in configuration notes
- InfiniBox 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 restoring disk-level snapshots
- 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
- Swagger UI-based authorization for CloudPoint REST API calls may fail
- Policy retention count is not honored for file system and application assets if there is an issue with the CloudPoint plug-in
- Working with your CloudPoint license
- Managing CloudPoint agents and plug-ins
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Section V. Reference
Creating a policy
To create a policy
- On the dashboard, in the Administration widget, locate Policies, and click Manage.
- On the Policies page, click New Policy.
- Complete the New Policy page.
Enter the following:
Policy Information
Name and describe the policy, and enable features.
Field
Description
Policy Name
Enter a name for the policy.
The name can contain 2 to 12 characters. The name can only contain lower case letters, numbers, and hyphens. The name should begin with a letter.
Notes:
In Google Cloud, a policy name cannot contain an underscore.
If policy contains any on-premise array disk, then the policy name must be a 2 to 12 character string.
In case of a Pure Storage array, the policy name must also not contain an underscore.
Description
(optional)
A short description to remind you about what the policy does.
Storage level
The level at which the snapshot is taken: Disk, Host, Application, or Share (applicable to NetApp).
Application Consistent
Click the check box to enable application-consistent snapshots.
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.
This option is not available with the CloudPoint Freemium license.
Note:
CloudPoint does not support application-consistent snapshots on ext2 file systems.
Enable Replication
Click the check box to enable replication.
Retention
Use the retention parameter to define how many copies of the asset snapshots to create and for how long you wish to keep them. You can choose to retain the snapshot copies for days, weeks, months, or years.
After the retention period expires, CloudPoint automatically deletes all the snapshots and their replicated copies.
Note:
Use careful planning and consideration when using this parameter. The retention period applies to the policy-created snapshot copies as well as the replicated snapshot copies that are stored at a different location than the source. All the snapshots are completely lost and you will not have access to them after they are deleted.
The following table shows some sample settings.
Number
Tab
Description
5
Copies
Retains the last five snapshots.
Note:
An asset may have more total snapshots than the number specified here. If an asset is associated with multiple policies, it has snapshots with each policy. Also, the snapshots you create manually do not count toward the retention total. Manual snapshots are not automatically deleted.
7
Days
Retains all snapshots for a week.
3
Months
Retains all snapshots for 3 months.
Scheduling
Use this part of the page to determine how often the policy runs.
Tab
Description
Hourly
Specify the hour or minute interval at which the policy runs.
Daily
Click the clock icon to specify the time the policy runs each day.
Weekly
Use the clock icon and day buttons to specify the day of the week and the time the policy runs.
Monthly
Use the clock icon and calendar to specify the time and the date each month on which the policy runs.
The following example takes application consistent snapshots each Monday at 12:00 AM. CloudPoint retains four snapshots before it discards the oldest one.
- Click Save.
CloudPoint displays a message that the new policy is created.
- The Policies page displays all the policies that are created.