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
About the CloudPoint fluentd configuration file
Fluentd uses a configuration file that defines the source of the log messages, the set of rules and filters to use for selecting the logs, and the target destinations for delivering those log messages.
The fluentd daemon running on the CloudPoint host is responsible for sending the CloudPoint logs to various destinations. These target destinations, along with the other details such as input data sources and required fluentd parameters are defined in the plug-in configuration file. For CloudPoint, these plug-in configurations are stored in a fluentd configuration file that is located at /cloudpoint/fluent/fluent.conf on the CloudPoint host. The fluentd daemon reads the output plug-in definition from this configuration file to determine where to send the CloudPoint log messages.
The following output plug-in definitions are added to the configuration file by default:
STDOUTThis is used to send the CloudPoint log messages to
/cloudpoint/logs/flexsnap.log.The plug-in is defined as follows:
# Send to fluentd docker logs <store> @type stdout </store>
Additionally, the CloudPoint fluentd configuration file includes plug-in definitions for the following destinations:
MongoDB
Splunk
ElasticSearch
These plug-in definitions are provided as a template and are commented out in the file. To configure an actual MongoDB, Splunk, or ElasticSearch target, you can uncomment these definitions and replace the parameter values as required.