Did you install cyrus on the new server before or after the steps
described below? It sounds as if it was before, just by the references
to shutting it down on the new server and
to /usr/lib/cyrus/cyrus-db-types.active.
Also, do you have any sense of the speed and accuracy of this method as
On Mon, Sep 7, 2009 at 3:34 PM, Ross Boylanr...@biostat.ucsf.edu wrote:
Did you install cyrus on the new server before or after the steps
described below? It sounds as if it was before, just by the references
to shutting it down on the new server and
to /usr/lib/cyrus/cyrus-db-types.active.
Hi,
I've seen some questions about migrating from 32 bit to 64 bit. We
migrated last weekend and these are the steps we took.
Old server:
- rsync the cyrus data while cyrus is running
rsync -vaH --delete -e ssh /var/lib/cyrus/ new-server:/var/lib/cyrus
rsync -vaH --delete -e
Hi,
I've seen some questions about migrating from 32 bit to 64 bit. We
Hi,
I understand that you also migrated to a newer OS and cyrus-imapd version,
right?
migrated last weekend and these are the steps we took.
Old server:
- rsync the cyrus data while cyrus is running
rsync
Simon Matter wrote:
I'm wondering how much of all this was really needed for the migration
from 32bit to 64bit? Are the BerkeleyDB ondisk files different on
32/64bit?
Yes they are. It's not the OS that matters but the architecture of the
libdb4.so file.
It is still a good idea not to use
I'm wondering how much of all this was really needed for the migration
from 32bit to 64bit? Are the BerkeleyDB ondisk files different on
32/64bit?
I initially tried just using rsync with cyrus shutdown on both servers
but cyrus failed to start on the new server due to db errors. As
mentioned
On Wed, Sep 02, 2009 at 10:46:35AM -0600, Bill Cameron wrote:
I'm wondering how much of all this was really needed for the migration
from 32bit to 64bit? Are the BerkeleyDB ondisk files different on
32/64bit?
I initially tried just using rsync with cyrus shutdown on both servers
but
