- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Clone an environment
If you want to clone an environment, for example to copy your production data to a staging environment, you can transfer your data and configurations.
Careful
The following statements are global statements. It is possible that the directories are placed in different places on your server, or that you have components that deviate from the basic installation, for example if you have an NFS vault. If in doubt, please consult the Constellio support team.
Single-instance environment
The following are the data directories for the environment copy:
- To stop Constellio : sudo systemctl stop constellio
- To stop Solr: sudo systemctl stop solr
- Configurations: /opt/constellio/conf/
- Contents: /opt/constellio/contents/
- Application directories: /opt/constellio/webapp*
- Transactional logs: /opt/constellio/transaction_log/
- Database index (records): /var/solr/configsets/
- Artemis files (Constellio 11+): /opt/constellio/artemis
Important
- If the destination environment is a new environment, Solr may have an error with Jetty: "no ok status: 414, message:Request-URI Too Long". It is then necessary to increase "solr.jetty.request.header.size" (see online documentation). Example: 8192 → 819200*
- Check if there are any configurations to copy to constellio.properties when copying a distributed→distributed or single→distributed environment. Not all configurations need to be copied so inquire about which ones are to keep. For example, the server URL configuration needs to be changed
- Ensure that permissions on the server on copied folders/documents are not changed. For example, you can use rsync with the -a option to do this
Distributed or multi-tenant environment
Since most distributed or multi-tenant environments are not standard (number of machines, load distribution software, etc.), it is best to consult with the Constellio support team.
Was this article helpful?