Upgrade confluence to latest version
Asked by me:

Hi I want to upgrade to the latest version of confluence

FROM (7.9.1 Build number 8505)

TO (7.13.0 Build number 8703)

what step exactly should I do, I read links that exist in the last section of this post but I think it's not completed. (e.x. 1-databse and build number compatibility 2-what happen when I copy home directory to new server does it required to backup from postgres and restore on new server?)

any one can tell me what should I do step by step?

Links:

[Confluence build information (atlassian.com)](https://developer.atlassian.com/server/confluence/confluence-build-information/)

[Upgrading Confluence \| Confluence Data Center and Server 7.13 \| Atlassian Documentation](https://confluence.atlassian.com/doc/upgrading-confluence-4578.html)

[Upgrading Confluence Manually \| Confluence Data Center and Server 7.13 \| Atlassian Documentation](https://confluence.atlassian.com/doc/upgrading-confluence-manually-255363437.html)

Thanks,


Answers:
author: Nic Brough -Adaptavist-
body: The steps for upgrading are given in the documentation you have linked to,

Instead of asking us for exact "steps to upgrade" that we can't possibly give you because we do not have your installation in front of us, can you tell us where you are stuck? What are you not understanding in the docs? Or what is going wrong? Or what do you think you need to do differently?

comments: author: me
body: first of all one most importatnt things that I didn't know is about different between \[bin\] and \[tar.gz\] installation (bin has wizard for upgrade but tar.gz not same)

another things is database export from \[prod\] and import on \[stage\] server not clear for me.

I have 2 environment prod, stage.

I want to upgrade stage first if everything was ok, upgrade prod.

I've done several thing and encounter many errors to figureout what shoud I do finally.

what I understand:

1-in prod

database upgrade automatitically will be done on prod if I put "share home directory" + "install directory of 7.13.0" + "home data" in the path and start confluence 7.13.0

2-in stage

I have 7.9.1 and

and I've done below step to start it correctly (this part not clear for me on documentaion)

A) database stuff:

su - postgres

#export postgredb on prod  
pg_dump confluence \> outfile

#cleanup postgredb on stage

DROP DATABASE confluence;

CREATE USER "confluence" PASSWORD 'MYPASS';  
CREATE SCHEMA confluence;  
GRANT ALL ON SCHEMA confluence TO "confluence";  
GRANT ALL ON ALL TABLES IN SCHEMA confluence TO "confluence"  
CREATE DATABASE "confluence" WITH ENCODING='UTF8' OWNER="confluence" CONNECTION LIMIT=-1;

#import postgredb on stage

psql confluence \< outfile

database upgrade automatitically will be done on stage if I put "share home directory" + "install directory of 7.13.0" + "home data" in the path and start confluence 7.13.0

in this way all suff work correctly restore correctly (before that I thought when I create backup job on confluence compress file that produce contain all this stuff but that file only contain pages not macros not template and ... )


author: Nic Brough -Adaptavist-
body: This does not look like you are following the documentation. The loss of macros is screaming that you're not doing a migration or upgrade at all, and I really cannot work out from this what you are actually doing.


author: me
body: yes as I mention after I doing this stuff findout what really happpen in upgrade process.

while if little more explanaintion was on upgrade guide pages, probably this proceess were more clear for me.

Thanks,


author: Nic Brough -Adaptavist-
body: I'm sorry, I was a bit short previously, but I've re-read and I think I understand a bit more now.

I think we should step back and look at one thing at a time, you've got several things to talk about in your posting, and I get confused when I jump around them. But to simplify it:

You mentioned the installer (bin) and the archive (tar.gz) - these are both capable of doing an upgrade, but you need to do the upgrade with each very differently. The installer is the recommended way to do an upgrade, and it is a lot easier to use than the archive, but it is a bit more flexible than the installer, and allows you to upgrade systems that the installer cannot. You'll need to decide which one you want to use (start by thinking about what you might have done differently to a "standard" install and why the installer may not be able to handle automatically!)

The rest of the stuff I want to talk about is better done by summarising what the upgrade process does and what steps you take to do it - if you have questions about any of this, then that will be what I wanted to talk more about.

Assumptions:

* You have a version 7.9 Confluence installed and running fine, with some data
* You have a licence key that expires after 7.13 was released
* You have downloaded the installer
* You have taken a full backup (a database dump and a copy of the attachments)

Process:

* Stop Confluence
* Run the installer, telling it where the home directory for the existing installation is
* Answer the rest of the questions it has, and note down what files it says it is going to overwrite
* Let it run to completion
* Merge any changed files back in
* Start Confluence (if the installer hasn't)
* Go to admin -\> manage apps and check the installed apps, clicking upgrade for each one that needs an update

This should leave you with an upgraded Confluence, with all your data (including all your macros, as they're in the database, with your pages and the rest)

You also mention a migration to another server. This is fine, but you should consider it to be totally separate from the upgrade. Do not try to move and upgrade at the same time, do it **sequentially**. Either migrate the 7.9 to a new server, and then upgrade it, or upgrade the 7.9 as it is now, and move the resulting 7.13 to a new server. (By all means, do both steps in one go, but do them as separate steps - last time I did this I moved the Jira and Confluence first thing in the morning, had brunch with some friends, and then spent the afternoon doing the upgrade, all in one change window. One of the upgrades failed, so we rolled back Jira, but only on the new server - the migration had worked fine, and didn't need rolling back)


author: KAGITHALA BABU ANVESH
body: Hello [@me](/t5/user/viewprofilepage/user-id/2563778) ,

If when ever there an upgrade required, Please check the supported software's first.

<https://confluence.atlassian.com/doc/supported-platforms-207488198.html>

Any database or others you can check above.

Next you have to Check the existing plugins compatibility for the targeted Confluence version.

[https://confluence.atlassian.com/upm/checking-app-compatibility-with-application-updates-273875705.html#:\~:text=To%20check%20compatibility%20of%20your,check%20or%20JIRA%20update%20check.](https://confluence.atlassian.com/upm/checking-app-compatibility-with-application-updates-273875705.html#:~:text=To%20check%20compatibility%20of%20your,check%20or%20JIRA%20update%20check.)

Before the upgrade, please keep a backup of Installation directory and Home Directory.

Thanks,

Anvesh

comments: author: me
body: Hi Anvesh, thank you for reply.

links that you mention reviewed before start to upgrade.

there is no issue about supported 'software" or "macro".

would you please tell me step by step about upgrade process?

Thanks,


Tags: confluence-server

migration

server

upgrade