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 files as storage type and for media server volumes, use managed-disk as storage type.

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.

Do not skip the Config-Checker utility execution during NetBackup upgrade or data migration.

Specify different block storage based volume to obtain good performance when the nbdeployutil utility does not perform well on Azure premium files based volumes.