Legacy Knowledge Base
Published Jun. 30, 2025

Mitigating Cloud Backup Breaking Change

Written By

Justin Bowman

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

  • The Liferay Cloud Backup image version 5.14.0 contains a breaking change that removed support for downloading and restoring backups created with client-side encryption. The goal was to release this change in a major version but it was mistakenly flagged for 5.14.0.
  • Backups created using version 4 are created using client-side encryption. This means that, in the event the backup service is updated from any 4.x version to 5.14.0, the backups created in 4.x will not be accessible.

Environment

  • Liferay PaaS

Resolution

  • When upgrading from 4.x, please upgrade to 5.13.1 or lower.
  • Wait 30 days for old 4.x backups to be replaced by new 5.x backups.
  • After 30 days, it is safe to update to 5.14.0.

Additional Information

  • It is safe to update to 5.14.0 if no 4.x backups exist. This means that if the project never used a 4.x image or was updated from 4.x over 30 days ago, this information can safely be ignored.
Did this article resolve your issue ?

Legacy Knowledge Base