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
Steps required after a SQL Server disk-level snapshot restore to new location
Perform these steps after you have restored a disk-level SQL Server snapshot from the CloudPoint UI. These steps are required only if the snapshot is restored to a new location. New location refers to a new host that is different from the one where the SQL instance is running.
Perform the following steps
- Connect to the new Windows host where the SQL Server instance is running.
Ensure that you use an account that has administrator privileges on the host.
- Open a command prompt window. If Windows UAC is enabled on the host, open the command prompt in the Run as administrator mode.
- Start the diskpart utility using the following command:
diskpart
- View the list of disks on the new host using the following command:
list disk
Identify the new disk that is attached due to the snapshot restore operation and make a note of the disk number. You will use it in the next step.
- Select the desired disk using the following command:
select disk <disknumber>
Here, <disknumber> represents the disk that you noted in the earlier step.
- View the attributes of the selected disk using the following command:
attributes disk
The output displays a list of attributes for the disk. One of the attributes is
read-only, which we will modify in the next step. - Modify the read-only attribute for the selected disk using the following command:
attributes disk clear readonly
This command changes the disk to read-write mode.
- Bring the disk online.
From the Windows Server Manager console, navigate to Files and Storage Devices > Disks and then right click on the newly attached disk and select Bring online.
- Quit the diskpart utility using the following command:
exit
Do not close the command prompt yet; you can use the same window to perform the remaining steps described in the next section.
Perform the following steps
- From the same command window used earlier, start the diskshadow command interpreter in the interactive mode using the following command:
diskshadow
- View the list of all the shadow copies that exist on the new host. Type the following command:
list shadows all
Identify the shadow copy that you want to use for the revert operation and make a note of the shadow copy ID. You will use the shadow ID in the next step.
- Revert the volume to the desired shadow copy using the following command:
revert <shadowcopyID>
Here, <shadowcopyID> is the shadow copy ID that you noted in the earlier step.
- Exit the DiskShadow utility using the following command:
exit
Perform the following steps:
- Ensure that the disk-level snapshot restore operation has completed successfully and a new disk is created and mounted on the application host.
- Log on to Microsoft SQL Server Management Studio as a database administrator.
- From the Object Explorer, connect to an instance of the SQL Server Database Engine and then click to expand the instance view.
- In the expanded instance view, right-click Databases and then click Attach.
- In the Attach Databases dialog box, click Add and then in the Locate Database Files dialog box, select the disk drive that contains the database and then find and select all the .mdf and .ldf files associated with that database. Then click OK.
The disk drive you selected should be the drive that was newly created by the disk-level snapshot restore operation.
- Wait for the requested operations to complete and then verify that the database is available and is successfully discovered by CloudPoint.