this is actually not a production issue (yet), but a request for knowledge.
Challenge: We need to move the Confluence database from one server to another. Everywhere I see, I see guides for migrating from one database to another, which isn't exactly what I had in mind.
Is it possible to simply move the database from one MS SQL server to another, change something in an XML file somewhere, and then be good to go ?
What's the procedure for doing that ?
I've indicated v4.2, but it's no problem to spend some time upgrading to the latest version before we move, if that makes things easier.
Thanks in advance :)
Yes, if you are NOT changing the type of database and you are NOT changing the application, you can simply take an entire database, copy it to another server and use it without having to do any more work.
Your steps should be simple, as you've already started to suspect:
You won't even need to worry about re-indexing or anything difficult like that.
This is exactly what I tried to do, and it did not work.
The Jira plugin failed, and reported that it was not licensed.
I tried re-entering the Confluence License, but no dice.
Rolling back to my old database server was easy though, and worked without a hitch.
How should I troubleshoot this?
This weekend I'm going to to give this another shot, after upgrading Confluence to 4.3
I will backup my Confluence db, and restore it to my new server, and edit the conflunce config file with the proper connection string.
What logs should I collect if I have problems?
There should be a file like "atlassian-confluence.log" in the logs directory under the confluence "home" directory. That's worth a read.
You can also simply try the upgrade again - sometimes, it can be recovered by stopping and starting the application, although it's unlikely (on the other hand, that will give you an error in the logs as well)
Following the instructions that Nic provided above didn't work. Although the config file was updated properly while the Confluence service was stopped, the web site wouldn't respond. Was forced to do a fresh install pointing to a blank shell database on the destination server and then restore the backed up data.
One oversight that may have been an issue was the JVM was not restarted. I don't know if this would have fixed the issue.
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
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!
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