XFER when changing database formats
wes at umich.edu
Wed Oct 28 21:13:08 EDT 2009
On 28 Oct 2009, at 09:43, David Mayo wrote:
> I am now looking at transferring our users to the new back-end server.
> The XFER command seems to do the job perfectly, except for the seen
> subscription databases because we are changing formats from flat to
> Looking at the telemetry, it appears the XFER command just dumps
> everything raw and the other end slurps it in without
> interpretation. We
> get lots of errors in the logs and unfortunately the sync client
> doesn't take too kindly to this either, and bails out!
> Our users won't accept losing their seen state. I can convert the seen
> state before/after the XFER with a bit of work, however does anyone
> of a cleaner solution that saves me having to run two different
I'm not aware of an off-the-shelf solution. It might be possible for
undump_mailbox() to examine the xfer'd data and convert it before
instantiating it. flat doesn't have a magic number, but skiplist
does. Presumably BDB does too, tho Cyrus doesn't know about it
directly. A general solution would probably be hard and/or ugly.
If it were me, I'd probably keep the file formats the same until XFER
is complete and convert after the fact.
More information about the Info-cyrus