Cyrus upgrade from 2.1.18 to 2.2.13 moved email messages

Steinar Bang sb at
Thu Nov 29 06:03:26 EST 2007

>>>>> "Alain Spineux" <aspineux at>:

> You would have won some time if you had read one of my previous post
> in another thread about pitfall you can meet when migrating. The
> thread title is "Migration 32 to 64 bit".  It could still help you to
> understand what you did :-)

Thanx, I'll study it.  I assume it's this one...?

(this is my home "server" (a Pentium II 233MHz, that have been running
more or less continously since 1999), so I don't have any test systems
to migrate to.  But I _do_ have an rsync copy of the spool, on a
separate HD.  So I would eventually have been able to recover most of
the messages, I think)

> Be aware that we are not all debian user, and dont know the script and
> tips provided by debian to help in migration. Anyway specify the
> source of your information and actions is a gooud practice.

I've tried to follow the instructions for the upgrade from 2.1 to to 2.2
in /usr/share/doc/cyrus-common-2.2/UPGRADE.Debian.gz (installed by the
cyrus-common-2.2 package of debian etch), which refers to the database
upgrade steps of the "Upgrading from cyrus 1.5.x in the same document.

The final step in the 1.5.x upgrade section, refers to the
/usr/share/doc/cyrus-common-2.2/README.Debian.database.gz (installed by
the same package) for database upgrades.

This document describes the conversion of the /var/lib/cyrus and the
SUBS and SEEN databases from bdb to skiplist, and the /var/lib/cyrus
databases was when things messed up for me, and I started posting
messages to the list.

(Side note: I already was on skiplists for the SEEN databases in 2.1.x.
I can't quite remember, but I think it was after losing the BDB SEEN
databases for the second or third time.  I have had no problems since
then, but the deliver.db (still in BDB) has gone corrupt on me a couple
of times)

And Alain: thanx again! You have been very helpful in this!

- Steinar

More information about the Info-cyrus mailing list