Upgrading NetBackup individual components
This section describes upgrading of the following individual components:
NetBackup operators
NetBackup application
MSDP Scaleout
Snapshot Manager
Note:
Ensure that you go through this section carefully before starting with the upgrade procedure.
During upgrade, ensure that the following sequence of upgrade is followed:
Upgrade NetBackup operator
Upgrade NetBackup application
Upgrade MSDP operator
Upgrading Snapshot Manager
In case the above sequence is not followed, user may face data loss.
Preparing for NetBackup upgrade
- Take a backup of all the NetBackup jobs and ensure that all the jobs are suspended.
- Take a catalog backup.
See Backing up a catalog.
- Copy DRPackages files (packages) located at
/mnt/nblogs/DRPackages/from the pod to the host machine from where Kubernetes Service cluster is accessed.Run the following command:
kubectl cp <primary-pod-namespace>/<primary-pod-name>:/mnt/nblogs/DRPackages <Path_where_to_copy_on_host_machine>
- Preserve the data of
/mnt/nbdata and /mnt/nblogson host machine by creating tar and copying it using the following command:kubectl cp <primary-pod-namespace>/<primary-pod-name>:<tar_file_name> <path_on_host_machine_where_to_preserve_the_data>
- Preserve the environment CR object using the following command and operator directory that is used to deploy the NetBackup operator:
kubectl -n <namespace> get environment.netbackup.veritas.com <environment name> -o yaml > environment.yaml
Note:
Ensure that you upgrade MSDP operator first.
- (AKS-specific) In case of existing NetBackup deployments with Azure disks, change the storage class for catalog and log data of primary server to trigger data migration. For more information on changing the storage class, refer to the AKS-specific requirements sub-section of the following section:
See Preparing the environment for NetBackup installation on Kubernetes cluster.
- (EKS-specific) In case of existing NetBackup deployments with EBS, change the storage class for catalog data of primary server to trigger data migration. For more information on changing the storage class, refer to the following section: