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
 
Before you create a cross account configuration
For CloudPoint cross account configuration, you need to perform the following additional tasks before you can create the configuration:
Create a new IAM role in the other AWS account (target account)
Create a new policy for the IAM role and ensure that it has required permissions to access the assets in that target AWS account
Establish a trust relationship between the source and the target AWS accounts
In the source AWS account, create a policy that allows the IAM role in the source AWS account to assume the IAM role in the target AWS account
In the target AWS account, set the maximum CLI/API session duration to 1 hour, at a minimum
Perform the following steps:
- Using the AWS Management Console, create an IAM role in the additional AWS account (the target account) whose assets you want to protect using CloudPoint.
While creating the IAM role, select the role type as Another AWS account.
 - Define a policy for the IAM role that you created in the earlier step.
Ensure that the policy has the required permissions that allow the IAM role to access all the assets (EC2, RDS, and so on) in the target AWS account.
 - Set up a trust relationship between the source and target AWS accounts.
In the target AWS account, edit the trust relationship and specify source account number and source account role.
This action allows only the CloudPoint instance hosted in source AWS account to assume the target role using the credentials associated with source account's IAM role. No other entities can assume this role.
 - Grant the source AWS account access to the target role.
In the source AWS account, from the account Summary page, create an inline policy and allow the source AWS account to assume the target role (
"sts:AssumeRole"). - From the target account's Summary page, edit the Maximum CLI/API session duration field and set the duration to 1 hour, at a minimum.
This setting determines the amount of time for which the temporary security credentials that the source account IAM role gets when it assumes target account IAM role remain valid.