Recommendations of NetBackup deployment on Kubernetes cluster
Note the following recommendations:
Do not delete the disk linked to PV used in primary server and media server CR deployment. This may lead to data loss.
Ensure that in one cluster, only one NetBackup operator instance is running.
Do not edit any Kubernetes resource created as part of primary server and media server custom resource. Update is supported through custom resource update only.
Detailed primary server custom resource deployment and media server custom resource deployment logs are retrieved from NetBackup operator pod logs using the kubectl logs <netbackup-operator-pod-name> -c netbackup-operator -n <netbackup operator-namespace> command .
Deploy primary server custom resource and media server custom resource in same namespace.
Ensure that you follow the symbolic link and edit the actual persisted version of the file, if you want to edit a file having a symbolic link in the primary server or media server.
Specify different block storage based volume to obtain good performance when the
nbdeployutilutility does not perform well on the following respective storage types based volumes:(AKS-specific): Azure premium files
(EKS-specific): Amazon elastic files
Duplication job configuration recommendation:
While configuring destination storage unit, manually select media servers that are always up, running and would never scale in (by the media server autoscaler). Number of media servers that are always up and running would be same as that of the value mentioned in field in CR.
When upgrading from older version of NetBackup 10.3, post upgrade ensure that you manually select media servers mentioned in field in CR. If the value of is not specified, the value will be set to the default value of 1.
Adjust the value of field and managed by the Cloud Scale Technology based on the backup environment and requirements.
(AKS-specific)
Use Azure Premium storage for data volume in media server CR.
Use Azure Standard storage for log volume in media server CR.
For primary server catalog volume, use
Azure premium filesas storage type and for media server volumes, usemanaged-diskas storage type.In case of upgrade and during migration, do not delete the
Azure premium files/Azure disk volumelinked to the old PV which is used in primary server CR deployment until the migration is completed successfully. Else this leads to data loss.Do not skip the Config-Checker utility execution during NetBackup upgrade or data migration.
(EKS-specific)
Use AWS Premium storage for data volume in media server CR.
Use AWS Standard storage for log volume in media server CR.
For primary server volume (catalog), use
Amazon EFSas storage type. For media server, primary server volumes, log and data volumes useAmazon EBSas storage type.In case of upgrade and during migration, do not delete the
Amazon elastic fileslinked to the old PV which is used in primary server CR deployment until the migration is completed successfully. Else this leads to data loss.