I do not know if this has been suggested but when an upgrade fails it should restore every thing back to working order. I have not had an upgrade go smooth yet. Maybe an option to ask you if you want to make a backup.
I do not know if this has been suggested but when an upgrade fails it should restore every thing back to working order. I have not had an upgrade go smooth yet. Maybe an option to ask you if you want to make a backup.
What's wrong? I haven't seen a post by you. Are you having trouble? If so, what?
-john
I do backup before I update. I just wish it was automated I think that it would be a nice feature for those that have problems. Not to mention those that don't back up first. Most problems I find a solution to on the forums and do not need to post. Most problems I run into are make a quick change and retry. I did have a problem with this upgrade and I plan on tracking that down after I get things settled from other changes I made this weekend. I really appreciate the response I get from the zimbra people.
Thanks
I agree that it would be much more robust for us to roll back changes after a failed upgrade, but I doubt this will ever happen. Many customers, particularly the ones with a large number of users, are more interested in a fast upgrade than a robust one. The smarter we are about recovery, the slower the upgrade will be.
One alternative that I can think of for smaller sites is that we could offer the user the option to shut down all services and then blindly copy /opt/zimbra or some portion of it to another location before starting the upgrade. If you think this would be a useful addition, feel free to file a bug.
Boris
This is the error that i received when upgrading this time. Any suggestions? Or should I start a separate thread?
ERROR 1051 (42S02) at line 8148: Unknown table 'tombstone,open_conversation,appointment,mail_item '
mysql invocation failed, exit code = 1: at /opt/zimbra/libexec/scripts/migrate20060911-MailboxGroup.pl line 84,
I don't really know. The error message is similar. Mine did a bunch of table updates (at least I think that is what it was doing) before getting the error. I will attach the zmsetup.log. I hope that is not the problem I really do not want to do a fresh install.
Thanks
Responded to via pvt message.
There are currently 1 users browsing this thread. (0 members and 1 guests)