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
- How to configure the 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
- Dell EMC PowerScale (Isilon) 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
- 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
- Volume Encryption in NetBackup
- Preparing for CloudPoint installation
- Section II. CloudPoint maintenance
- CloudPoint logging
- Troubleshooting CloudPoint
- Restarting CloudPoint
- Troubleshooting CloudPoint logging
- CloudPoint agent fails to connect to the CloudPoint server if the agent host is restarted abruptly
- CloudPoint agent registration on Windows hosts may time out or fail
- Disaster recovery when DR package is lost or passphrase is lost
- Agentless log file name changed
- Upgrading CloudPoint
- Uninstalling CloudPoint
Oracle plug-in configuration notes
You can configure the Oracle plug-in to discover and protect your Oracle database applications with disk-level snapshots.
Before you configure the Oracle plug-in, make sure that your environment meets the following requirements:
A supported version of Oracle is installed in a supported Red Hat Enterprise Linux (RHEL) host environment.
Oracle standalone instance is discoverable.
Oracle binary and Oracle data must be on separate volumes.
Log archiving is enabled.
The
db_recovery_file_dest_sizeparameter size is set as per Oracle recommendation.Refer to the Oracle documentation for more information:
https://docs.oracle.com/cd/B19306_01/backup.102/b14192/setup005.htm
The databases are running, mounted, and open.
CloudPoint supports discovery and snapshot operations on databases that are in a backup mode. After taking snapshots, the state of the databases is retained as is; CloudPoint does not change the status of such databases. However, in-place restore for such databases is not supported.