Hello.
In the upcoming weeks I may need to move a Cyrus installation from the
server where it's been living for the latest years and I'm open to some
suggetions.
Normally I'd just move its jail (it's on FreeBSD) via ZFS send/receive,
doing it incrementally in order to reduce the downtime to a few seconds.
In this case, however I'm wondering if the "replica" alternative would
be better.
In fact:
a) I'm running version 3.6.7 and I'd like to move to 3.12.
I've always done the upgrades in place, but in this case I'd need to
step through 3.10.
Is the statement "Before upgrading to 3.12, your deployment should be
running 3.10.1 (or later)" also valid if done through replica?
If this was not the case I could just do everything in one step (replica
from 3.6 to 3.12), instead of three (upgrade 3.6->3.10, 3.10->3.12, copy
everything).
b) I'm also not very fond of UUID named mailboxes.
If I set "mailbox_legacy_dirs: on" on the new server will the mailbox
replicate using the "traditional" directory names?
In case I go the replica way, I find documentation to be somewhat scarce.
Do I get it right that I should:
_ configure everything;
_ (log based replication, either rolling or periodic, starts, but only
for new data);
_ run sync_client to do a full replication;
_ let log based replication catch up;
_ stop the old server;
_ promote the replica to master (just remove the replica config);
_ start using the new server;
?
At this point I should start doing backups of the new server and I see
two ways:
a) set it up to be included in the backup system the normal way;
b) change the replica direction from new to old (should I first delete
everything) and keep backing up the old server.
The second option would proably reduce network (WAN) usage. Any cons?
Thanks in advance.
bye
av.
P.S.
IIUC replica is master/slave only.
I.e.
Server A cannot be slave for B and at the same time server B be slave
for A (so as to be able to let clients use both servers indifferently
and have everything kept coherent on both).
Right?
------------------------------------------
Cyrus: Info
Permalink:
https://cyrus.topicbox.com/groups/info/T20718c9f2ef9b310-Mb182557e2590b802ca373aa7
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
