Submit Feedback
Legacy Knowledge Base
Published Jul. 2, 2025

Liferay DXP starts as a clean installation after restoring an on-premises DXP backup in Liferay PaaS

Written By

Jose Jimenez

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.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • Some databases manage the table names in lower case (e.g., PostgreSQL).
  • A backup coming from this kind of databases normally is not going to work in Liferay PaaS, and as a result of the restore you will get the behavior of a clean/empty installation of Liferay DXP in the Liferay PaaS platform.
  • If you are in this situation you can view duplicated table names, with lower case and camel case names, in the restored DXP database. For example: Release_ and release_.

Environment

  • Liferay DXP 7.2

Resolution

  • Create an intermediate database in MySQL and rename all the Liferay Cloud table names to camel case before generating and uploading the backup of the on-premises installation. 
  • Attached you can find a useful script for a basic 7.2.10 installation that you can use as a base script for this operation. Please, check if you need to add or remove any other table names because each installation is going to be different depending on the installed plugins and some plugins as for example your custom plugins or other downloaded plugins from the marketplace are not considered in this basic script.

Additional Information

 

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?