[SOLVED] DB Version Mismatch after upgrade from RC1 to RC2

[PhishKiller]

Very good news! THX!!! I'll be starting the install shortly.

[jholder]

Originally Posted by PhishKiller

Very good news! THX!!! I'll be starting the install shortly.

I wouldn't.

RC2 still has some bugs. We're gonna try and kick out GA next week...

[PhishKiller]

That ship sailed. It also allowed us to install a 3rd party commercial cert that has been a thorn in our side for over a week. It's up and running.. just can't POP mailboxes. How far out is GA.. still targeted for the 17th?

[jholder]

(Pulls soap box out from under his desk)

I honestly don't know why people don't heed our warnings.

We say: It's really not a good idea to hack your installation to work on another OS. . . and they do anyway..

We say: Make sure you backup before you do anything...and some don't.

We say: PLEASE don't run Zimbra Betas in a production environment. . and they do.

We don't just say these things to be jerks, but we say them because we really do know what's best for you. And it is not in your best interest to run RC2 in a production environment. Just look at the bugzilla! Do a search for all 5.0 bugs.

Just two nights ago we discovered that some ldap entries aren't migrated. We've found issues, and we're fixing them We just don't want anyone to ever have to post a horror story about how they lost their data. It's that simple.

The fact is, this is a HUGE release for us with a lot of new featres, and we want people to test it. . but not at the cost of their data. It's just not worth the risk.

I've been there. I've wiped data doing this very same thing (before I worked at Zimbra) and almost got arrested. We do it so you don't have to. It's that simple.

Not worth the risk.
Still on target for Dec.

(Climbs down from soap box)

All the Best,

john

[PhishKiller]

As a professional software developer myself I understand.

For us, the server is pre-production. It is slated to take over 100% of our internal mail services buy the end of the month. What we are trying to do now is make sure it is capable of doing the things it needs to do, to service our needs.

If we had to dump the entire thing again, so be it. I decided to install 5.0RC2 fresh, generate a new CSR, get it authenticated and installed. It was so much easier than 4.5.9 was (we never did get that right). Burning $80 or so a cert is not our pass-time but it's cheap compared to development time.

For us, the risk is low, in having to re-install again in 2-3 weeks. I'd rather not but it won't kill us. Seeing the upcoming capabilities, improvements, etc. have indicated this is package we want to stick with.

In the mean time, I've turned off the imap proxy... maybe that will help with our POP/IMAP problem. If not. .well.. hopefully the GA release will solve that. So far everything else has been mitigated.

[jholder]

Originally Posted by PhishKiller

As a professional software developer myself I understand.

For us, the server is pre-production. It is slated to take over 100% of our internal mail services buy the end of the month. What we are trying to do now is make sure it is capable of doing the things it needs to do, to service our needs.

If we had to dump the entire thing again, so be it. I decided to install 5.0RC2 fresh, generate a new CSR, get it authenticated and installed. It was so much easier than 4.5.9 was (we never did get that right). Burning $80 or so a cert is not our pass-time but it's cheap compared to development time.

For us, the risk is low, in having to re-install again in 2-3 weeks. I'd rather not but it won't kill us. Seeing the upcoming capabilities, improvements, etc. have indicated this is package we want to stick with.

In the mean time, I've turned off the imap proxy... maybe that will help with our POP/IMAP problem. If not. .well.. hopefully the GA release will solve that. So far everything else has been mitigated.

Okay, I'll buy that. In which case, more power to ya! Test away!

Just keep in mind, if something happens, you're going to have to regenerate a CSR anyway. . and a lot of vendors have a specific window for how long you can regenerate it. . before you pay again.

[dijichi2]

Originally Posted by jholder

(Pulls soap box out from under his desk)
I honestly don't know why people don't heed our warnings.

We say: It's really not a good idea to hack your installation to work on another OS. . . and they do anyway..

We say: Make sure you backup before you do anything...and some don't.

We say: PLEASE don't run Zimbra Betas in a production environment. . and they do.

For the Network Edition running production email, of course I agree 200% - the things I read people doing on this forum sometimes gives me the heebie jeebies.

If this relates to the Opensource edition, well what do you expect? Of course people are going to hack it to work on other OSs - for various reasons sometimes this is necessary. The various hacks I've posted in the past to get zimbra running on nonstandard OSs have been because I've had to run it on those OSs usually due to hosting choice. A lot of small companies rent servers to run services like Zimbra - it's a very cheap and reliable way of doing it.

With regards to not running Betas, how do you expect to catch bugs and produce stable versions without people running the code? Lots of the opensource versions are run on production but not earth-shatteringly-vital installs such as mine, where I can live with the odd bug every now and then and do so in order to test funky new features and to try and contribute bug fixes back to zimbra. This way the opensource versions contribute towards the stability of the paying network editions.

Aren't these some of the main reasons you allow limited access to your source code in the first place?

[jholder]

In this situation, I draw the distinction not with Open Source vs. Network, but with Production vs. Development environments.

Just because we don't get paid for Open Source users isn't a good enough reason for me to believe that their systems are any less important.

Agreed. We do want bug testers, and we do want hackers. . . but never at the expense of their production system.

I once was told by a user that we should test more before putting out a Beta. The fact is, that you and others are the best asset we have. That's how we test. We just never hope that anyone will ever do it at the risk of their data.