Please enter search query.
Search <book_title>...
NetBackup™ Snapshot Manager Install and Upgrade Guide
Last Published:
2023-03-31
Product(s):
NetBackup (10.2)
- 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
- 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
- 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 from snapshot job fails with timeout error
Acknowledgment not received for datamover
Backup job fails with the following error message, where acknowledgment is not received for datamover:
Oct 10, 2022 5:06:21 AM - begin SnapDupe Mount: Import Snapshot Oct 10, 2022 5:06:21 AM - Info nbjm (pid=7578) BackupId=aws-ec2-us-east-2-xxxxxxxxxxxxxx_1665303611 Oct 10, 2022 5:06:23 AM - Info nbcs (pid=523) Start Oct 10, 2022 5:06:23 AM - Info nbcs (pid=523) Requesting data mover container Oct 10, 2022 5:18:36 AM - Error nbcs (pid=523) Invalid operation for asset: aws-ec2-us-east-2-xxxxxxxxxxxxxx Oct 10, 2022 5:18:36 AM - Error nbcs (pid=523) Acknowledgment not received for datamover datamover.a2d3dc2249da45a0a839bc77eface2a4 Oct 10, 2022 5:18:36 AM - Info nbcs (pid=523) End
The above error message is observed on the cluster, when:
The pods are in ContainerCreating state. For example:
flexsnap-workflow-general-1665398188-4d03f27e-fblxb 0/1 ContainerCreating 0 142m flexsnap-workflow-general-1665398188-538a8846-zrgtl 0/1 ContainerCreating 0 142m flexsnap-workflow-general-1665398188-87cb301a-5bqss 0/1 ContainerCreating 0 142m flexsnap-workflow-general-1665398188-f61f5f42-g2rhv 0/1 ContainerCreating 0 142mThe describe pod displays the events as follows:
Type Reason Age From Message ---- ------ ---- ---- ------- Normal SandboxChanged 25m (x1874 over 140m) kubelet Pod sandbox changed, it will be killed and re-created. Warning FailedCreatePodSandBox 56s (x2079 over 140m) kubelet (combined from similar events): Failed to create pod sandbox: rpc error: code = Unknown desc =failed to set up sandbox container "45f90b441cc4ea83efca63eacff1028779d4114fb213a5200e76f2e25373e054" network for pod "flexsnap-workflow-general-1665398189-f46e636e-vrcdz": networkPlugin cni failed to set up pod "flexsnap-workflow-general-1665398189-f46e636e-vrcdz_nbuxsystest" network: add cmd: failed to assign an IP address to container
To resolve this issue, refer to the AWS troubleshooting section and implement the solution. Contact the AWS support for further troubleshooting.