Veritas NetBackup™ CloudPoint Install and Upgrade Guide
- Section I. CloudPoint installation and configuration
- Preparing for CloudPoint installation
- About the deployment approach
- Deciding where to run CloudPoint
- About deploying CloudPoint in the cloud
- Meeting system requirements
- CloudPoint host sizing recommendations
- CloudPoint extension sizing recommendations
- Creating an instance or preparing the host to install CloudPoint
- Installing container platform (Docker, Podman)
- Creating and mounting a volume to store CloudPoint data
- Verifying that specific ports are open on the instance or physical host
- Preparing CloudPoint for backup from snapshot jobs
- Deploying CloudPoint using container images
- Deploying CloudPoint extensions
- Before you begin installing CloudPoint extensions
- Downloading the CloudPoint extension
- Preparing to install the extension on a VM
- Installing the CloudPoint extension on a VM
- Preparing to install the extension on a managed Kubernetes cluster (AKS) in Azure
- Preparing to install the extension on a managed Kubernetes cluster (EKS) in AWS
- Install extension using the Kustomize and CR YAMLs
- Installing the CloudPoint extension on Azure (AKS)
- Installing the CloudPoint extension on AWS (EKS)
- Managing the extensions
- CloudPoint cloud plug-ins
- CloudPoint storage array plug-ins
- How to configure the CloudPoint storage array plug-ins?
- NetApp plug-in configuration notes
- ACL configuration on NetApp array
- Nutanix Files plug-in configuration notes
- Configuring ACL for Nutanix array
- Dell EMC Unity array plug-in configuration notes
- FUJITSU AF/DX plug-in configuration notes
- NetApp NAS plug-in configuration notes
- Dell EMC PowerStore plug-in configuration notes
- Dell EMC PowerStore NAS plug-in configuration notes
- Dell EMC PowerFlex plug-in configuration notes
- Dell EMC XtremIO SAN plug-in configuration notes
- Pure Storage FlashArray plug-in configuration notes
- Pure Storage FlashBlade plug-in configuration notes
- IBM Storwize plug-in configuration notes
- HPE RMC plug-in configuration notes
- HPE XP plug-in configuration notes
- Hitachi plug-in configuration notes
- Hitachi (HDS VSP 5000) plug-in configuration notes
- InfiniBox plug-in configuration notes
- Dell EMC PowerScale (Isilon) plug-in configuration notes
- Dell EMC PowerMax and VMax plug-in configuration notes
- Qumulo plug-in configuration notes
- CloudPoint application agents and plug-ins
- Microsoft SQL plug-in configuration notes
- Oracle plug-in configuration notes
- About the installation and configuration process
- Preparing to install the Linux-based agent
- Preparing to install the Windows-based agent
- Downloading and installing the CloudPoint agent
- Registering the Linux-based agent
- Registering the Windows-based agent
- Configuring the CloudPoint application plug-in
- Configuring VSS to store shadow copies on the originating drive
- Creating a NetBackup protection plan for cloud assets
- Subscribing cloud assets to a NetBackup protection plan
- Restore requirements and limitations for Microsoft SQL Server
- Restore requirements and limitations for Oracle
- Additional steps required after an Oracle snapshot restore
- Steps required before restoring SQL AG databases
- Recovering a SQL database to the same location
- Recovering a SQL database to an alternate location
- Additional steps required after a SQL Server snapshot restore
- Additional steps required after restoring SQL AG databases
- SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the CloudPoint host
- Disk-level snapshot restore fails if the original disk is detached from the instance
- Additional steps required after restoring an AWS RDS database instance
- Protecting assets with CloudPoint's agentless feature
- Volume Encryption in NetBackup CloudPoint
- CloudPoint security
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
- CloudPoint logging
- Upgrading CloudPoint
- Uninstalling CloudPoint
- Preparing to uninstall CloudPoint
- Backing up CloudPoint
- Unconfiguring CloudPoint plug-ins
- Unconfiguring CloudPoint agents
- Removing the CloudPoint agents
- Removing CloudPoint from a standalone Docker host environment
- Removing CloudPoint extensions - VM-based or managed Kubernetes cluster-based
- Restoring CloudPoint
- Troubleshooting CloudPoint
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 NetBackup 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.
Note:
These steps are applicable only in case of a SQL Server instance snapshot restore to a new location. These are not applicable for a SQL Server database snapshot restore.
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.
- Assign drive letters to the volumes on the disk that you brought online in the earlier step. Drive letters are required to view the shadow copies associated with each volume on the disk.
Go back to the command prompt window and perform the following steps:
View the list of volumes on the new host using the following command:
list volume
From the list of volumes displayed, identify the volume for which you want to assign, modify, or remove a drive letter.
Select the desired volume using the following command:
select volume <volnumber>
Here, <volnumber> represents the volume that you noted in the earlier step.
Assign a drive letter to the selected volume using the following command:
assign letter=<driveletter>
Here, <driveletter> is the drive letter that you wish to assign to the volume. Ensure that the specified drive letter is not already in use by another volume.
Repeat these steps to assign a drive letter to all the SQL Server volumes on the disk.
- 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 NetBackup.