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
Prerequisites for the agentless configuration
Have the following information with you:
Host user name
Host password or SSH key
CloudPoint requires these details to gain access to the host and perform requested operations.
On hosts where you wish to configure this feature, grant password-less sudo access to the host user account that you provide to CloudPoint.
CloudPoint requires a host user account to connect and perform operations on the host. You must grant password-less sudo access to the user account that you provide to CloudPoint. This is required for all the hosts where you wish to configure the agentless feature.
Note:
The following steps are provided as a general guideline. Refer to the operating system or the distribution-specific documentation for detailed instructions on how to grant password-less sudo access to a user account.
Perform the following steps on a host where you want to configure the agentless feature
Verify that the host user name that you provide to CloudPoint is part of the
wheelgroup.Log on as a root user and run the following command:
# usermod -aG wheel hostuserID
Here, hostuserID is the host user name that you provide to CloudPoint.
Log out and log in again for the changes to take effect.
Edit the
/etc/sudoersfile using the visudo command:# sudo visudo
Add the following entry to the
/etc/sudoersfile:hostuserID ALL=(ALL) NOPASSWD: ALLIn the
/etc/sudoersfile, edit the entries for thewheelgroup as follows:Comment out (add a # character at the start of the line) the following line entry:
# %wheel ALL=(ALL) ALL
Uncomment (remove the # character at the start of the line) the following line entry:
%wheel ALL=(ALL) NOPASSWD: ALL
The changes should appear as follows:
## Allows people in group wheel to run all commands # %wheel ALL=(ALL) ALL ## Same thing without a password %wheel ALL=(ALL) NOPASSWD: ALL
Save the changes to the
/etc/sudoersfile.Log out and log on to the host again using the user account that you provide to CloudPoint.
Run the following command to confirm that the changes are in effect:
# sudo su
If you do not see any prompt requesting for a password, then the user account has been granted password-less sudo access.
You can now proceed to configure the CloudPoint agentless feature.
The user account used to connect to remote instance should be able to:
Access remote admin share (ADMIN$). Enabled by default.
Access to
root\cimv2
Configure the following ports:
Modify the security group to allow inbound traffic on the ports 135, 445 and dynamic port or fixed port for WMI .
Enable inbound rules in the firewall for the ports 135, 445 and the dynamic or fixed WMI-IN ports on Windows hosts.
Note:
The dynamic range for the ports is 49152-65535.
You can use fixed or dynamic WMI-IN ports. If you want to configure a fixed WMI-IN port, see https://docs.microsoft.com/en-us/windows/win32/wmisdk/setting-up-a-fixed-port-for-wmi
Disable User Account Control for the users groups accessing the agentless feature.
For protecting SQL applications, the user account used for connecting to the cloud host, must have the required admin privileges to access the SQL server.