NetBackup™ Status Codes Reference Guide
- NetBackup status codes
- NetBackup status codes
- NetBackup KMS status codes
- NetBackup status codes
- Media Manager status codes
- Media Manager status codes
- Media Manager status codes
- Device configuration status codes
- Device configuration status codes
- Device configuration status codes
- Device management status codes
- Device management status codes
- Device management status codes
- Robotic status codes
- Robotic status codes
- Robotic status codes
- Robotic error codes
- Robotic error codes
- Robotic error codes
- Security services status codes
- Security services status codes
- Security services status codes
- NetBackup alert notification status codes
NetBackup status code: 8469
Explanation: Cannot rename Persistent Volume Claim (PVC) in the given cluster.
Recommended Action: Perform the following as appropriate:
Check the NetBackup operator logs for details using the following command:
kubectl logs <netbackup-operator-pod-name> netbackup-operator -n <netbackup-operator-namespace>
Check if the storageClassName provided in CR is available in the cluster using following command:
kubectl get storageclass
Verify that RBAC permissions are correct. Refer to the NetBackup Deployment on Azure Kubernetes Cluster (AKS) Administrator's Guide.
Check the Kubernetes documentation for PVC details.
Manually rename using the following steps:
Save the PVC's volume name and storage class as follows:
kubectl describe pvc <azure-disk- or-files-pvc-name> -n < netbackup-environment-namespace >
Delete the old Azure disk or files PVC:
kubectl delete pvc <azure-disk-or-files-pvc-name> -n <netbackup-environment-namespace> kubectl patch pv <saved_volume_name> --type json -p '[{"op": "remove", "path": "/spec/claimRef"}]'
Ensure that the PV is available after completing the previous steps.
Create a new Azure files PVC with the old PV as follows:
apiVersion: v1 kind: PersistentVolumeClaim metadata: name: <old_pvc_name> namespace: <old_pvc_namespace> spec: accessModes: - ReadWriteMany volumeName: <saved_volume_name> storageClassName: <saved_storage_class_name> resources: requests: storage: 100Gi #previous files size
Enable the probes /opt/veritas/vxapp-manage/nbu-health enable.
Set replica count to 1 or reapply
environment.yaml
file as follows:kubectl scale --replicas=1 <STS name> -n <netbackup-environment-namespace> or reapply the
environment.yaml
file.
Click here to view technical notes and other information on the Veritas Technical Support website about this status code.