On Mon, 17 Oct, 2005 at 19:04:21 +0200, Sandy Drobic wrote:
Jon Clausen wrote:
I still would like for cyradm to be able to pull contents from another server, but either I'm missing something or else it's just not been implemented yet.
Unfortunately this is something most server applications tend to neglect: How to backup/restore your configuration/data.
Right. But since (current) cyradm has a 'transfer mailbox' function, at least it seems that it is being worked on. In my situation it does little good since it only supports transferring mailboxes *to* a different server. And the older version that's on the old server doesn't...
Circumstances dictated that I offlined the old server and onlined the new simultaneously. Also I needed immediate access to some of the folders, which I copied over using Mutt.
I am afraid that was a big mistake. I prefer to test and check the migration with a test system and a small database, then use the real data to check, if there is a hidden bug and see how much time is needed. I then double the time to have space for the inevitable bugs that occur in the real migration. Then I set an offline window and tell the users to store mails needed in the mean-time in off-line folders. That way they don't bug me when I need my concentration and nerves for the actual migration.
Right. I guess I should have pointed out earlier, that I am in fact the only user on either of the servers.
First rule is always: Don't let yourself be talked into things that you simply can not guarantee. Rather find ways around to solve the immediate problem and then proceed according to plan.
I was the one who talked myself into doing it like that. The hows and whys are immaterial at this point. Let's just say; the pressure was entirely from myself. Originally I didn't intend to do any 'behind the scenes' backup/restore for the transition. Which is why I never spent much time looking into the mechanics of that. My original plan was to copy the contents using IMAP, and if all else fails that is still a viable solution. Even if it means I have to depart from the 'vanila' state of the new server.
As a consequence I now have a number of folders which are severely out of sync (between "old" and "new"). Question;
At this point I should clarify about the folder structure; INBOX; Toplevel, 'synced' manually INBOX.1st-sub; Mailinglists, workrelated etc. some in sync some not INBOX.2nd-sub; Timeslice archives of above (quarterly, monthly etc) What I'm looking at restoring, at this point, is mostly just the 2nd sublevel. So I think that the basic approach outlined previously would still apply, with modifications to only work on the 2nd level?
One hare-brained way to get them back might be to export the mailbox.db on the old system and the new system, merge these files and then use unique to delete double entries. This might work, but I have never tried something that reckless. (^-^)
I like that :) If I were somewhat more comfortable with how Cyrus works, I might even try it...
PS: if you use sieve-scripts, please don't forget to copy those as well.
At least on that front there is no problem. I use Procmail for filtering. Which, incidentally, was my motivation to set up the 1st sublevel structure; So that the procmailrc's could be 'just cut/pasted' and start work immediately... which they did :) /Jon -- YMMV