Production to QA data copy

[Janakiraman S]

Hi Team,

I was copying the data from Production (DC with single node) into our QA (Windows) environment. Therefore,

1) I replicated the Prod database into QA

2) I copied over the JIRA Home folder (without attachments and logs) into QA

3) Modified my dbconfig.xml to point to the replicated DB. 

While copying the Home folder, the security settings to it appears to be changed and I am unable to start the JIRA service. 

Keep running into the error although the Admins (user who triggers Jira service is part of this) have Full permissions to the jira.home folder 

Setup: JIRA couldn't create the jira.home directory

Ensure JIRA has permission to create and write to the jira.home directory

Have I missed any step that causes this error?

Would be very helpful if someone can share some leads how to overcome this error.

Thanks & Regards,

Janaki. 

[Janakiraman S]

Thank you for your feedback all.

The culprit was indeed (not to mention my stupidity too) the path in cluster.properties file. I had copied that also from Prod to QA and the path was different in both the environments. Therefore JIRA was crying that it wasn't able to write to the specified path.

[Radek Dostál]

And the 3rd idea to complete the trio since I don't see it mentioned - check your jira.home property.

As per https://confluence.atlassian.com/adminjiraserver/setting-your-jira-application-home-directory-938847747.html

• At the command prompt, enter the following command:

  set JIRA_HOME=C:\path\to\jira\home

• Add the above command to the \bin\start-jira.bat file.

I don't see this mentioned anywhere but you are starting Jira on winblows from one of the .bat files, it must know where the home is. I'm not that familiar with winblows on business level but I assume that either it must be either defined as a system environment variable, or defined in the start-jira.bat file (which would essentially add that variable on session level whenever you execute the script).

[Rilwan Ahmed]

Jira usually is started using user "jira". Create it if not exists, and grant required RW access to all folders

[Nic Brough -Adaptavist-]

A new machine is unlikely to have the same user permissions as production, at the operating system level.  You will probably need to change the owner or access permission on the directories you copied from the other machine. 

The usual thing to do is change the owner of the Jira home and in tall directories to the user that will be running the service