Please enter search query.
Search <book_title>...
NetBackup™ Snapshot Manager Install and Upgrade Guide
Last Published:
2022-09-08
Product(s):
NetBackup & Alta Data Protection (10.1)
- Introduction
- Section I. NetBackup Snapshot Manager installation and configuration
- Preparing for NetBackup Snapshot Manager installation
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager extensions
- Installing the Snapshot Manager extension on a VM
- Installing the Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
- Installing the Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
- Installing the Snapshot Manager extension on a managed Kubernetes cluster (GKE) in GCP
- NetBackup Snapshot Manager cloud plug-ins
- NetBackup Snapshot Manager application agents and plug-ins
- Installing and configuring Snapshot Manager agent
- Configuring the Snapshot Manager application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- NetBackup protection plan
- Protecting assets with NetBackup Snapshot Manager's agentless feature
- Volume Encryption in NetBackup Snapshot Manager
- NetBackup Snapshot Manager security
- Preparing for NetBackup Snapshot Manager installation
- Section II. NetBackup Snapshot Manager maintenance
- NetBackup Snapshot Manager logging
- Upgrading NetBackup Snapshot Manager
- Uninstalling NetBackup Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
Modifying the fluentd configuration file
Modify the fluent.conf
configuration file if you want to modify the existing plug-in definitions.
To modify the fluent.conf file
- On the Snapshot Manager host, open the
/cloudpoint/fluent/fluent.conf
configuration file in a text editor of your choice and then edit the contents to add or remove a plug-in definition. - Save all the changes to the file.
- Restart the
flexsnap-fluentd
container service using the following command:# sudo docker restart flexsnap-fluentd
Note that the changes take effect immediately and are applicable only to the newer log messages that get generated after the change. The file changes do not apply to the older logs that were generated before the configuration file was updated.