Does anyone know where I can find a maintained listing of upgrade paths for the Network edition versions?
I got caught with my pants down last night trying to do an upgrade... I made the assumption that any v6.x release could be upgraded to any v7.x release. This is not the case and got me stuck. I had assumed you could go from 6.0.16 to 7.1.4, but this is a no-go...
Thanks! -Cheers, Peter.
Upgrade paths are always in the relevant Release Notes for each version of ZCS.
Where prey tell in the release notes?
The only section that seems to references it is "Upgrade Process" and all it says is "To upgrade from 5.0.x or 6.0.x to 7.1.x, download the latest ZCS 7.1.x and run the upgrade."
So in my case, nowhere did I find that 6.0.16 could not upgrade to 7.1.4.
I was using "http://files2.zimbra.com/website/docs/7.0/Zimbra%20NE%20Release%20Notes%207.1.4-2.pdf" linked as the release notes from the downloads page.
- Cheers, Peter.
It says it right there, and you quoted it: "To upgrade from 5.0.x or 6.0.x to 7.1.x, download the latest ZCS 7.1.x and run
If you are at 6.0.x, you just download the 7.1.x release you want to update to and run the upgrade.
You say you are at 6.0.14 == 6.0.x
You want to upgrade to 7.1.4 == 7.1.x
Where is the confusion?
Your initial assumption is correct, and you *should* be able to upgrade any zimbra release to any later zimbra release. There is a comprehensive procedure as part of the upgrade system that progressively rolls all the required version forward until you get to where you want to go, so if it did not work for you then you need to provide some more information for us to go on. Error messages, logs, whatever else you have to hand.
Originally Posted by pbrunnen
It *should* work. Having said that sometimes stuff happens. I initially installed 7.0.1 and the upgrade to 7.1 refused to work. I had to manually edit a text file in /opt/zimbra to get it to proceed.
Probably does not help you, but I replicate my zimbra VM (and associated data files) and attempt to perform the upgrade on the backup. If it succeeds (which it usually does) then I make the upgraded VM the prime and discard the old one.
Once bitten ...
Actually Brad, that is a good idea. I make snapshots of the OS currently but my big hang-up is that all the raw data is raw device mapped onto our san. I should look at our san's snapshot capabilities... maybe I can duplicate a snapshot off to a test system. At least test the upgrade on the duplicated dataset first and I will know what should happen in production.
Originally Posted by Brad_C
Thanks! -Cheers, Peter.
Yea... you are right. So why did the software not allow me to upgrade??
Originally Posted by Krishopper
Furthermore, I looked at v7.0.0 as I considered that seeing as maybe 6.0.x to 7.1.x was too big of a jump. Zimbra support said that you can't upgrade 6.0.16 to 7.0.0 because 6.0.16 was released after 7.0.0 was... Yet the 7.0.0 release notes say "To upgrade from 5.0.x or 6.0.x to 7.0.x, download the latest ZCS 7.0.x and run the upgrade." which is by Zimbra support team's own words - wrong.
It should read something like "To upgrade from 5.0.x or <=6.0.8 to 7.0.x, download the latest ZCS 7.0.x and run the upgrade." (or whatever is the current version of the 6.0 train that was released at the time of the 7.0.x release). This is clear and would not have lead me down the wrong path.
The thing though that has me all fired up is that the installer should check and error that this is not a possible upgrade *Before* removing the old packages and installing the new ones. The installer replaces all the packages and then connects to the database and says the equivalent of 'oops' and ends. Nevermind that my datastores were not actually upgraded. If I had not had snapshots of my VM, I would have been SOL because the install script balked immediately at attempting to install 6.0.16 again saying it can't downgrade 7.1.4 to 6.0.16... and I certainly didn't want to delete the programs manually and cause the script to handle it like a new install... that would have meant even more work.
Sorry... It was been a very testing few days.