Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ Snapshot Manager for Data Center Administrator's Guide
  3. NetBackup Snapshot Manager logging
  4. How Fluentd-based NetBackup Snapshot Manager for Data Center logging works
NetBackup™ Snapshot Manager for Data Center Administrator's Guide

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. The flexsnap-fluentd service serves as the fluentd 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

  1. In /cloudpoint/flexsnap.conf file, enter the log_rotate_age and log_rotate_size values under logging section and then restart the flexsnap-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.

  2. After changing the flexsnap.conf file, restart the flexsnap-fluentd container:
    • For docker environment: # sudo docker restart flexsnap-fluentd

    • For podman environment:

      # sudo podman stop flexsnap-fluentd
      # sudo podman start flexsnap-fluentd

Feedback

Was this page helpful?
Previous

About NetBackup Snapshot Manager for Data Center logging mechanism

Next

About the NetBackup Snapshot Manager for Data Center fluentd configuration file

Feedback

Was this page helpful?