Need to restore all data in Jira from MS SQL backup

Hi Team,

SEN-3355779

We have Jira Server installed on Linux server with MS SQL server database & it got crashed due to unexpectedly restart the server. Now it is not working properly. Tomcat is shutting down automatically. We need to setup again Jira with Old data.

We have SQL Database, Old Jira Home Directory, Old installed directory.

Now Please provide us the steps to configure jira with old database and all previous plugins & settings.

1 answer

0 vote

There's no point - if you restore exactly everything as before, it's still not going to start. If your database is trashed, restoring it will just give you a trashed database and you need to go for a backup. If you've damaged the installation files, then you'll want a clean Jira with the old database imported. And so-on.

You need to know WHY it's failed before you can do any form of recovery.

When you try to start this Jira, then what errors are you getting in the logs? Read atlassian-jira.log and catalina.out to see what it is doing.

Please find below logs.

2014-08-28 19:41:35,168 localhost-startStop-1 ERROR [internal.util.concurrent.RunnableTimedExecution] Closing runnable for context NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.jira.plugins.jira-importers-redmine-plugin, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

2014-08-28 19:41:45,326 localhost-startStop-1 ERROR [internal.util.concurrent.RunnableTimedExecution] Closing runnable for context NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.upm.atlassian-universal-plugin-manager-plugin, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

2014-08-28 19:41:55,368 localhost-startStop-1 ERROR [internal.util.concurrent.RunnableTimedExecution] Closing runnable for context NonValidatingOsgiBundleXmlApplicationContext(bundle=com.atlassian.support.stp, config=osgibundle:/META-INF/spring/*.xml) did not finish in 10000ms; consider taking a snapshot and then shutdown the VM in case the thread still hangs

Aug 28, 2014 7:42:05 PM org.apache.coyote.AbstractProtocol stop

INFO: Stopping ProtocolHandler ["http-bio-8080"]

Aug 28, 2014 7:42:06 PM org.apache.coyote.AbstractProtocol destroy

INFO: Destroying ProtocolHandler ["http-bio-8080"]

log4j:WARN No appenders could be found for logger (org.springframework.context.annotation.CommonAnnotationBeanPostProcessor).

log4j:WARN Please initialize the log4j system properly.

Those are usually indicative of a broken installation, or sometimes, an under-resourced Jira, although you should have a stack of other errors in the second case.

What else does the log say?

Hi Nic,

I have installed Jira on new server with old database. It was working propely on new server but after reindexing in Jira I am getting below error.

___ FAILED PLUGIN REPORT _____________________

3 plugins failed to load during JIRA startup.

'com.atlassian.jira.gadgets' - 'Atlassian JIRA - Plugins - Gadgets Plugin' failed to load.

Application context initialization for 'com.atlassian.jira.gadgets-plugin' has timed out

It has the following missing service dependencies :

&dashboardService of type (objectClass=com.atlassian.gadgets.dashboard.DashboardService)

&dashboardService of type (objectClass=com.atlassian.gadgets.dashboard.DashboardService)

It was loaded from /var/atlassian/application-data/jira/plugins/.bundled-plugins/jira-gadgets-plugin-6.2.7.jar

'com.atlassian.jira.collector.plugin.jira-issue-collector-plugin' - 'JIRA Issue Collector Plugin' failed to load.

Application context initialization for 'com.atlassian.jira.collector.plugin.jira-issue-collector-plugin' has timed out

Ok, that's indicative of the high load at startup time overloading your system.

Start with https://confluence.atlassian.com/display/JIRAKB/JIRA+System+Plugin+Timeout+While+Waiting+for+Plugins+to+Enable

As per our analysis Jira is using crowd for the authentication. I have installed Jira on new server with old database. It was working propely on new server but after reindexing in Jira I am getting authentication error & unable to login into Jira.

I am using SQL Server for Jira database. Can we modify database so Jira will use jira internal directory for jira authentication instead of crowd.

Plugin issue is resolved.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,293 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot