Allocating static PV for Media pods
When you want to use a disk with specific performance parameters, you can statically create the PV and PVC. You must allocate static PV and PVC before deploying the NetBackup server for the first time.
To allocate static PV for Media pods
- Create storage class in cluster as per recommendations.
See How does the Config-Checker utility work. for storage class recommendation.
This newly created storage class name is used while creating PV and PVC's and should be mentioned for Catalog, Log, Data volume in the environment CR in mediaServer section at the time of deployment.
For more information on creating storage class, see Create a custom storage class.
For example,
kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: managed-premium-retain provisioner: disk.csi.azure.com reclaimPolicy: Retain allowVolumeExpansion: true volumeBindingMode: Immediate parameters: storageaccounttype: Premium_LRS kind: Managed
- Calculate number of disks required.
The following persistent volumes are required by Media pods:
Data and Log volume disk per replica of media server.
Use the following format to form PVC names.
For media server
data-<resourceNamePrefix_of_media>-media-<media server replica number. Count starts from 0>
logs-<resourceNamePrefix_of_media>-media-<media server replica number. Count starts from 0>
Example 1
If user wants to deploy a media server with replica count 3.
Names of the Media PVC assuming resourceNamePrefix_of_media is testmedia.
For this scenario, you must create total 8 disks, 8 PV and 8 PVCs.
6 disks, 6 PV and 6 PVCs for media server.
Following will be the names for media server volumes
For data:
data-testmedia-media-0
data-testmedia-media-1
data-testmedia-media-10
data-testmedia-media-2
For log:
logs-testmedia-media-0
logs-testmedia-media-1
logs-testmedia-media-2
Example 2
If user wants to deploy a media server with replica count 5
Names of the Media PVC assuming resourceNamePrefix_of_media is testmedia.
For this scenario, you must create 12 disks, 12 PV and 12 PVCs
10 disks, 10 PV and 10 PVCs for media server.
Following will be the names for media server volumes
For data:
data-testmedia-media-0
data-testmedia-media-1
data-testmedia-media-2
data-testmedia-media-3
data-testmedia-media-4
For log:
logs-testmedia-media-0
logs-testmedia-media-1
logs-testmedia-media-2
logs-testmedia-media-3
logs-testmedia-media-4
- Create required number of Azure disks and save the ID of newly created disk.
For more information, see Azure Disk - Static
- Create PVs for each disk and link the PVCs to respective PVs.
To create the PVs, specify the created storage class and diskURI (ID of the disk received in step 3). The PV must be created using the claimRef field and provide PVC name for its corresponding namespace.
For example, if you are creating PV for catalog volume, storage required is 128GB, diskName is primary_catalog_pv and namespace is test. PVC named catalog-testprimary-primary-0 is linked to this PV when PVC is created in the namespace test.
apiVersion: v1 kind: PersistentVolume metadata: name: catalog spec: capacity: storage: 128Gi accessModes: - ReadWriteOnce azureDisk: kind: Managed diskName: primary_catalog_pv diskURI: /subscriptions/3247febe-4e28-467d-a65c-10ca69bcd74b/ resourcegroups/MC_NBU-k8s-network_xxxxxx_eastus/providers/Microsoft.Compute/disks/deepak_s_pv claimRef: apiVersion: v1 kind: PersistentVolumeClaim name: catalog-testprimary-primary-0 namespace: test - Create PVC with correct PVC name (step 2), storage class and storage.
For example,
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: catalog-testprimary-primary-0 namespace: test spec: storageClassName: "managed-premium-retain" accessModes: - ReadWriteOnce resources: requests: storage: 128Gi - Deploy the Operator.
- Use previously created storage class names for the volumes in mediaServers section in environment CR spec and deploy environment CR.