Oswald Buddenhagen <oswald.buddenha...@gmx.de> writes: > On Tue, May 12, 2015 at 03:51:06PM -0400, Eric Abrahamsen wrote: >> I have migrated (yet again) to another computer, and since I had >> pretty good luck last time I did this, I just rsync'd the message >> directories and ~/.mbsync over onto the new machine directly. >> > you can do that, as long as you can be sure that no mbsync is running > over either store while you are rsyncing. otherwise it's a recipe for > disaster (by which i mean mail loss on the server).
Yup, I didn't touch anything while the sync was going on. >> This has basically worked, except for two groups on one account which >> are giving me "UIDVALIDITY of master changed". I notice that the state >> directory contains extra .journal and .new files for these two groups. >> The .new files are empty, the .journal files are large. >> > that means that syncing did not complete. > first make sure that the store you copied *from* is still ok and has no > stale journals. > then make sure no mbsyncs are running. > then rsync again with --delete. > then you can fire up the mbsyncs. That did it, thanks a lot! Eric ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ isync-devel mailing list isync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/isync-devel
