procedure to refresh database one jira service managment v10.3.4

[infra système]

Hi,

We are running Jira Service Management in a cluster of two VMs with a PostgreSQL database in the production and acceptance (AQ) environments. We would like to perform a refresh of the acceptance database from production in order to have two identical environments.

Could you please provide us with a detailed procedure to achieve this?

Thank you

[Rilwan Ahmed]

Hi @infra système ,

Welcome to the community !!

https://confluence.atlassian.com/adminjiraserver/creating-a-test-environment-for-jira-966063324.html describes the step to sync lower environments with production data.

[infra système]

Hi @Rilwan Ahmed 

Thank you for the documentation.

So, we have to copy these 3 directories from production to acceptance:

• production installation directory (Is it really necessary to copy this directory? Doesn’t it only contain the binaries?):
  ls -lrt /appli/jsm/jirasoftware/atlassian-jira-servicedesk-10.3.4-standalone/
  total 160
  drwxr-x---. 2 jira jira 6 Mar 5 2025 webapps
  drwxr-x---. 2 jira jira 113 Apr 24 13:33 sbom
  drwxr-x---. 18 jira jira 4096 Apr 24 13:34 atlassian-jira
  drwxr-x---. 2 jira jira 61 Apr 24 13:34 tomcat-docs
  drwxr-x---. 2 jira jira 41 Apr 24 13:34 external-source
  drwxr-x---. 2 jira jira 61440 Apr 24 13:34 licenses
  drwxr-x---. 2 jira jira 4096 Apr 24 13:34 lib
  drwxr-x---. 3 jira jira 4096 Apr 24 15:08 conf
  drwxr-x---. 2 jira jira 4096 Jun 4 10:44 bin
  drwxr-x---. 3 jira jira 42 Sep 12 15:37 work
  drwxr-x---. 2 jira jira 12288 Sep 15 08:16 logs
  drwxr-x---. 4 jira jira 143 Sep 15 08:40 temp
  -rwxr-x---. 1 jira jira 3362 Feb 13 2025 README.md
  -rwxr-x---. 1 jira jira 2401 Feb 13 2025 NOTICE
  -rwxr-x---. 1 jira jira 6330 Feb 13 2025 CONTRIBUTING.md
  -rwxr-x---. 1 jira jira 21516 Feb 13 2025 BUILDING.txt
  -rwxr-x---. 1 jira jira 3517 Mar 5 2025 README.txt
  -rwxr-x---. 1 jira jira 5668 Mar 5 2025 README.html

• production home directory
  # ls -lrt /appli/jsm/jirasoftware-home/
  total 60
  drwxr-x---. 2 jira jira 76 Apr 24 13:37 monitor
  drwxr-x---. 2 jira jira 128 Apr 24 13:38 keys
  drwxr-x---. 5 jira jira 79 Apr 24 15:11 import
  drwxr-x---. 7 jira jira 114 Apr 24 15:11 plugins
  drwxr-x---. 2 jira jira 59 Apr 24 15:11 authentication-plugin-keys
  drwxr-x---. 6 jira jira 71 Apr 25 11:05 data
  drwxr-x---. 3 jira jira 24 May 1 16:52 proforma.cache
  drwxr-x---. 2 jira jira 4096 Jun 2 10:02 logos
  drwxr-x---. 5 jira jira 4096 Jun 3 10:24 export
  drwxr-x---. 2 jira jira 76 Jun 4 10:39 secured
  drwxr-x---. 2 jira jira 4096 Jun 5 00:34 analytics-logs
  drwxr-x---. 6 jira jira 97 Jun 12 18:14 caches
  drwxr-x---. 2 jira jira 4096 Jun 25 15:34 localq
  drwxr-x---. 5 jira jira 92 Sep 11 19:49 customisations-backup
  drwxr-x---. 5 jira jira 92 Sep 12 15:40 customisations
  drwxr-x---. 4 jira jira 8192 Sep 15 08:04 log
  drwxr-x---. 3 jira jira 8192 Sep 15 08:43 tmp
  -rwxr-x---. 1 jira jira 165 Apr 24 13:36 secrets-config.yaml
  -rwxr-x---. 1 jira jira 1145 May 12 07:23 dbconfig.xml.bak
  -rwxr-x---. 1 jira jira 197 Jun 5 14:13 cluster.properties
  -rwxr-x---. 1 jira jira 1153 Sep 12 15:39 dbconfig.xml

• production shared home directory ( nfs volume)
  # ls -lrt /appli/jsm/jirasoftware-shared/
  total 68
  drwxr-x---. 2 jira jira 4096 Apr 24 13:38 keys
  drwxr-x---. 7 jira jira 4096 Apr 24 15:11 plugins
  drwxr-x---. 6 jira jira 4096 Apr 25 11:05 data
  drwxr-x---. 2 jira jira 4096 Jun 2 10:02 logos
  drwxr-x---. 6 jira jira 4096 Jun 5 14:13 caches
  drwxr-x---. 3 jira jira 4096 Jun 5 14:46 proforma.cache
  drwxr-x---. 6 jira jira 4096 Jun 17 11:43 import
  drwxr-x---. 6 jira jira 4096 Aug 11 15:26 export
  drwxr-x---. 3 jira jira 4096 Sep 10 12:30 data-pipeline
  drwxr-x---. 2 jira jira 4096 Sep 12 15:39 secured
  drwxr-x---. 2 jira jira 4096 Sep 15 00:53 analytics-logs
  drwxr-x---. 2 jira jira 4096 Sep 15 08:44 node-status
  drwxr-x---. 2 jira jira 4096 Sep 15 08:44 tmp
  -rwxr-x---. 1 jira jira 165 Apr 24 13:36 secrets-config.yaml

Regards,

Alex

[Rilwan Ahmed]

Hi @infra système ,

Yes. Copying the entire production installation directory 

• copies your exact production setup including all configs, plugins, customizations, and the application files.

• It's useful if you want your test environment to mirror production exactly without reconfiguring everything.

• Makes the sync quicker because you don’t have to reinstall or reconfigure Jira.\

Please note:

1. Edit <installation-directory>/atlassian-jira/WEB-INF/classes/jira-application.properties to point to your test home directory. 
   CLUSTER For DC, make this change on every node.

2. Edit <home-directory>/dbconfig.xml or  <installation-directory>/server.xml (older versions) to point to your test database. 

3. <local-home-directory>/cluster.properties to point to your test shared home directory. Make this change on every test node. 

I suggest you follow each and every step as described in https://confluence.atlassian.com/adminjiraserver/creating-a-test-environment-for-jira-966063324.html