Can I upgrade Confluence to a newer version that was released before our licence expired?
The upgrade guide says:
1. Confirm that your license support period is still valid before you try to upgrade.
2. If your current license has expired but you have a new license with you, please update your license in Confluence before performing the upgrade.
If you forget to do this and your license has expired, you will receive errors during the upgrade process.
But why shouldn't I be able to upgrade to a version that was released when our licence was valid?
Note: We only need to upgrade so that we can migrate one wiki into anouther.
You're able to upgrade to any version that was released before your license expired. One thing to be aware of if you're upgrading to a version pre 2.10.4 is that we updated a bunch of our old versions to remove 3rd party code, the license can sometimes be tripped up on this as technically they may have been released after your license expired (see: http://www.atlassian.com/software/confluence/ArchiveConfluenceDownloads.jspa).
If this is the case for you, you're best off creating an evaluation license for the upgrade.
Yes, in theory, you should, but as the manual says, it does throw errors into the log file.
As you're only using it temporarily though, I'd simply use a developer license from the Confluence you are moving into (assuming that is licensed? If not, then you could try an evaluation license)
Here is my issue. I have a clustered install of 4.3.1. The license expired on June 30th 2015. Atlassian will not give me either a temporary license nor sell me a clustered license, but says I must buy Data Center license, as this is the new cluster software. That's fine. But I am in the middle of an upgrade from 4.3.1 to 5.4.4(the old cluster software). I have already upgraded development and staging environments to 5.4.4 when the license was still valid. Can I finish my upgrade to 5.4.4 in production with an expired license?
Thanks Nic. It was valid until June 30th, 2015. The thing that worries me are the errors in the log files. For those of us who know how to turn logging on and off, more and less, in the GUI, it's better to keep the chaff minimal. But I'd hate like hell to not have enough logging and miss some critical fact. I do have a qual instance that is still 4.3.1, so I will do the upgrade there first and then prepare for production.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
@Manon Soubies-Camy is an engineer who has been an avid Atlassian user since 2014. She helps companies of all sizes transform the way they work with the Atlassian stack, including Jira and Confl...
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