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
CloudPoint fails to revert restored snapshots if indexing, classification, or restore operations fail
When you trigger CloudPoint operations such as indexing, classification, and restore (full snapshot restore, single file restore, or application restore), CloudPoint first attaches the snapshot to the CloudPoint host (in case of indexing and classification) or to the target host (in case of snapshot restore) and then performs the operation. The snapshot is detached from the host once the operation is completed successfully.
Sometimes, these CloudPoint operations might fail due to an internal workflow error, an unknown exception, or an unlikely error scenario. In such failure cases, it is observed that CloudPoint is unable to detach the snapshot that was exported on the host for performing the operation. The snapshot remains attached to the host, even if the operation itself has failed. As a result, you may not be able to trigger any subsequent indexing, classification, or restore operations. Even if you are able to initiate these operations, they remain in a queued state and may eventually fail.
Workaround:
If you encounter such an issue, you may have to manually detach the snapshot from the host. This will ensure that subsequent indexing, classification, or restore jobs do not fail.
Perform the following steps on the CloudPoint host:
Check if the restored snapshot file system is mounted on the CloudPoint host. If it is mounted, unmount the file system from the host.
Check if the restored snapshot disk is attached to the CloudPoint host. If it is attached, detach the volume from the host.
Check if the restored snapshot volume is visible in the cloud. If it is available, delete that volume using the cloud management console.
Perform the following steps on the Linux host:
Check if the restored snapshot file system is mounted on the Linux host. If it is mounted, unmount the file system from the host.
Check if the restored snapshot disk is attached to the Linux host. If it is attached, detach the volume from the host using the cloud management console.
Check if the restored snapshot volume is visible in the cloud. If it is available, delete that volume using the cloud management console.
Perform the following steps on the Windows host:
Check if the restored snapshot volume is mounted on the Windows host. If it is mounted, unmount the volume from the host.
Check if the restored snapshot disk is attached to the Windows host. If it is attached, take the disk offline using the diskpart command line utility or from the Windows Computer Management UI.
Verify that the restored snapshot disk is offline on the Windows host, and then detach the volume from the host.
Check if the restored snapshot volume is visible in the cloud. If it is available, delete that volume using the cloud management console.