Upgrading Snapshot Manager extensions
When Snapshot Manager is upgraded, all the extensions are automatically disabled. You must upgrade the extensions with the required Snapshot Manager version and enable them manually from the NetBackup Web UI.
Upgrading Snapshot Manager extensions on a managed Kubernetes cluster (AKS)
- Permit the script to run as an executable:
# chmod +x cp_extension_start.sh
- Run the command as follows:
# ./cp_extension.sh install
NetBackup Snapshot Manager image repository path. Format=<Login-server/image:tag>: bfsscale.azurecr.io/veritas/flexsnap-deploy:10.0.0.0.9804 Snapshot Manager extension namespace: cloudpoint-system Snapshot Manager extension token: This is an upgrade of NetBackup Snapshot Manager Extension Starting Snapshot Manager service deployment customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com unchanged serviceaccount/cloudpoint-acc unchanged clusterrole.rbac.authorization.k8s.io/cloudpoint-cloudpoint-system unchanged clusterrolebinding.rbac.authorization.k8s.io/cloudpoint-rolebinding-cloudpoint-system unchanged deployment.apps/flexsnap-deploy unchanged Snapshot Manager service deployment ...done customresourcedefinition.apiextensions.k8s.io/cloudpoint-servers.veritas.com condition met Generating Snapshot Manager Custom Resource Definition object deployment "flexsnap-deploy" successfully rolled out cloudpointrule.veritas.com/cloudpoint-config-rule configured Snapshot Manager extension installation ...done
Executable way
Permit the script to run as an executable:
# chmod +x cp_extension_start.sh
Run the installation command as follows:
# ./cp_extension_start.sh install -i <target_image:tag> -n <namespace> -t <workflow_token>
For example:
# ./cp_extension_start.sh install -i mycontainer.azurecr.io/veritas/flexsnap-deploy:9.0.1.0.9271 -n cloudpoint-system -t workflow 3q3ou4jxiircp9tk0eer2g9jx7mwuypwz10k4i3sms2e7k4ee7-.....
Upgrade of Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
To improve the security in NetBackup 10.1, the process in data mover container are configured to launch with service (non-root) user. If file share is created with the protocol then Backup from Snapshot, Index from Snapshot operations and so on would fail when data mover is launched for data movement operation. To resolve this issue, perform the following:
Take a backup of the logs from old file share or retain the old file share.
Uninstall the Snapshot Manager extension. Delete , and from AKS extensions.
Install Snapshot Manager extension. While defining consider using CSI provisioner for
Azure Fileswith NFS protocol.Installing the Snapshot Manager extension on a managed Kubernetes cluster (AKS) in Azure
Upgrading Snapshot Manager extensions on a VM
- Load required images:
For docker environments: # sudo docker load -i SnapshotManager_image_name
For podman environment, un-tar the image file:
# gunzip VRTSflexsnap-podman-9.x.x.x.x.tar.gz
- Run the following command to prepare the Snapshot Manager host for installation:
# ./flexsnap_preinstall.sh
- Run the following respective command to upgrade VM extension:
For docker environment:
# sudo docker run -it --rm -u 0 -v /<full_path_to_volume_name>:/<full_path_to_volume_name> -v /var/run/docker.sock:/var/run/docker.sock veritas/flexsnap-deploy:<new_version> install_extension
For podman environment:
# sudo podman run -it --rm -u 0 --privileged -v /<full_path_to_volume_name>:/<full_path_to_volume_name> -v /run/podman/podman.sock:/run/podman/podman.sock veritas/flexsnap-deploy:<new_version> install_extension