Legacy Knowledge Base
Published Sep. 10, 2025

Need to clone a Production environment to a lower one

Written By

Debora Vita

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

  • We had some issues upgrading our Production environment about a year ago and had to roll it back. Our Non Production and Pre-production environments remained on the newer version of Liferay (at the time) and we haven't attempted an upgrade since. We need to clone our Production environment down to our Pre-production environment. We would shut down our current Pre servers to make sure the new server doesn't clash. We would like to receive some guidance on where/what to change since our production servers need to stay up.

Environment

  • DXP 7.3

Resolution

  • The most important aspects will be ElasticSearch and any SSO/LDAP configuration. Elasticsearch settings can be updated in a .config file, which you can find in /$Liferay_home/osgi/configs. You should be able to copy an existing one and modify it for the new environment, but please be sure to validate all of the settings in it before starting up the Pre-production environment.
  • The database will have all of your production data, configuration, etc. So it is needed to reset the ES to use a non-prod ES and change the SSO for non-prod configuration. 
  • Other thing you may want to or need to do is update virtual hosts.
  • Remote staging would also be a possible concern if you’re using that and mail configurations as well.

 

Did this article resolve your issue ?

Legacy Knowledge Base