similar to: dsync and altpath on shared storage.

On 9/2/19 3:03 PM, Sami Ketola wrote: >> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote: ... >> Is there anyway for dsync to avoid moving Gigabytes of data for could >> just be "moved" by moving the mount? > > > Not tested but you can probably do something like this in the target server: > > doveadm backup -u

> On 3 Sep 2019, at 15.34, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote: > > > > On 9/2/19 3:03 PM, Sami Ketola wrote: >>> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote: > ... >>> Is there anyway for dsync to avoid moving Gigabytes of data for could >>> just be "moved" by moving

> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote: > > Hi, > > I was wondering... > > If one had mdbox ALT path set to a shared storage mount (say, on NFS) > and one wanted to move a mailbox to a different host... I guess it in > principle wouldn't be necessary to copy all the ALT storage through > dsync, when the volume

So... I've done some testing. One method which seemed to work - at least for primitive cases - was to: * Mount the ALT storage on the destination. * Run "doveadm force-resync \*" on the destination. (putting all the mails in ALT storage into the dovecot.map.index) * Run dsync from source to destination. Of course... if there was some way to avoid step 2... /Peter

Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser dsync(standl2): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(standl2):

I was thinking about documentation for alternate storage. We have a few mentions at: http://wiki2.dovecot.org/MailboxFormat/dbox http://wiki2.dovecot.org/Tools/Doveadm http://wiki2.dovecot.org/Tools/Doveadm/Altmove But I was thinking it would be helpful if there could be a page about alternate storage. I could write the page, but I currently have so many unknowns that I think it would be

Hi! I'm currently running an small imap-server on Dovecot 2.2.4 but will retire that server. I've set up an new server with Dovecot 2.3.4 and will migrate the mailboxes (maildir-format) from the old to the new server. I'm planning to restructure the accounts a bit when migrating so I need to move them one by one. Its only a few so thats not a big issue. Both servers are using

Am 30.12.18 um 10:53 schrieb Sami Ketola: > >> On 29 Dec 2018, at 23.49, Hans Brage <hans at plattformen.se> wrote: >> >> Hi! >> >> I'm currently running an small imap-server on Dovecot 2.2.4 but will retire that server. I've set up an new server with Dovecot 2.3.4 and will migrate the mailboxes (maildir-format) from the old to the new server.

I'm moving/converting email from one system to another The source system is: Dual core x86_64 6GB memory 180 GB raid1 disks ext4 Fedora 9 Dovecot 1.0.15 Maildir format The destination system is: Dual core x86_64 2GB memory 1TB raid1 disks ext4 Fedora 18 Dovecot 2.1.15 sdbox format I am moving mail in a series of steps: 0) cd ( to mail user home directory ) mkdir Maildir 1) # rsync mail

Hi there, We're trying to convert users from Maildir to sdbox at present; I'm using dsync to achieve this (2.0.16) however when the user's have been converted we only get minimal information in the caching files. Is there some way to preserve all the caching decisions that were previously made so that when the user logs in to the new mailbox we don't have to cause an io storm

I have an idea for running a pair of redundant dovecot mail servers that may be odd but it might work. I'm interested in any thoughts on the topic. Would it work to run 'dsync mirror' every minute against either mdbox or sdbox mailbox on a dedicated network connection between two (or potentially three or four) mail servers? I'm trying to avoid using a NAS/SAN or some other

Hi all, We are currently using snapshots and rsync to backup a large mail server to a backup mail server. I have been looking into using dsync to replace rsync in hopes that it would make backups more efficient. I decided to test the performance using a single mailbox. Unfortunately dsync seems to run much slower than rsync. Rsync was able to sync the mailbox in 2 seconds. dsync took over

Hi, We have dsync failing once in a while when running in "backup" mode. What's strange is that the result is that the file permissions on the *source* machine ends up with the wrong permissions (set to uid 0). Even though the dsync manual clearly says: "Backup mails from default mail location to location2 (or vice versa, if -R parameter is given). No changes are ever done

Hi Guys, I have a quite interesting problem. I have two servers that replicate to each-other. Suddenly one of the accounts is starting to eat a very large amount of disk space on, what basically is the replica for this account. doveadm-server seems to hang and keeps on filling the disk. I came across this message in the logs: Dec 8 07:36:40 <server> dovecot:

Hi, It seems we are still able to reproduce this: http://www.dovecot.org/list/dovecot/2014-May/096367.html However... there's no longer any error-messages. It just silently changes permissions on some dovecot files in the source maildir. (most often dovecot-uidlist) We're running dsync as root, with hardwired userdb values for other reasons. So it has the OS permissions to change

Thanks! That was a really useful answer. // Hans Den 2018-12-30 kl. 10:53, skrev Sami Ketola: >> On 29 Dec 2018, at 23.49, Hans Brage <hans at plattformen.se> wrote: >> >> Hi! >> >> I'm currently running an small imap-server on Dovecot 2.2.4 but will retire that server. I've set up an new server with Dovecot 2.3.4 and will migrate the mailboxes

Hi there, I ran into an issue yesterday (dovecot 2.0) whereby when we dsync messages from a local machine (sdbox) to a remote (Maildir) which have different pop3_uidl_formats configured, the uidl format is not preserved. There doesn't seem to be any way to force this in the code, although I suspect that Maildir sources with saved pop3 uidls would pass them correctly. Attached is a rough patch

Gents, I'm relocating mailboxes to a new server. Before switching over to a new server I ran syncing a few times without any issues first I sync files with rsync from the old server to have a local copy, then I sync mailboxes with dsync /usr/bin/doveadm -Dv sync -u $MBOX -R "sdbox:/srv/vmail/temp/srv/srv.bgoperator.ru/${MBOX}:DIRNAME=DbOx-mAiLs" After switching over smtp

I'm using dsync to synchronize emails on a laptop where wifi connectivity sometimes fails in the middle of a sync. I have a shell script that runs dsync, and here is one line of it including the output of dsync: + dsync -f -m realmail mirror /home/paulproteus/projects/ssh-attach/run ssh rose.makesad.us dsync dsync-local(paulproteus): Error: dbox

On Fri Feb 23 2018 13:53:27 GMT-0500 (Eastern Standard Time), Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > Once you cache grows bigger than 0x4000000 you have problems This is for a single mailbox? IS this only a problem for mbox and maybe sdbox?