Skip to main content
Version: 3.0

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.

note

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:GetBucketObjectLockConfiguration
  • s3:GetObjectLegalHold
  • s3:GetObjectRetention

Access permissions in Portworx Backup​

Users with the admin role can access the following resources in the Portworx Backup web console:

  • Can view and back up clusters that you added
  • Can view all user-created backups on the Backups page
  • Can view all Portworx Backup security objects such as cloud credentials, backup locations, schedule policies, and backup rules of all users
  • Cannot view non-Portworx Backup user management objects

The access permissions available to a user in case of backup sync are:

  • If a user is the owner of a bucket, then the Backups page lists backups of all users who used that bucket

  • If a user is a collaborator, then the user can view own backups only

Last updated on