Issues restoring confluence
Asked by ChrisEricksonQBE:

We are migrating confluence over from a backup to docker. We have used the same version that was backed up(6.7.2). However when it gets to 90% restored we get a hibernation error. I can provide full logs of the restore.

2018-11-14 02:40:51,227 ERROR \[Caesium-1-3\] \[engine.jdbc.spi.SqlExceptionHelper\] logExceptions Connection reset  
2018-11-14 02:40:51,228 WARN \[Caesium-1-3\] \[v2.c3p0.impl.NewPooledConnection\] log \[c3p0\] A PooledConnection that has already signalled a Connection error is still in use!  
2018-11-14 02:40:51,228 WARN \[Caesium-1-3\] \[v2.c3p0.impl.NewPooledConnection\] log \[c3p0\] Another error has occurred \[ com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed. \] which will not be reported to listeners!  
com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed.

2018-11-14 02:40:51,233 WARN \[Caesium-1-3\] \[v2.c3p0.impl.NewPooledConnection\] log \[c3p0\] A PooledConnection that has already signalled a Connection error is still in use!  
2018-11-14 02:40:51,233 WARN \[Caesium-1-3\] \[v2.c3p0.impl.NewPooledConnection\] log \[c3p0\] Another error has occurred \[ com.microsoft.sqlserver.jdbc.SQLServerException: The connection is closed. \] which will not be reported to listeners!

Docker 6.7.2 Confluence

SQL server 2017


Answers:
author: Austin Smith
body: I am having the exact same issue as mentioned in the original post. I am migrating from a windows server w/ MSSQL backend to Linux w/ PSQL backend. Sad not to see an acceptable resolution here.


author: Stephen Sifers
body: Hello Christopher and welcome to the Community!

It looks like you have a solid understand of everything needed for your Confluence server migration. We just need to get past this hibernation error.

We will need a larger scope of the log/restore log as you mentioned to see what is happening.

There is some documentation around [XML backups that fail on restore](https://confluence.atlassian.com/conf67/troubleshooting-xml-backups-that-fail-on-restore-945103555.html).

For Your SQL 2017 instance, can you let us know if it's Express, Standard, or Developer?

Something else to keep in mind is that Confluence 6.7 does not support SQL 2017. Only Confluence 6.11 and above do. You can find more here at our [Supported Platforms](https://confluence.atlassian.com/conf67/supported-platforms-945103877.html).

We look forward to your response so we can get you migrated over to your new server.

Regards,  
Stephen Sifers

comments: author: ChrisEricksonQBE
body: Is there a way I can upload the logs somewhere? My plan was to migrate this then upgrade to a supported version. We are using Developer.


author: Stephen Sifers
body: Hello Christopher,

You will need to paste your log output here for us to review.

When this error is thrown, does Confluence continue to run?

Regards,  
Stephen Sifers


author: ChrisEricksonQBE
body: The logs are too big to paste. 4697 lines. It errors out when i try to post. Can I upload them somewhere?

Confluence continues to run. It looks like it does a roll back.


author: Stephen Sifers
body: Hello Christopher,

We are able to see that the database connection is closing while your restore is going through. Without the logs we are unable to see exactly why it is closing. We do have another method that will make migrating a bit easier.

Do you still have your other Confluence server available? If so, we would suggest you do a migration between servers instead of spinning up a new server and restoring the XML backup.

This method would allow for easier migration and will bring over the server as it was on the other server (including attachments).

Here are the instructions for [Migrating Confluence Between Servers;](https://confluence.atlassian.com/conf67/migrating-confluence-between-servers-945103880.html)[](https://confluence.atlassian.com/conf67/migrating-confluence-between-servers-945103880.html)To transfer Confluence to another server you will copy the home and install folders straight into an identical external database and user management setup. If your new server is using a different operating system there may be some additional changes at step 4.

1. Run the Confluence installer on your new server
2. Shut down Confluence on both your old and new servers
3. If you're using Oracle or MySQL, copy [the drivers](https://confluence.atlassian.com/conf67/database-jdbc-drivers-945103513.html) from your old server to the new one
4. Delete the contents of the home directory on your new Confluence server, then copy in the contents of the home directory from your old Confluence server.
5. Make any additional changes required for your environment.
6. [If you're changing the location of the home directory...](https://confluence.atlassian.com/conf67/migrating-confluence-between-servers-945103880.html#)
7. [If you're moving your database...](https://confluence.atlassian.com/conf67/migrating-confluence-between-servers-945103880.html#)
8. [If your new server has a different operating system...](https://confluence.atlassian.com/conf67/migrating-confluence-between-servers-945103880.html#)
9. Copy the \<confluence-install\>/conf/server.xml file from your old server to the same location on your new server
10. If you use a data source, ensure the data source points to the new database. See [Configuring a datasource connection](https://confluence.atlassian.com/conf67/configuring-a-datasource-connection-945103537.html).
11. Start Confluence, then head to **General configuration** \> **License Details** to add your license key

We strongly recommend you perform a [rebuild of your content indices](https://confluence.atlassian.com/display/CONFKB/How+to+rebuild+the+content+indexes+from+scratch) after performing a migration, to ensure Confluence search works as expected.

If this is not an option, please let us know.

Regards,  
Stephen Sifers


author: ChrisEricksonQBE
body: We ended up using the internal database to restore. That was successful. You can close this ticket.


Tags: confluence-server

server