About NetBackup Snapshot Manager
You must deploy Snapshot Manager solution in your Kubernetes cluster environment. The Kubernetes cluster must be created with appropriate network and configuration settings. Before you deploy the solution, ensure that your environment meets the requirements.
See Prerequisites for Snapshot Manager (AKS/EKS).
Starting from NetBackup version 11.1, the fluent-bit sidecar has been removed from the datamover pod. Log collection for datamover pods will now be handled by a single, centralized fluent-bit sidecar running as part of the flexsnap-listener pod.
Benefits
Reduced resource usage (fewer sidecars per datamover instance).
Simplified log collection and management.
Consistent logging architecture across components.
Previous behavior (before 11.1 release)
Each datamover pod launched with its own fluent-bit sidecar.
This sidecar was responsible for collecting datamover logs and forwarding them to the collector pod.
Current behavior (from 11.1 release)
The per-pod fluent-bit sidecar has been removed.
A single fluent-bit sidecar, running continuously with the
flexsnap-listenerpod, now collects and forwards logs from all datamover pods.This implementation is similar to the existing fluent-bit sidecar setup used for NetBackup Primary and Media pods.
An abrupt restart of the listener service, along with the fluent-bit sidecar, while jobs are in progress can result in duplicate log entries being relayed to the fluent-bit collector.