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
How Fluentd-based CloudPoint logging works
When you install or upgrade CloudPoint, the following changes occur on the CloudPoint host:
A new container service named
flexsnap-fluentdis started on the CloudPoint host. This service is started before all the other CloudPoint container services. Theflexsnap-fluentdservice serves as thefluentddaemon on the host.All the CloudPoint container services are then started with
fluentdas the Docker logging driver.A
fluentdconfiguration file is created at/cloudpoint/fluent/fluent.conf.This file contains the output plug-in definitions that are used to determine where the CloudPoint logs are redirected for consumption.
Once all the infrastructure components are ready, each of the CloudPoint services begin to send their respective log messages to the configured Docker fluentd logging driver. The fluentd daemon then redirects the structured logs to the output plug-ins configured in the fluentd configuration file. These logs are then sent to the /cloudpoint/logs/flexsnap.log file on the CloudPoint host.
Note that the flexsnap.log file gets rotated after the file size reaches a maximum of 100 MB. A total of 30 generations (rotated files) of the flexsnap.log file are maintained. These conditions are applicable because of the new log file rotate (log-rotate-age) and log size (log-rotate-size) command options that are introduced in the fluentd command.