NetBackup™ Snapshot Manager Install and Upgrade Guide
- Introduction
- Section I. NetBackup Snapshot Manager installation and configuration
- Preparing for NetBackup Snapshot Manager installation
- Meeting system requirements
- Snapshot Manager host sizing recommendations
- Snapshot Manager extension sizing recommendations
- Creating an instance or preparing the host to install Snapshot Manager
- Installing container platform (Docker, Podman)
- Creating and mounting a volume to store Snapshot Manager data
- Verifying that specific ports are open on the instance or physical host
- Preparing Snapshot Manager for backup from snapshot jobs
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager extensions
- Before you begin installing Snapshot Manager extensions
- Downloading the Snapshot Manager extension
- 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
- Install extension using the Kustomize and CR YAMLs
- Managing the extensions
- NetBackup Snapshot Manager cloud plug-ins
- NetBackup Snapshot Manager application agents and plug-ins
- About the installation and configuration process
- Installing and configuring Snapshot Manager agent
- Configuring the Snapshot Manager application plug-in
- Configuring an application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- NetBackup protection plan
- Configuring VSS to store shadow copies on the originating drive
- Additional steps required after restoring an AWS RDS database instance
- 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
- Preparing to uninstall Snapshot Manager
- Backing up Snapshot Manager
- Unconfiguring Snapshot Manager plug-ins
- Unconfiguring Snapshot Manager agents
- Removing the Snapshot Manager agents
- Removing Snapshot Manager from a standalone Docker host environment
- Removing Snapshot Manager extensions - VM-based or managed Kubernetes cluster-based
- Restoring Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
- Troubleshooting Snapshot Manager
- SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the Snapshot Manager host
- Disk-level snapshot restore fails if the original disk is detached from the instance
- Discovery is not working even after assigning system managed identity to the control node pool
- Performance issue with GCP backup from snapshot
- Post migration on host agents fail with an error message
- File restore job fails with an error message
Snapshot Manager logs
Snapshot Manager maintains the following logs that you can use to monitor Snapshot Manager activity and troubleshoot issues, if any. The logs are stored at <install_path>/cloudpoint/logs on the Snapshot Manager host.
Table: Snapshot Manager log files
Log | Description |
|---|---|
| This log file contains all the product logs. |
| This log file contains all the Snapshot Manager installation related logs. |
| This log file contains all the IPv6 related logs. |
Navigate to: /cloudpoint/openv/dm/datamover.<id>
Here, logs can be found in the following directories: logs, opt and the netbackup.
nbpxyhelperandnbsubscriberlogs can be found inside thelogsdirectoryVRTSpbxlogs can be found inside theoptdirectorybpbkar, bpcd, bpclntcmd, nbcert, vnetd, vxmsand all other services logs can be found insidenetbackupdirectory
To increase logging verbosity, bp.conf and nblog.conf files can be updated on Snapshot Manager at /cloudpoint/openv/netbackup. See NetBackup Logging Reference Guide
Changes to the bp.conf and nblog.conf files come to effect when the next backup from snapshot or restore job runs.
The default configuration for datamover logs is as follows:
Log retention maximum period is 30 days. Logs older than 30 days are deleted.
The default configuration for high and low water marks for datamover logs is 70% and 30% of the size of "/cloudpoint" mount point. For example, if the usable size of the
/cloudpointfolder is 30 GB, then the high water mark is 21 GB (70%) and low water mark is 9GB (30%). In case, the logs directory (/cloudpoint/openv/dm/) size reaches to high water mark, older logs for which the datamover containers are cleaned up and no longer running are considered for deletion. The logs are deleted for such datamover containers until low water mark is reached or no logs are remaining for the datamover containers cleaned up or no longer running.
Modifying the default configuration:
You can modify the default configuration for log retention by adding such a section in the flexsnap.conf on the primary Snapshot Manager. Open the flexsnap.conf file from the path /cloudpoint/flexsnap.conf and add the following section:
[datamover] high_water_mark = 50 low_water_mark = 20 log_retention_in_days = 60
In case of Snapshot Manager extensions, the configuration from the primary server are used. Once the configuration is changed in primary Snapshot Manager, the configuration is updated on each Snapshot Manager extension within one hour. It is not possible to have separate custom configurations for primary Snapshot Manager or the Snapshot Manager extensions and configurations should only be changed in the primary Snapshot Manager. Though the configuration is same for primary Snapshot Manager and Snapshot Manager extensions, the high water mark and low water mark for log size are calculated based on the /cloudpoint directory mounted on each primary Snapshot Manager or Snapshot Manager extensions.
Each Snapshot Manager extension maintains the logs under its own /cloudpoint/logs location.
VM-based extension logs: Under the directory
/cloudpoint/logs.Managed Kubernetes cluster-based extension logs: Under the directory
/cloudpoint/logswhich belongs to a file share.