NetBackup™ Snapshot Manager for Data Center Administrator's Guide
- Introduction
- Preparing for NetBackup Snapshot Manager for Data Center installation
- Deploying NetBackup Snapshot Manager for Data Center using container images
- Upgrading NetBackup Snapshot Manager for Data Center
- Uninstalling NetBackup Snapshot Manager for Data Center
- Snapshot Manager for Data Center catalog backup and recovery
- Configure NetBackup Snapshot Manager for Data Center
- Storage array replication
- Storage array plug-ins for Snapshot Manager for Data Center
- Dell EMC PowerMax and VMax array
- Dell EMC PowerFlex array
- Dell EMC PowerScale (Isilon)
- Dell EMC PowerStore SAN and NAS plug-in
- Dell EMC XtremIO SAN array
- Dell EMC Unity Array
- Fujitsu Eternus AF/DX SAN array
- Fujitsu Eternus AB/HB SAN array
- HPE RMC plug-in
- HPE XP plug-in
- HPE Alletra 9000 SAN array
- HPE Alletra 6000 SAN array
- Hitachi NAS array
- Hitachi SAN array
- IBM Storwize SAN V7000 plug-in
- InfiniBox SAN array
- InfiniBox NAS array
- Lenovo DM 5000 series array
- NetApp Storage array
- NetApp E-Series array
- Nutanix Files array
- Pure Storage FlashArray SAN
- Pure Storage FlashBlade plug-in configuration notes
- PowerMax eNAS array
- Qumulo NAS array
- Configuring storage lifecycle policies for snapshots and snapshot replication
- Operation types in a storage lifecycle policy
- Retention types for storage lifecycle policy operations
- NetBackup Snapshot Manager logging
- Troubleshooting
How Fluentd-based NetBackup Snapshot Manager for Data Center logging works
When you install or upgrade NetBackup Snapshot Manager for Data Center, the following changes occur on the NetBackup Snapshot Manager for Data Center host:
A new container service named
flexsnap-fluentd
is started on the NetBackup Snapshot Manager for Data Center host. This service is started before all the other NetBackup Snapshot Manager for Data Center container services. Theflexsnap-fluentd
service serves as thefluentd
daemon on the host.All the NetBackup Snapshot Manager for Data Center 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 for Data Center logs are redirected for consumption.
Once all the infrastructure components are ready, each of the NetBackup Snapshot Manager for Data Center 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 for Data Center 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