$ oc get dpa -n openshift-adp -o yaml > dpa.orig.backup
The release notes for OpenShift API for Data Protection (OADP) describe new features and enhancements, deprecated features, product recommendations, known issues, and resolved issues.
The OpenShift API for Data Protection (OADP) 1.4.0 release notes lists resolved issues and known issues.
Previously, while restoring the deleted application namespace, the restore operation partially failed with the resource name may not be empty
error in OKD 4.16.
With this update, restore works as expected in OKD 4.16.
OADP-4075
Previously, Velero was using the earlier version of SDK where the Spec.SourceVolumeMode
field did not exist. As a consequence, Data Mover backups failed in the OKD 4.16 cluster on the external snapshotter with version 4.2.
With this update, external snapshotter is upgraded to version 7.0 and later. As a result, backups do not fail in the OKD 4.16 cluster.
OADP-3922
For a complete list of all issues resolved in this release, see the list of OADP 1.4.0 resolved issues in Jira.
While performing a backup of any application with Noobaa as the backup location, if the checksumAlgorithm
configuration parameter is not set, backup fails. To fix this problem, if you do not provide a value for checksumAlgorithm
in the Backup Storage Location (BSL) configuration, an empty value is added.
The empty value is only added for BSLs that are created using Data Protection Application (DPA) custom resource (CR), and this value is not added if BSLs are created using any other method.
OADP-4274
For a complete list of all known issues in this release, see the list of OADP 1.4.0 known issues in Jira.
Always upgrade to the next minor version. Do not skip versions. To update to a later version, upgrade only one channel at a time. For example, to upgrade from OpenShift API for Data Protection (OADP) 1.1 to 1.3, upgrade first to 1.2, and then to 1.3. |
The Velero server has been updated from version 1.12 to 1.14. Note that there are no changes in the Data Protection Application (DPA).
This changes the following:
The velero-plugin-for-csi
code is now available in the Velero code, which means an init
container is no longer required for the plugin.
Velero changed client Burst and QPS defaults from 30 and 20 to 100 and 100, respectively.
The velero-plugin-for-aws
plugin updated default value of the spec.config.checksumAlgorithm
field in BackupStorageLocation
objects (BSLs) from ""
(no checksum calculation) to the CRC32
algorithm. For more information, see Velero plugins for AWS Backup Storage Location. The checksum algorithm types are known to work only with AWS.
Several S3 providers require the md5sum
to be disabled by setting the checksum algorithm to ""
. Confirm md5sum
algorithm support and configuration with your storage provider.
In OADP 1.4, the default value for BSLs created within DPA for this configuration is ""
. This default value means that the md5sum
is not checked, which is consistent with OADP 1.3. For BSLs created within DPA, update it by using the spec.backupLocations[].velero.config.checksumAlgorithm
field in the DPA. If your BSLs are created outside DPA, you can update this configuration by using spec.config.checksumAlgorithm
in the BSLs.
You must back up your current DataProtectionApplication
(DPA) configuration.
Save your current DPA configuration by running the following command:
$ oc get dpa -n openshift-adp -o yaml > dpa.orig.backup
Use the following procedure when upgrading the OpenShift API for Data Protection (OADP) Operator.
Change your subscription channel for the OADP Operator from stable-1.3
to stable-1.4
.
Wait for the Operator and containers to update and restart.
To upgrade from OADP 1.3 to 1.4, no Data Protection Application (DPA) changes are required.
Verify the installation by following steps from the Verifying the upgrade section.