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
 - 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 using the Docker image
 - 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 parameters
 - Pure Storage FlashArray plug-in configuration notes
 - HPE RMC plug-in configuration notes
 - Hitachi plug-in configuration notes
 - InfiniBox plug-in configuration notes
 - How to configure the CloudPoint storage array plug-ins?
 
 - CloudPoint application agents and plug-ins
- Microsoft SQL plug-in configuration notes
 - Oracle plug-in configuration notes
 - MongoDB 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
 - About snapshot restore
 - Restore requirements and limitations for Microsoft SQL Server
 - Restore requirements and limitations for Oracle
 - Restore requirements and limitations for MongoDB
 - 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 a MongoDB snapshot restore
 - Additional steps required after an Oracle snapshot restore
 - Additional steps required after restoring an AWS RDS database instance
 
 - Protecting assets with CloudPoint's agentless feature
 
 - Preparing for CloudPoint installation
 - Section II. CloudPoint maintenance
 
Granting password-less sudo access to host user account
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.