Locating Configurations in OSGi in Backup
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
- Where could I locate files such as modules, Marketplace packages and WAR files from the backup?
- What are the files we take from Document Library in the backup?
Resolution
-
What are the files we take from Document Library in the backup?
- In PaaS or SaaS environments, we only back up the
/opt/liferay/data directory, which contains the document library. Then, we back up the database, which includes all the schema details.
-
Where could I locate files such as modules, Marketplace packages and WAR files from the backup?
- Before restoring the backup, a build containing all the configurations must be deployed to the environment. During this build process, Kubernetes pulls a Docker image from GCR for deployment. This Docker image is custom-built and contains all the necessary modules.
- The command below creates a Dockerfile that copies all the configurations to the Docker image
./gradlew clean deploy createDockerfile
-
- The deployments from the build process through repositories such as GitHub, GitLab, etc. Whenever the deployments are passed through CI, it will be submitted as part of the deployment. These deployments, configurations and customizations would be included in the repository where they are building from.
Did this article resolve your issue ?