Portworx Backup Release Notes
Portworx Backup 2.7.4
January 21, 2025
Refer these topics before you start install or upgrade tasks:
Fix
Portworx Backup offers the following fix in this release:
| Issue Number | Description | Severity |
|---|---|---|
| PB-9312 | Issue: Possible exposure of certain sensitive information in logs. Resolution: Logs are now sanitized to prevent any exposure of confidential data to ensure enhanced security and compliance. If you are on Portworx Backup version 2.6.0 or 2.7.x, upgrade to version 2.6.1 or 2.7.4 respectively. If you are on versions earlier than 2.6.0, please contact the Pure Storage support team for upgrade assistance. Affected Versions: 2.6.0, 2.7.1, 2.7.2, 2.7.3 | Major |
Portworx Backup 2.7.3
October 15, 2024
Refer these topics before you start install or upgrade tasks:
Portworx Backup offers the following features and fixes in this release:
Feature
Portworx Backup now offers support for Azure Blob immutable storage containers as backup targets. This feature expands the existing S3 object lock functionality to Azure Blob Storage, providing data protection with immutability. It enforces a version-level Write Once Read Many (WORM) policy, applicable at both the storage account and container levels. For more information, refer to Azure immutability backup location.
Fixes
| Issue Number | Description | Severity |
|---|---|---|
| PB-8360 | Issue: In certain versions of IBM Cloud Object Storage (COS), addition of backup location failed for unlocked buckets. User Impact: The backup location addition failed with an UnsupportedOperation error for unlocked IBM COS buckets.Resolution: Portworx Backup now ignores this error for unlocked IBM COS buckets and the user no longer encounters this error. Component: Backup location Affected Versions: 2.7.0, 2.7.1, 2.7.2 | Major |
| PB-8316 | Issue: The backup status was incorrectly marked as successful instead of partial success despite some PVCs failing during the backup process.User Impact: Users might incorrectly assume that the backup process was successful though all the data is not backed up due to failed PVCs. Resolution: Portworx Backup now updates the in-memory value, accurately displays the number of failed volumes, and reflects correct backup status. Component: Partial success backups Affected Versions: 2.7.0, 2.7.1, 2.7.2 | Major |
| PB-7938 | Issue: During Portworx Backup installation or upgrade, if the PostgreSQL service is in Not ready state, post install job used to fail.User impact: User cannot access Portworx Backup web console. Resolution: Post install job waits for the PostgreSQL service pod to reach the Ready state and then starts the dependent operations.Component: PostgreSQL Affected Versions: 2.7.0, 2.7.1, 2.7.2 | Minor |
| PB-7868 | Issue: NFS backup location PVC used to fail without the NFS version being passed in mount option. User impact: KDMP restore with NFSv4 backup location used to fail. Resolution: You can now restore KDMP backup taken on NFSv4 backup location. Component: KDMP restore Affected Versions: 2.7.0, 2.7.1, 2.7.2 | Major |
| PB-7726 | Issue: Kubevirt VM backups used to fail if there was a VM whose migration has failed . User impact: VM Backups with default exec rules were failing if their virt-launcher pods are not in Running state.Resolution: Default exec rules are now executed on Virt-launcher pods that are in Running state for the VM backups to succeed.Component: Kubevirt Affected Versions: 2.7.0, 2.7.1, 2.7.2 | Major |
| PB-4394 | Issue: KDMP restore of a PVC used to fail if the snapshot size was greater than PVC size. User impact: User was not able to perform a KDMP restore of PVC for file system-based storage provisioners. Resolution: By default, Portworx Backup now increases the restore PVC size for KDMP backups by 10% (based on snapshot size). In addition, provides option to increase the size of restore PVC. For more information, refer to KDMP restore Component: KDMP restore Affected Versions: 2.7.0, 2.7.1, 2.7.2 | Major |
Portworx Backup 2.7.2
Sep 12, 2024
Refer these topics before you start install or upgrade tasks:
Portworx Backup provides the following enhancement and fix in this release:
Enhancement
Partial success backup
This enhancement ensures that backups with some failed volumes are still considered successful for the volumes that were successfully backed up, improving the overall utility and reliability of our backup solution. Users can now rely on partial backups, ensuring that successfully backed-up volumes are still usable even if some volumes fail. For more information, refer to partial success backups.
Fix
Portworx Backup 2.7.2 provides the following fix:
| Issue Number | Description | Severity |
|---|---|---|
| PB-7726 | Issue: VM backups used to fail during auto execution of default backup rules (both pre-exec and post-exec) if the virt-launcher pod of the VMs are not in running state. User impact: You cannot backup your VM successfully. Resolution: Default backup rules are now auto-executed on the virt-launcher pods that are in running state for successful creation of VM backups. Component: Kubevirt Affected Versions: 2.7.0, 2.7.1 | Major |
Portworx Backup 2.7.1
June 6, 2024
Refer these topics before install or upgrade to know more on the installation prerequisites and compatible versions:
Portworx Backup provides the following enhancement and fixes in this release:
Enhancement
Portworx backup enables you to add an Azure backup location based out of China through Portworx Backup web console. For more information, refer to Add Azure backup location.
Fixes
Portworx Backup 2.7.1 comes with the following fixes:
| Issue Number | Description |
|---|---|
| PB-6908 | Issue: Being on Portworx Backup version 2.6.0, if you upgraded Stork version to 24.1.0 and then opt for default VSC in the Create Backup window, VSC Not Found Error was seen.Resolution: You can now choose default VSC and create successful backups in this environment. |
| PB-6687 | Issue: If you deploy Portworx Enterprise with PX-Security enabled and take a backup on NFS backup location and then restore, restore used to fail. Resolution: This issue is now fixed. |
Known Issues
Portworx Backup team is aware of the following known issues and they will be fixed in the upcoming releases:
| Issue Number | Description |
|---|---|
| PB-7159 | Issue: For default CSI restores with replace existing resources option on cloud platforms, restores will be successful but the application pods get stuck in container creating state. Workaround: Perform a custom restore to a different namespace to bring the application pods up. |
| PB-7158 | Issue: When you restore a CSI backup based on any cloud platform supported by Portworx Backup, Show Details window of restore displays duplicate entries for PV and PVC resources. |
Portworx Backup 2.7.0
May 20, 2024
Refer these topics before install or upgrade to know more on the installation prerequisites and compatible versions:
Portworx Backup proudly introduces a series of new features in this release.
New Features
New web console
Portworx Backup provides an intuitive web console with light theme designed to provide a holistic view, centralized management, detailed insights, and simplifies management of your backups and restores. Along with real-time insights and streamlined management capabilities the user interface provides easy navigation and usability. For more information, refer to Web console.
Portworx Backup Dashboard
Portworx Backup introduces an extensive dashboard that provides enhanced visibility and control over your backup and restore operations across all clusters. Dashboard enables you to track the health and status of all your backup and restore operations in real-time. Also, you can view metrics like total number of protected applications, successful and failed operations, and ongoing activities with breakdowns by hour, day, and cluster. You can export detailed backup and restore data in CSV format for in-depth analysis and reporting to make informed decisions based on historical data trends. Refer to Web console for more information.
Email Alerts
From Portworx Backup version 2.7.0, you can configure dashboard alerts, receive instant notifications for critical events such as failures in backups, restores, backup location and connectivity to clusters. Administrators can set up a dedicated SMTP server to enable email notifications to keep the intended audience informed on the key events that arise in Portworx Backup environment. For more information, refer to Email alerts and Configure email alerts.
Refined CSI and KDMP backups
This feature provides significant refinements to the backup options available in Portworx Backup utilizing the CSI (Container Storage Interface) and KDMP (Kubernetes Data Management Platform) drivers. Portworx Backup now facilitates cross-cloud backups and restores through the web console and the new approach gives the users more control to map their storage provisioners with the VSCs more accurately to create the required type of backup as per their needs. Refer to CSI backups and KDMP backups for more information.
Native monitoring with external or internal Prometheus stack
From 2.7.0 release, you can opt in to use your own Prometheus Stack or Portworx Backup provided one as your monitoring component with minimal configuration settings. With this, Portworx Backup offers the reliability of Prometheus and Alertmanager for metrics collection and alert management. You can deploy Portworx Backup's Prometheus stack through Helm for this robust framework to support a secure and scalable alerting and monitoring solution. For more information, refer to Configure Prometheus.
Backup and restore VMs with KubeVirt
Portworx Backup now lets you backup and restore your VMs through stream-lined workflow with a new web console. In addition, Portworx Backup internally applies default or built-in (pre-exec and post-exec) rules in case you do not apply any rules during creation of VM-based backups.
Fixes
Portworx Backup 2.7.0 comes with the following fixes:
| Issue Number | Description |
|---|---|
| PB-6880 | Issue: Previously, deleting KDMP backups failed if the "CSI + Offload to backup location" option was selected in the Create Backup window of Portworx Backup version 2.6.0 and below. Resolution: This issue has been fixed. |
| PB-6631 | Issue: Quick and full maintenance job pods were using certificates and TLS secrets (even with SSL disabled) and got stuck in the ContainerCreating state failing to mount a non-existent secret.Resolution: These pods now operate smoothly without getting stuck. |
| PB-6578 | Issue: Portworx Backup pod would crash with a nil pointer error when handling a large number of backups. Resolution: This issue is resolved now. |
| PB-6435 | Issue: A Kubernetes version call would fail when more than 100 application clusters were added to a single backup deployment. Resolution: This issue has been fixed. |
| PB-5824 | Issue: In the Restore Backup window, the Destination Namespace drop-down was not scrollable when the list of namespaces was too large. Resolution: Scrolling through a large list of destination namespaces is now possible. |
| PB-5438 | Issue: Restoring backups of static PVCs with labels previously failed. Resolution: Backups of static PVCs with labels can now be restored without issues. |
| PB-4623 | Issue: The Portworx Backup web console displayed the Remove option from the vertical ellipsis even when a backup was in the Deleting or Delete pending state. Resolution: The backups in these states appear disabled now and display only the View Json and Show Details options in the vertical ellipsis. |
| PB-4443 | Issue: The Portworx Backup web console experienced slow performance when multiple users logged into a single instance. Resolution: This issue has been resolved. |
| PB-3852 | Issue: The Portworx Backup web console previously allowed users to delete a backup while its restore was in progress. Resolution: From version 2.7.0 of Portworx Backup, deleting a backup during its restore is no longer possible. |
| PB-3175 | Issue: Users were unable to delete a cluster that was in a Not available state. Resolution: Clusters in this state can now be deleted. |
Known Issues
Portworx Backup team is aware of the following known issues and these issues will be addressed in the upcoming releases:
| Issue Number | Description |
|---|---|
| PB-6999 | Issue: Users will not be able to create a duplicate of VM backup. |
| PB-6908 | Issue: If you upgrade to Stork version 24.1.0 while you are on Portworx Backup 2.6.0, selecting the default VSC in the Create Backup window may result in a VSC Not Found Error. |
| PB-6901 | Issue: When you try to restore a backup of a namespace with Istio enabled, the restore goes into a partial success state. Workaround: While restoring the backup of application namespace with Istio enabled ensure that you deselect Istio ConfigMap istio-ca-root-cert resource under Resource Selector during restore. |
| PB-6896 | Issue: Gateway time-out errors occur in SMTP configurations lacking user authorization because Portworx Backup does not support email alert configurations for unauthorized or non-authenticated SMTP servers. |
| PB-6819 | Issue: Portworx Backup does not support backing up and restoring VMs in Microsoft Windows environments. |
| PB-6817 | Issue: Portworx Backup does not support snapshot class mapping backup (CSI or CSI with KDMP) with CephFS. |
| PB-6758 | Issue: When navigating away from the Portworx Backup home page during a report download, the download task is aborted without notification if there are a large number of backups involved. |
| PB-6747 | Issue: Scheduled backups on OCP clusters may occasionally fail when creating a snapshot class mapping backup with the Offload to backup location option if the cluster's Kubernetes version is below 1.29. This failure is due to a faulty condition in the snapshot controller. |
| PB-6612 | Issue: Portworx Backup does not support KDMP backups for Kubevirt VMs. |
| PB-6046 | Issue: The activity timeline chart on the Portworx Backup Dashboard page displays all backup data instead of only showing filtered backup data for the specified time. |