Hello,
I would like to upgrade confluence 5.4.2 to the latest version 5.6.4 on Linux.
Before upgrading the Confluence to the new version I would like to Test this on the staging/test machine first
so I don't break the production machine.
How do I go about it? I would like to reproduce the same setting.
Which files do I copy files from the current machine ?
Thanks,
pv
I suggest the following steps for creating a test server:
NOTE: this is a rough high-level outline - more steps may be necessary but this should get you going in the right direction.
mysqldump
to create the SQL back-up fileconfluence.cfg.xml
file to use the new test db name and log-in credentialssed
) to change the base URL in the SQL dump file prior to restoring to the test databaseThis should get you going on a test system where you can perform the upgrade as many times as necessary to get it working just the way you want. It's simple to revert back to your original Confluence version - just make sure you wipe out your Confluence home/install directories and the database before you attempt to put 5.4.2 back on the test system.
When you are satisfied with the procedure you've developed, you can then perform an in-place upgrade on your production server.
Hope all goes well for you.
Hi Stephen, When I try to logon to the localhost:8090 it still points back to the Original link: https://confluence.site.com I changed the confluence.cfg.xml Is there other configuration file that I need to change?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi PV,
This document should help in establishing a staging/test server for Confluence.
https://confluence.atlassian.com/display/DOC/Restoring+a+Test+Instance+from+Production
Cheers
Bhushan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bhushan, Could you please clarify these steps. Do I have to login to mysql tabase first to run these commands on my Test machine? Ensuring no contact with production systems To ensure no contact with external systems, you will need to disable both inbound and outbound mail services. 1. Disable global outbound mail by running the following database query: SELECT * FROM BANDANA WHERE BANDANAKEY = 'atlassian.confluence.smtp.mail.accounts'; 2. Disable space-level mail archiving by running the following database query: SELECT * FROM BANDANA WHERE BANDANAKEY = 'atlassian.confluence.space.mailaccounts'; Thanks, pv
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.