NetBackup™ Snapshot Manager Install and Upgrade Guide
- Introduction
- Section I. NetBackup Snapshot Manager installation and configuration
- Preparing for NetBackup Snapshot Manager installation
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager extensions
- Installing the NetBackup Snapshot Manager extension on a VM
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (GKE) in GCP
- NetBackup Snapshot Manager cloud providers
- Configuration for protecting assets on cloud hosts/VM
- Protecting assets with NetBackup Snapshot Manager's on-host agent feature
- Installing and configuring NetBackup Snapshot Manager agent
- Configuring the NetBackup Snapshot Manager application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- Protecting assets with NetBackup Snapshot Manager's agentless feature
- NetBackup Snapshot Manager assets protection
- Volume Encryption in NetBackup Snapshot Manager
- NetBackup Snapshot Manager security
- Preparing for NetBackup Snapshot Manager installation
- Section II. NetBackup Snapshot Manager maintenance
- NetBackup Snapshot Manager logging
- Upgrading NetBackup Snapshot Manager
- Migrating and upgrading NetBackup Snapshot Manager
- Post-upgrade tasks
- Uninstalling NetBackup Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
How Fluentd-based NetBackup Snapshot Manager logging works
When you install or upgrade NetBackup Snapshot Manager, the following changes occur on the NetBackup Snapshot Manager host:
A new container service named
flexsnap-fluentd
is started on the NetBackup Snapshot Manager host. This service is started before all the other NetBackup Snapshot Manager container services. Theflexsnap-fluentd
service serves as thefluentd
daemon on the host.All the NetBackup Snapshot Manager container services are then started with
fluentd
as the Docker logging driver.A
fluentd
configuration file is created at/cloudpoint/fluent/fluent.conf
.This file contains the output plug-in definitions that are used to determine where the NetBackup Snapshot Manager logs are redirected for consumption.
Once all the infrastructure components are ready, each of the NetBackup Snapshot Manager 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 NetBackup Snapshot Manager 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.
Steps to configure log file rotate and log size command options
- In
/cloudpoint/flexsnap.conf
file, enter thelog_rotate_age
andlog_rotate_size
values under logging section and then restartflexsnap-fluentd
container for changes to take effect.Sample
flexsnap.conf
file:[logging] log_rotate_age = 7 log_rotate_size = 20000 ```
log_rotate_age: Specifies the generations to keep rotated log files (the total number of files that can be accumulated before rotation), the default value is 30.
log_rotate_size: Specifies the log file size (in bytes) after which a single log file will be rotated, the default value is 100000000 bytes.
- After changing the
flexsnap.conf
file, restart theflexsnap-fluentd
container:For docker environment: # sudo docker restart flexsnap-fluentd
For podman environment:
# sudo podman stop flexsnap-fluentd # sudo podman start flexsnap-fluentd