Skip to main content
Version: 2.7


Portworx Backup (PX-Backup) is a Kubernetes backup solution that allows you to back up and restore applications, KubeVirt Virtual Machines (VMs) and their data across multiple clusters. Portworx Backup works with Portworx Central (a web console, that centralizes various features or products including Portworx Backup into a single user interface), allowing administrators or other users to manage backups and restores of multiple Kubernetes clusters through a web console. Under this principle of multi-tenancy, authorized users connect through authorization providers to create and manage backups for clusters and applications for which they have permissions (without reaching out to the administrators). Portworx Backup maintains a repository of available application backups and restores them to any destination cluster that a user has access to. Portworx Backup communicates with backup locations on regular-basis to check for the availability of new backups.

Portworx Backup architecture

Portworx Backup Architecture

Understand how Portworx Backup works

Portworx Backup is compatible with any Kubernetes cluster, including managed and cloud deployments and integrates with the following major categories of storage providers:

  • AWS S3
  • S3 compatible object store
  • Azure
  • Google
  • NFS
    • EFS
    • GCP Filestore
    • Azure file share

Portworx Backup supports taking backup on the following backup targets:

Block storage (Data being backed up from)File storage (Data being backed up from)
  • Amazon EBS
  • Google Persistent Disk
  • Azure Managed Disks
  • Portworx PX-Store
  • CSI
  • EFS
  • GCP Filestore
  • Azure file share

Here is a list of some Kubernetes native resources that Portworx Backup can back up:


The Portworx Backup web console displays a platform-dependent list of resources it can back up for each type of cluster. Additionally, even for the same platform, the resource list depends on the applications of the namespace.

Portworx Backup provides namespace and label selectors, allowing you to create granular backups of the application you want. You can back up an entire namespace or use label selectors to select certain resources to back up. This selection method also helps preserve associated configuration and pod data, ensuring that you can leverage your backup data after restore. For example, Portworx Backup can back up a MySQL deployment containing pods, PVCs, and volumes tagged with an app = mysql label. You can apply the labels for your namespaces, resources and their backups with a key-value pair using the CLI and with Portworx Backup web console you can filter them when needed to create a backup. With this mechanism, Portworx Backup can back up stateful applications as easily as stateless ones. For more information on how labels work, refer to Labels in Portworx Backup.

You can create a schedule for your backups by creating an independent schedule policy that defines when backups must be created and how many rolling copies they should retain. After creating schedule policies, you can associate them with multiple backups.

Portworx Backup rules help you to eliminate manual preparation tasks and lets you minimize the interruptions to your cluster during backup operations. You can create pre-exec (freeze) or post-exec (unfreeze/thaw) rules that run before and after backups are taken. As with schedule policies, you can associate rules with multiple backups.

The following topics help you to know more about Portworx Backup:

Was this page helpful?