LMTP during dsync migration

[Reindl Harald]

Am 30.07.2014 16:39, schrieb Jogi Hofmüller:
> Am 2014-07-30 12:02, schrieb Jiri Bourek:
>> Or better - disable LMTP service in Dovecot. Incoming mail will stay on
>> your MTA and when you're done, you just tell it to deliver everything
>> that piled up in the queue in the meantime
> 
> Better but still not perfect ;)  We have users that work late and I am
> sure they would complain when they don't receive email during migration
> nights

normally you announce a mainantaince window for such migrations

why do you need dsync at all for such a migration?

* HOT: rsync --delete-after -tPrlpogEAX /datadir/ root at new:/datadir/
* stop services
* COLD: rsync --delete-after -tPrlpogEAX /datadir/ root at new:/datadir/
* start services on new machine

the second rsync is damned fast because it only cares about
changes and in case of really large data repeat the hot run
multiple times to reduce the overall differences

nobody right in his mind starts such tasks while the servers
are online because if something goes wrong you can throw
your mandatory backups out of the window given you can
choose what data you more like to loose - the one happened
by errors while migration or the one received between backup
and restore

> Still thinking ...

you asked "The question is what to do with LMTP _while_ the doveadm
backup migration is happening?" and there is not much to think

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://dovecot.org/pipermail/dovecot/attachments/20140730/fa7a797b/attachment.sig>