Post-upgrade
After you run the upgrade command, Portworx Backup triggers a health check to evaluate whether your setup meets installation requirements. If the upgrade fails because of unmet requirements, relevant error messages are displayed in the Helm output. For more information, see health check and health check matrix.
Monitor installation completion
After running the Helm install command, monitor the post-install hook to ensure successful deployment:
# Check post-install hook status
kubectl get pod --namespace px-backup -ljob-name=pxcentral-post-install-hook -o wide | awk '{print $1, $3}' | grep -iv error
Expected output:
pxcentral-post-install-hook-xxxxx Completed
# Monitor until completion
kubectl get job pxcentral-post-install-hook -n px-backup -w
Expected output:
NAME COMPLETIONS DURATION AGE
pxcentral-post-install-hook 1/1 2m 2m
Verify pod status
Ensure all Portworx Backup components are running:
kubectl get pods -n px-backup
All pods should be in Running or Completed state.
Access the Portworx Backup web console
Configure access to the Portworx Backup web console.
Portworx Backup supports object lock from release version 2.2.0. For more information, see S3 Object Lock in Portworx Backup. You need the permissions listed below to check if the bucket configured in the backup location supports object lock. If you are upgrading to Portworx Backup 2.2.0 from any lower version, ensure that the following object lock related permissions are enabled in the AWS web console:
s3:GetBucketObjectLockConfigurations3:GetObjectLegalHolds3:GetObjectRetention