25.1.0
February 12, 2025
Improvements
| Issue Number | Enhancement Description |
|---|---|
| PB-9039 | Portworx Backup now supports storing and restoring the status of Custom Resources (CR) during backup and restore operations. This feature ensures that CRs retain their status upon restoration, improving consistency and recovery reliability. To enable this feature in the UI, you must set the corresponding flag in the ConfigMap. Note: Only create and delete operations are supported for this flag in both manual and scheduled backups. |
| PB-8121 | Portworx Backup includes virtualMachineInstancetype and VirtualMachinePreference resources when backing up KubeVirt VMs. This ensures that these resources can be restored successfully. |
| PB-8466 | Portworx Backup now captures NetworkAttachmentDefinition resources during KubeVirt VM backups. This ensures that NetworkAttachmentDefinition resources can be restored successfully. |
Fixes
| Issue Number | Issue Description | Severity |
|---|---|---|
| PB-6688 | Backup failed for Portworx volumes encrypted at the storage class level using CSI and Kubernetes Secrets on non-secure clusters. User Impact: Users had to rely on alternative encryption methods to secure their Portworx volumes. Resolution: Portworx Backup now successfully backs up volumes encrypted at the storage class level using CSI and Kubernetes Secrets on non-secure clusters. Affected Versions: 24.4.0 and earlier |
Minor |
| PB-9267 | In PX-Security enabled clusters, if the required user token is unavailable or misconfigured, backups for encrypted volumes fail. However, the system incorrectly marks the partial backup status as successful. User Impact: Users might assume that backups completed successfully, even if one or more volumes failed to back up. Resolution: Now, volumeInfo correctly marks volumes as failed when token retrieval fails and skips reconciliation for these volumes. This ensures that the partial backup status accurately reflects the backup state.Affected Versions: 24.4.0 and earlier |
Minor |