Skip to main content
Version: 2.10

Post-upgrade

After you run upgrade command, Portworx Backup triggers health check to evaluate if your setup meets installation requirements. If the installation fails because of the failure in meeting the install requirements, Portworx Backup displays relevant error messages in the CLI. For more information, refer to 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

# Monitor until completion
kubectl get job pxcentral-post-install-hook -n px-backup -w

Expected output:

pxcentral-post-install-hook-xxxxx Completed

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 PXB 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, refer to 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 2.x.x​

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

  • Can view and backup clusters that you added
  • Can view all user created backups in 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 all 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