Please enter search query.
Search <book_title>...
NetBackup™ Web UI Kubernetes Administrator's Guide
Last Published:
2024-03-27
Product(s):
NetBackup & Alta Data Protection (10.4)
- Overview of NetBackup for Kubernetes
- Deploying and configuring the NetBackup Kubernetes operator
- Configure settings for NetBackup snapshot operation
- Deploying certificates on NetBackup Kubernetes operator
- Managing Kubernetes assets
- Managing Kubernetes intelligent groups
- Protecting Kubernetes assets
- Managing image groups
- Protecting Rancher managed clusters in NetBackup
- Recovering Kubernetes assets
- About incremental backup and restore
- Enabling accelerator based backup
- Enabling FIPS mode in Kubernetes
- Troubleshooting Kubernetes issues
Controlling disk space for track logs on primary server
To proceed with an accelerator enabled backup, NetBackup anticipates a disk-full situation due to track log processing. Accelerator track logs on the primary server can become a problem with less free space.
By default, NetBackup prevents an accelerator backup, if there is less than 5 GB or 5% of free space on the system.
NetBackup provides two configuration settings to control the amount of free disk space on a host for an accelerator backup to start:
ACCELERATOR_TRACKLOG_FREE_SPACE_MB
ACCELERATOR_TRACKLOG_FREE_SPACE_PERCENT
The default value for each setting is 5120 MB and 5%, respectively. These values can be setup on the primary bp.conf for the backup to fail fast in case of insufficient space.