nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Boards are not restoring from backup to db

gandalf1990

Hi,
we have an issue with backup boards to database. After restoring xml files all tables are creating, complementing but tables with boards and sprints are empty.
We are migrating from PostgreSQL - 9.5.6 to MSSQL 2012 on Azure.
Let me describe the whole process which I used.
So our company decided to migrate to mssql. On our production server we have JIRA 7.3.0 but we want to use the newest version. So i copied our production server and i upgraded to newest version. Next I copied attachments, indexes and plugins to our new VM. Then I made restore. Then I started new VM.
First issue that i see after connecting to new db is issue due to collation error. You are recommending to use Latin1_General_CI_AI so we choose this collation but after fist jira initializiation there was an error with suggestion to use SQL_Latin1_General_CI_AI but on Azure we cant choose these collation, only Latin1_General_CI_AI.
After these i made backup from zip file but boards didnt restore. I was getting java.lang.IllegalArgumentException: Unsupported field encountered: binary but after restarting server the error dissapeared. Then i made indexing.
Summarazing the whole things. Tables for boards, i.e AO_60DB71_RAPIDVIEW are still empty.
I used your instructions on attlassian sites but there are not helpful for me.
Any ideas how to fix that issue?

Accepted answers

Andy Heinzer

Just to circle back on this case:

We found that this error was caused by a bug to a plugin, Xporter. In turn there exists a bug report for this in https://jira.xpand-addons.com/browse/XPORTER-834

The problem here is that older versions of this plugin would create XML backups that could not be restored in Jira. We were able to resolve this by going back to the source Jira instance and updating this plugin there to a version such as 5.1.1 or higher. That way we could create an updated XML backup that can then be restored in the destination instance.

All comments

Nic Brough -Adaptavist-

You don't say how you backed up or restored the database - you just say "made backup". Was this XML via the UI, or a database dump and restore or something else?

gandalf1990

Via UI. But i say that i made it from zip so I thought that was clear.

Nic Brough -Adaptavist-

I'm afraid it was not that clear, no, but it is now, and it's the only thing that was not clear.

An xml export and import should have restored everything. Missing boards suggests the restoration has not worked properly.

Do you have any errors in the logs from when you did the upgrade or the xml restoration?

Andy Heinzer

It is possible that the XML import process failed, but Jira still appears to work anyways. The logs from the time of the import though would indicate if there was a problem here. I'm expecting there is probably some kind of SQL exception that happens during this XML restore with more details.

The XML import will have a percentage that should run from 1% to 100%. If you're logs don't reach 100%, then the import was incomplete and we should look more closely at the error in the logs from that time in order to understand how to fix this.

Andy Heinzer

The interesting parts of these logs to me is this:

2017-11-29 09:13:30,416 automation-queue-claimer:thread-1 WARN [c.c.j.p.automation.queue.JiraAutomationQueueExecutor] Queue claimer could not claim from queue yet due to SQL exception. This is most likely due to the active object tables not being initialised yet (Exception: SQLServerException: Invalid object name 'dbo.AO_589059_AUTOMATION_QUEUE'.). Retrying...
2017-11-29 09:13:33,992 JiraImportTaskExecutionThread-1 ERROR Filip.Gorloff 544x382x1 ibfiv9 178.73.11.84,165.225.84.61 /secure/admin/XmlRestore.jspa [c.a.j.bc.dataimport.DefaultDataImportService] Error importing data: java.lang.IllegalArgumentException: Unsupported field encountered: binary
java.lang.IllegalArgumentException: Unsupported field encountered: binary

That specific table 'AO_589059_AUTOMATION_QUEUE' is specifically created by the Automation Lite for Jira plugin

Since you're seeing this error, it indicates that this plugin is not yet installed on this destination instance at the time of the restore. As such, Jira can't create the table needed to store that plugin data and in turn we're seeing these SQL exceptions. But my concern is that this error is a symptom of other plugins that might be missing or incompatible with this Jira.

You might need to update these plugins on the destination instance before the restore of the XML backup, otherwise the data might not be restored. This tends to be easier to manage when you do the database migration as a separate process to the upgrade of Jira. By both upgrading and migrating the database at the same time, this complicates the process needed in order to restore all the data in the XML backup properly.

It is not to say it is impossible to both migrate and upgrade simultaneously, but in my experience it tends to be much easier when migrating everything (server, app, database, etc) like this to just follow these steps:

install the same version of Jira on the destination instance,
Connect this Jira instance to a new empty database using either the Jira Config Tool or by editing the dbconfig.xml
copy the $JIRAHOME/plugins/installed-plugins/ folder from source to destination, also copy the $JIRAHOME/data into destination,
then restart the destination Jira once more to make sure this loads all your plugins. When Jira starts up with an empty database, you will get the initial setup wizard where you can then use the 'import existing data' link to import your XML backup
and then do the XML import in order to restore your data to this new database type.

Once this is done and working, then I would recommend upgrading Jira to the latest version.

If you try to both upgrade and migrate these at the same time, the versions of your Jira plugins are unlikely to be compatible with this newer version of Jira and as such you would have to manually update each of these on the filesystem and restart Jira before doing this initial setup wizard where you can restore this.

gandalf1990

Thanks for your answer. Today we are upgrading our production JIRA to newest version. Next step is to try migrate JIRA as you describe. I will let You know if we have succeeded.

gandalf1990

Ok, so it doesn't work I did everything as it is written and it doesnt help. The same situation as it was before. Ale thing has been imported except boards and sprints. I will provide logs but insterting them there is not a best solution. Can i provide them to You in another way ?

Andy Heinzer

Hi @gandalf1990,

I recreated a support request on your behalf for this issue. Please upload the logs to this case:

https://getsupport.atlassian.com/servicedesk/customer/portal/20/GHS-101918

From there we can take a closer look at what Jira is doing during this process.

Regards,
Andy

Andy Heinzer

Just to circle back on this case:

We found that this error was caused by a bug to a plugin, Xporter. In turn there exists a bug report for this in https://jira.xpand-addons.com/browse/XPORTER-834

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

migration

ms-sql

postgres