Please enter search query.
Search <book_title>...
NetBackup™ Snapshot Manager Install and Upgrade Guide
Last Published:
2024-04-10
Product(s):
NetBackup (10.3)
- Introduction
- Section I. NetBackup Snapshot Manager installation and configuration
- Preparing for NetBackup Snapshot Manager installation
- Meeting system requirements
- NetBackup Snapshot Manager host sizing recommendations
- NetBackup Snapshot Manager extension sizing recommendations
- Creating an instance or preparing the host to install NetBackup Snapshot Manager
- Installing container platform (Docker, Podman)
- Creating and mounting a volume to store NetBackup Snapshot Manager data
- Verifying that specific ports are open on the instance or physical host
- Preparing NetBackup Snapshot Manager for backup from snapshot jobs
- Deploying NetBackup Snapshot Manager using container images
- Deploying NetBackup Snapshot Manager extensions
- Before you begin installing NetBackup Snapshot Manager extensions
- Downloading the NetBackup Snapshot Manager extension
- Installing the NetBackup Snapshot Manager extension on a VM
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
- Installing the NetBackup Snapshot Manager extension on a managed Kubernetes cluster (EKS) in AWS
- Installing the NetBackup 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 providers
- Configuration for protecting assets on cloud hosts/VM
- Deciding which feature (on-host agent or agentless) of NetBackup Snapshot Manager is to be used for protecting the assets
- Protecting assets with NetBackup Snapshot Manager's on-host agent feature
- Installing and configuring NetBackup Snapshot Manager agent
- Configuring the NetBackup Snapshot Manager application plug-in
- Configuring an application plug-in
- Microsoft SQL plug-in
- Oracle plug-in
- Protecting assets with NetBackup Snapshot Manager's agentless feature
- Snapshot Manager catalog backup and recovery
- NetBackup Snapshot Manager assets protection
- 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
- About NetBackup Snapshot Manager upgrades
- Supported upgrade path
- Upgrade scenarios
- Preparing to upgrade NetBackup Snapshot Manager
- Upgrading NetBackup Snapshot Manager
- Upgrading NetBackup Snapshot Manager using patch or hotfix
- Applying operating system patches on NetBackup Snapshot Manager host
- Migrating and upgrading NetBackup Snapshot Manager
- GCP configuration for migration from zone to region
- Post-upgrade tasks
- Post-migration tasks
- Uninstalling NetBackup Snapshot Manager
- Preparing to uninstall NetBackup Snapshot Manager
- Backing up NetBackup Snapshot Manager
- Unconfiguring NetBackup Snapshot Manager plug-ins
- Unconfiguring NetBackup Snapshot Manager agents
- Removing the NetBackup Snapshot Manager agents
- Removing NetBackup Snapshot Manager from a standalone Docker host environment
- Removing NetBackup Snapshot Manager extensions - VM-based or managed Kubernetes cluster-based
- Restoring NetBackup Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
- Troubleshooting NetBackup Snapshot Manager
- SQL snapshot or restore and granular restore operations fail if the Windows instance loses connectivity with the NetBackup 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
- Acknowledgment not received for datamover
- Upgrade of extension on AWS (EKS) fails when upgrading through script
- Backup and restore jobs fail with timeout error
- GCP restore with encryption key failed with an error message
- Amazon Redshift databases not available after discovery
- Shared VPC subnet not visible
- Failure of encryption key listing during VM restore
- Container manager may not spawn the ephemeral registration container timely
- GCP restore from VM fails to obtain firewall rules
- Parameterised VM restore fails to retrieve encryption keys
(Optional) Policies for podman based deployments
On RHEL version 8.x systems, after deploying NetBackup Snapshot Manager, to reduce the selinux logs getting logged to /var/log/messages folder, user can add and apply the following policies:
(allow container_t container_runtime_t (unix_stream_socket (connectto))) (allow container_t unlabeled_t (dir (add_name create read remove_name setattr write ))) (allow container_t unlabeled_t (file (append create ioctl open read setattr link unlink write rename))) (allow container_t unlabeled_t (lnk_file (create))) (allow container_t default_t (dir ( add_name remove_name write create setattr))) (allow container_t default_t (file ( create open read append rename unlink write ioctl lock link))) (allow container_t default_t (lnk_file (create))) (allow container_t lvm_var_run_t (file (lock open read write))) (allow container_t container_var_lib_t( file ( ioctl open read ))) (allow container_t var_run_t (sock_file (write))) (allow container_t autofs_device_t (chr_file (getattr))) (allow container_t clock_device_t (chr_file (getattr))) (allow container_t cpu_device_t (chr_file (getattr))) (allow container_t event_device_t (chr_file (getattr))) (allow container_t fixed_disk_device_t (chr_file (getattr))) (allow container_t framebuf_device_t (chr_file (getattr))) (allow container_t hypervkvp_device_t (chr_file (getattr))) (allow container_t kmsg_device_t (chr_file (getattr))) (allow container_t loop_control_device_t (chr_file (getattr))) (allow container_t lvm_control_t (chr_file (getattr))) (allow container_t memory_device_t (chr_file (getattr))) (allow container_t netcontrol_device_t (chr_file (getattr))) (allow container_t nvram_device_t (chr_file (getattr))) (allow container_t ptmx_t (chr_file (getattr))) (allow container_t scsi_generic_device_t (chr_file (getattr))) (allow container_t tun_tap_device_t (chr_file (getattr))) (allow container_t uhid_device_t (chr_file (getattr))) (allow container_t vfio_device_t (chr_file (getattr))) (allow container_t vhost_device_t (chr_file (getattr))) (allow container_t fixed_disk_device_t (blk_file (getattr))) (allow container_t fs_t (filesystem (associate))) (allow container_t self (dir (create remove_name))) (allow container_t self(file (link rename unlink)))
To add and load the policy
- Create a
/tmp/VRTSflexsnap.cilfile and copy the above policies to/tmp/VRTSflexsnap.cilfile. - Execute the following commands to load the policies:
sudo semodule -i /tmp/VRTSflexsnap.cil
sudo semanage fcontext -a -t container_file_t \"/cloudpoint(/.*)?\"\n"
sudo restorecon -Rv /cloudpoint{}