Veritas NetBackup™ CloudPoint Install and Upgrade Guide
- Section I. CloudPoint installation and configuration
- Preparing for CloudPoint installation
- CloudPoint host sizing recommendations
- Deploying CloudPoint using container images
- Deploying CloudPoint extensions
- Installing the CloudPoint extension on AWS (EKS)
- CloudPoint cloud plug-ins
- CloudPoint storage array plug-ins
- NetApp plug-in configuration notes
- Nutanix Files plug-in configuration notes
- 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
- Oracle plug-in configuration notes
- Additional steps required after a SQL Server snapshot restore
- 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
- 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
wheel
group.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/sudoers
file using the visudo command:# sudo visudo
Add the following entry to the
/etc/sudoers
file:hostuserID ALL=(ALL) NOPASSWD: ALL
In the
/etc/sudoers
file, edit the entries for thewheel
group 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/sudoers
file.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.