Search <book_title>...

NetBackup™ Deployment Guide for Kubernetes Clusters

Last Published: 2025-03-18

Product(s): NetBackup & Alta Data Protection (11.0)

Parameters for logging (fluentbit)

The logging feature is introduced in NetBackup 10.5 to to consolidate log files that have been distributed during the process of running NetBackup in a scale-out environment. To configure the fluentbit, ensure that the following prerequisites are met:

Prerequisites for logging fluentbit)

Ensure that the following system requirements and prerequisites are met before proceeding with the deployment:

System requirements: Cloud Scale deployment environment only
Application requirements: Cloud Scale fluentbit pods and containers:
- Fluentbit collector pod and containers
- Fluentbit DaemonSet sender pods and containers
- Fluentbit sidecar sender containers

To view the current values, execute the command:

helm get values fluentbit -n <netbackup namespace>

To apply the new values of fluentbit, execute the command:

helm upgrade --install fluentbit <fluentbit .tgz> -f new-values.yaml -n <netbackup namespace>

Table: Fluentbit collector configuration variables

Configuration value	Description
fluentbit.volume.pvcStorage	This is the size of the PVC created for the fluentbit collector to store logs.
collectorNodeSelector	This is how you can set the node selector for the fluentbit collector pod.

Table: Log Cleanup configuration variables

Configuration value	Description
fluentbit.volume.pvcStorage	This parameter describes the size of the PVC created for the fluentbit collector to store logs.
fluentbit.cleanup.retentionDays	(number of days) - Number of days to retain logs before cleaning them up. For example1 would mean 1 day which would mean that if the logs were created the day before they are to be kept that 1 day and no cleanup would occur. The next day the logs are 2 days old and with a setting of 1 they would be cleaned up. Default: retentionDays: 7
fluentbit.cleanup.retentionCleanupTime	(hh:mm) - Time of day to cleanup the logs. This is based on the local Kubernetes time zone. The retention cleanup occurs once daily. Default: retentionCleanupTime: 04:00
fluentbit.cleanup.utilizationCleanupFrequency	(number of minutes) - Number of minutes to wait between subsequent utilization cleanups. This is based on start time of the previous cleanup, not when the cleanup finishes. Default: utilizationCleanupFrequency: 60
fluentbit.cleanup.highWatermark	(number percent) - This is the percentage of storage utilization that the utilization cleanup will start cleaning up data one day at a time. It will continue until it reaches the low watermark or only the current days logs remain. If only current days logs remain it will start cleaning up individual files of the current day based on last updated time. Default: highWatermark: 90
fluentbit.cleanup.lowWatermark	(number percent) - This is the percentage of storage utilization that the utilization cleanup will stop cleaning up data once it gets below. Default: lowWatermark: 60
fluentbit.namespaces	This is a list of namespaces to collect stdout logs from. This is designed to allow you to filter out cluster logs and other logs not related to the NetBackup system in order to reduce network traffic and focus on relevant logs. Default: netbackup, netbackup-operator-system

Table: Fluentbit DaemonSet configuration variables

Configuration value	Description
tolerations	This is where you can set the tolerations of the daemonset pods to help determine which nodes they should be scheduled to.

Table: Resizing Log Volumes

Configuration value	Description
Resize Log Volumes: It is important that all the non-collector log volumes must remain the same size. This is because they are all using a common variable in the bp.conf file to determine when to be cleaned up and how much size to use.	Except for the primary server, perform this action on every log volume. It opens the edit menu that allows you to change the volume size and save. Upon saving it takes few minutes to resize the volume. In order to resize the log volumes you must run the command: $ kubectl edit pvc -n <netbackup namespace> <pvc name> To resize the primary volume run: $ kubectl edit environment -n <netbackup namespace> <netbackup environment name> It opens an edit menu where you can change the value of spec.primary.storage.log.capacity to a new value (which must be higher). The new values take a few minutes to apply but it will change the log volume size as well as edit the associated bp.conf value. After executing the edit command, run the delete command to restart the pod. kubectl delete pod -n <netbackup namespace> <application pod name>

Configuration value

Description

Resize Log Volumes:

It is important that all the non-collector log volumes must remain the same size. This is because they are all using a common variable in the bp.conf file to determine when to be cleaned up and how much size to use.

Except for the primary server, perform this action on every log volume. It opens the edit menu that allows you to change the volume size and save. Upon saving it takes few minutes to resize the volume. In order to resize the log volumes you must run the command:
$ kubectl edit pvc -n <netbackup namespace> <pvc name>
To resize the primary volume run:
$ kubectl edit environment -n <netbackup namespace> <netbackup environment name>
It opens an edit menu where you can change the value of spec.primary.storage.log.capacity to a new value (which must be higher). The new values take a few minutes to apply but it will change the log volume size as well as edit the associated bp.conf value.
After executing the edit command, run the delete command to restart the pod.
kubectl delete pod -n <netbackup namespace> <application pod name>