Restoring a catalog
You can restore a catalog.
To restore a catalog
- Copy DRPackages files (packages) located at
/mnt/nblogs/DRPackages/from the pod to the host machine from where Azure Kubernetes Service cluster is accessed.Run the kubectl cp <primary-pod-namespace>/<primary-pod-name>:/mnt/nblogs/DRPackages <Path_where_to_copy_on_host_machine> command.
- Preserve the data of
/mnt/nbdataand/mnt/nblogson host machine by creating tar and copying it using the kubectl cp <primary-pod-namespace>/<primary-pod-name>:<tar_file_name> <path_on_host_machine_where_to_preserve_the_data> command. - Change CR spec from paused: false to paused: true in primary, mediaServers, and msdpScaleouts sections in
environment.yamland re-apply yaml using the kubectl apply -f environment.yaml -n <namespace> command. - Change replica count to 0 in primary server's statefulset using the kubectl edit statefulset <primary-server-statefulset-name> -n <namespace> command.
- Get names of PV attached to primary server PVC (catalog, log and data) using the kubectl get pvc -n <namespace> -o wide command.
- Delete primary server PVC (catalog, log and data) using the kubectl delete pvc <pvc-name> -n <namespace> command.
- Delete the PV linked to primary server PVC using the kubectl delete pv <pv-name> command.
- Change CR spec paused: true to paused: false in primary server section in
environment.yamland reapply yaml with the kubectl apply -f environment.yaml -n <namespace> command. - After the primary server pod is in ready state, change CR spec from paused: false to paused: true in primary server section in
environment.yamland reapply yaml with the kubectl apply -f environment.yaml -n <namespace> command. - Execute the kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash command in the primary server pod.
Increase the debug logs level on primary server.
Create a directory
DRPackagesat persisted location usingmkdir /mnt/nblogs/DRPackages.Change ownership of the
DRPackagesfolder to service user using the chown nbsvcusr:nbsvcusr /mnt/nblogs/DRPackages command.
- Copy earlier copied DR files to primary pod at
/mnt/nblogs/DRPackagesusing the kubectl cp <Path_of_DRPackages_on_host_machine> <primary-pod-namespace>/<primary-pod-name>:/mnt/nblogs/DRPackages command. - Execute the following steps in the primary server pod.
Change ownership of files in
/mnt/nblogs/DRPackagesusing the chown nbsvcusr:nbsvcusr <file-name> command.Deactivate NetBackup health probes using the /opt/veritas/vxapp-manage/nbu-health deactivate command.
Stop the NetBackup services using
/usr/openv/netbackup/bin/bp.kill_all.Execute the nbhostidentity -import -infile /mnt/nblogs/DRPackages/<filename>.drpkg command.
Restart all the NetBackup services using
/usr/openv/netbackup/bin/bp.start_all.
- Verify security settings are back.
- Add respective media server entry in host properties using NetBackup Administration Console.
Navigate to NetBackup Management > Host properties > Master Server > Add Additional server and add media server.
- Restart the NetBackup services in primary server pod and external media server.
Execute the following command in the primary server pod:
kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash
Run the /usr/openv/netbackup/bin/bp.kill_all command. After stopping all services restart the same using the /usr/openv/netbackup/bin/bp.start_all command.
Run the /usr/openv/netbackup/bin/bp.kill_all command. After stopping all services restart the services using the /usr/openv/netbackup/bin/bp.start_all command on the external media server.
- Configure a storage unit on external media server that is used during catalog backup.
- Perform catalog recovery from NetBackup Administration Console.
For more information, refer to the NetBackup Troubleshooting Guide.
- Execute the kubectl exec -it -n <namespace> <primary-pod-name> -- /bin/bash command in the primary server pod.
Stop the NetBackup services using the /usr/openv/netbackup/bin/bp.kill_all command.
Start NetBackup services using the /usr/openv/netbackup/bin/bp.start_all command.
Activate NetBackup health probes using the /opt/veritas/vxapp-manage/nbu-health activate command.
- Change CR spec from paused: true to paused: false in primary, mediaServers, and msdpScaleouts sections in
environment.yamland re-apply yaml using the kubectl apply -f environment.yaml -n <namespace> command. - To configure NetBackup IT Analytics refer to the following topic.
See Configuring NetBackup IT Analytics for NetBackup deployment.