Recommend how to move 31GB of mail to a new server

[jerry at cockatoos.com]

If you run one of your rsync updates just before you shutdown, the one after
will be faster because of operating system caching. I would guess just a
couple of minutes after stopping the services with a fast connection between
the servers. So fast it will be the least of your configuration issues. 

We dumped and imported mailboxes.db while the rsync was running; and in our
case, moved the service IP between servers. We preferred moving a secondary
IP because it was faster to move it back if things weren't working as they
should, and in our case with a few silly mistakes, we did quickly revert a
few times. A firewall routing change would have been nicer.

Just be careful what you sync to avoid overwriting updated DB files or
whatever if you are updating at the same time. It took us a few tries to get
the timing right and have a working system when we started the new server
and began a reconstruct. 


-----Original Message-----
From: info-cyrus-bounces at lists.andrew.cmu.edu
[mailto:info-cyrus-bounces at lists.andrew.cmu.edu] On Behalf Of Daniel
O'Connor
Sent: Sunday, June 24, 2007 12:58 AM
To: info-cyrus at lists.andrew.cmu.edu
Subject: Re: Recommend how to move 31GB of mail to a new server

On Sunday 24 June 2007 11:04, Patrick Boutilier wrote:
> > That should save considerable time as I would imagine the vast
> > majority of email would be unchanged between the first & second
> > copy.
>
> But unfortunately rsync will still have to scan each file to
> determine what has changed, and that can chew up a lot of time.

Yes, but hopefully less time that copying the files :)
By default it will compare mtime and size and skip files which match.

-- 
Daniel O'Connor software and network engineer
for Genesis Software - http://www.gsoft.com.au
"The nice thing about standards is that there
are so many of them to choose from."
  -- Andrew Tanenbaum
GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C