Time to restor jira data in jira 5.2.5

[assia abde]

it is normal that data recovery of jira (4.1.2) in jira 5.2.5 takes more than 70 hours(still in progress)? knowing that the xml file is 1.5GB and the machine (VMW) has the following configuration: 3 GB RAM, Win Server 2008 64 bit, 4 processors
jira connected with MSSQL 2005 which is on another server

[assia abde · Accepted solution]

I had to redo the entire service configuration jira

I await the end of the updating custom fields

I presice that I executed this request "
ALTER DATABASE [DATABASE-JIRA] SET READ_COMMITTED_SNAPSHOT ON"

thank you all

[codelab expert]

Please have a look into the log file of jira. Perhaps you have an OutOfMemoryError because of the size of your backup file. Try to increase the memory of jira (xmx and xms parameter).

[assia abde]

there is no OutOfMemory

I'll try to restore Data in the HSQL in local server (it is just to verify that the problem is not MS SQL)

[Janet Albion]

This sound like a known problem discussed at https://confluence.atlassian.com/pages/viewpage.action?pageId=264045011

[assia abde]

I had to redo the entire service configuration jira
I await the end of the updating custom fields

[assia abde]

I presice that I executed this request "
ALTER DATABASE [DATABASE-JIRA] SET READ_COMMITTED_SNAPSHOT ON"

thank you all

[Nic Brough -Adaptavist-]

That's far too long - it took 2 hours to restore our test system from a much larger xml file. Also using a VM, but with 4Gb RAM.

I suspect there's something wrong with the VM or Operating system setup. Do you have antivirus running on it? That can kill java processes.

[assia abde]

yes, there is a ESET NOD32 antivirus

it is 70h, which is at 92% "data during upgrade to the most recent version"