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
- 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
Post-upgrade tasks
You may need to perform the following tasks after a successful upgrade of the NetBackup Snapshot Manager server.
Post-upgrade tasks
- Upgrade the NetBackup Snapshot Manager agents on the Linux and Windows application hosts.
Note:
If you are upgrading from NetBackup Snapshot Manager 8.3 to 9.0 or 9.1, then you must manually upgrade the on-host agents. If you are upgrading from NetBackup Snapshot Manager 9.0 to 9.1, upgrading the on-host agents is optional.
Perform the following steps to upgrade the agent on Linux hosts:
Sign in to NetBackup UI and download the newer agent package.
Navigate to Cloud > NetBackup Snapshot Managers > Actions > Add agent.
Stop the flexsnap agent service on the Linux host where you want to upgrade the agent.
Run the following command on the Linux host:
# sudo systemctl stop flexsnap-core.service
Upgrade the agent on the Linux host.
Run the following command on the Linux host:
# sudo rpm -Uvh --force flexsnap_agent_rpm_name
Here, flexsnap_agent_rpm_name is the name of the agent rpm package you downloaded earlier.
Reload the daemon, if prompted.
Run the following command on the Linux host:
# sudo systemctl daemon-reload
Repeat these steps on all the Linux hosts where you wish to upgrade the Linux-based agent.
Note the following:
When upgrading from CloudPoint agent to Flexsnap agent, uninstall CloudPoint agent first and then install the Flexsnap agent using the following recommended uninstallation and installation commands:
Uninstallation: sudo yum -y remove cloudpoint_agent_rpm_name
Installation: sudo yum -y install flexnsap_agent_rpm_name
Connect to the Linux host and re-register the agent using the following command:
sudo flexsnap-agent --ip <snapshotmanager_host_FQDN_or_IP> --token <authtoken>
Run discovery task.
Perform the following steps to upgrade the agent on Windows hosts:
Sign in to NetBackup UI and download the newer agent package.
Navigate to Cloud > NetBackup Snapshot Managers > Actions > Add agent.
Stop the Veritas NetBackup Snapshot Manager Agent service that is running on the host.
Run the newer version of the agent package file and follow the installation wizard workflow to upgrade the on-host agent on the Windows host.
The installer detects the existing installation and upgrades the package to the new version automatically.
Generate the token for agent configuration. Navigate to NetBackup Web UI > Cloud > NetBackup Snapshot Managers > Actions > Add agent > Create Token.
Repeat these steps on all the Windows hosts where you wish to upgrade the Windows-based agent.
For details on how to download the agent installation package from the NetBackup UI, refer to the following:
See Downloading and installing the NetBackup Snapshot Manager agent.
- If you want to run backup from snapshot and restore from backup jobs after upgrade, you must update the NetBackup configuration so that the upgraded NetBackup Snapshot Manager configuration details are available with NetBackup. After upgrading, all the NetBackup Snapshot Manager that you want to use for backup from snapshot or restore from backup jobs, must be re-edited by providing a token so that NetBackup certificates are generated. See Edit a NetBackup Snapshot Manager section, in the NetBackup Web UI Cloud Administrator's Guide.
Perform one of the following actions:
From the NetBackup Web UI, edit the NetBackup Snapshot Manager server information.
In the Web UI, click Workloads > Cloud from the left navigation pane and then click the NetBackup Snapshot Manager servers tab.
Select the NetBackup Snapshot Manager server that you just upgraded, and then click Edit from the ellipsis action button on the right.
In the Edit NetBackup Snapshot Manager server dialog, specify all the requested details.
Click Validate to validate the NetBackup Snapshot Manager server certificate.
In the Token field enter the Standard Host Token.
Click Save to update the NetBackup Snapshot Manager server configuration.
Or, on the NetBackup primary server, run the following command:
./tpconfig -update -snapshot_manager <snapshot_manager_name> -snapshot_manager_user_id <user_ID> -manage_workload <manage_workload> [-requiredport <IP_port_number>] [-security_token <token_value>]
Note:
Additional option -security_token is required for updating NetBackup Snapshot Manager which is managing cloud workloads. The token must be Standard host token. This is required for NetBackup certificates generation on NetBackup Snapshot Manager.
On UNIX systems, the directory path to this command is
/usr/openv/volmgr/bin/. On Windows systems, the directory path to this command isinstall_path\Volmgr\bin\. Refer to the Veritas NetBackup Commands Reference Guide for details.Or, make a PATCH API call to the NetBackup primary server using the following URL:
https://primaryserver.domain.com/netbackup/config/servers/snapshot-mgmt-servers/cp-hostname
- By default, the create snapshot operation in NetBackup Snapshot Manager version 10.2 would create recovery points instead of snapshots. Hence to use Azure recovery points for the snapshots to be application consistent, ensure that the following additional permissions are configured to enable Azure restore points:
actions": [ "Microsoft.Compute/restorePointCollections/read", "Microsoft.Compute/restorePointCollections/write", "Microsoft.Compute/restorePointCollections/delete", "Microsoft.Compute/restorePointCollections/restorePoints/read", "Microsoft.Compute/restorePointCollections/restorePoints/write", "Microsoft.Compute/restorePointCollections/restorePoints/delete", "Microsoft.Compute/restorePointCollections/restorePoints/ retrieveSasUris/action", "Microsoft.Compute/restorePointCollections/restorePoints/ diskRestorePoints/read", "Microsoft.Compute/restorePointCollections/restorePoints/ diskRestorePoints/beginGetAccess/action", "Microsoft.Compute/restorePointCollections/restorePoints/ diskRestorePoints/endGetAccess/action" ]," - After upgrading NetBackup Snapshot Manager to version 10.2, the on-host agent must be restarted to discover and protect assets on LVM storage.
For more details about the tpconfig command and its options, refer to the Veritas NetBackup Commands Reference Guide.