From: "Victor" <[EMAIL PROTECTED]> Date: Fri, 11 Jan 2002 17:25:02 -0500 [...] > Then, we schedule downtime, upgrade the binaries on the production server, > and reboot (if needed). This is, of course, provided that the data files > haven't changed format between the two versions ;)
This is exactly the issue I was concerned about :) I suppose there would be tools then to convert. However if the set of mail is huge (or distributed over servers), it can be a real hassle to convert everything. Well, this is why most of the recent change-in-format has been done automatically by the server as it encounters out-of-date data. Unfortunately, this opens up the "can't downgrade" problem, which we don't have a good solution for. [...] If you don't mind, I also wanted to ask you about your setup. It is not recommended that Cyrus run over NFS. So I assume you have it running on one server (or many server using the special function to break message storage onto many servers). Do you just hold backups and if a server fails, restore? We currently have a single server. The configuration is on the web at http://asg.web.cmu.edu/cyrus/config.html. We have backups. We've never had to restore an entire partition, but the backups have been used to recover from various filesystem problems, administrator error, and (more frequently) user error. Or do you hot like a hot standby box? I am curious what steps can be taken to make cyrus be High Availability. We don't have a hot standby box, though we have many Sun boxes that could be similiarly configured on short notice (we use them as development machines, etc.). Our hope is to use the aggregator in production (and document it) in the next few months. Larry
