<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 08/30/2014 02:37 PM, Patrick Goetz wrote:<br>
<blockquote cite="mid:540227E0.7080500@mail.utexas.edu" type="cite">
<pre wrap="">On 8/30/2014 10:10 AM, Simon Matter wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
I suggest -aH to preserve single instance storage in the backup.
</pre>
</blockquote>
<pre wrap="">
Does cyrus use a lot of hard links? I use rsync a lot to create
snapshot backups, and use hard links across snapshots to preserve space;
however, for a single instance backup and unless the filesystem includes
hard links (not normal), then the -H won't do much for you.</pre>
</blockquote>
<br>
Cyrus uses hard links among copies of the same message in different
mailboxes, when "singleinstancestore: 1" is set, which is the
default. From the man page imapd.conf(5):<br>
<blockquote>If enabled, imapd, lmtpd and nntpd attempt to only write
one copy of a message per partition and create hard links,
resulting in a potentially large disk savings. <br>
</blockquote>
<br>
<blockquote cite="mid:540227E0.7080500@mail.utexas.edu" type="cite">
<pre wrap="">Of course one should always use -a.
The biggest concern I have about backing up mail spools is keeping the
index and message stores in sync while the backup is taking place. A
long time ago someone suggested using cyrdump, but when I looked into
this, I couldn't find any documentation whatsoever. Is cyrdump a real
thing, or did I imagine all this?</pre>
</blockquote>
<br>
Are you thinking of ctl_mboxlist? It allows one to dump the
mailboxes database to a flat file. In an out-of-the-box Cyrus
installation the indexes are stored with the messages in the mailbox
hierarchy. If you decide to store meta-data separately, you should
simply snapshot that at the same time you snapshot your mailstore.
At the beginning of this thread, Marcus Schopen wrote this example:<br>
<blockquote>
<pre wrap=""> ctl_cyrusdb -c
ctl_mboxlist -d > mailboxes.db.dump
stop cyrus
lvm snaps
start cyrus
rsync <i class="moz-txt-slash"><span class="moz-txt-tag">/</span>var/lib/cyrus<span class="moz-txt-tag">/</span></i> and /var/spool/cyrus to backup host
remove snaps
</pre>
</blockquote>
One could simply include any meta-data volumes in the snapshotting
process.<br>
<br>
Cheers,<br>
-nic<br>
<blockquote cite="mid:540227E0.7080500@mail.utexas.edu" type="cite">
<pre wrap="">
----
Cyrus Home Page: <a class="moz-txt-link-freetext" href="http://www.cyrusimap.org/">http://www.cyrusimap.org/</a>
List Archives/Info: <a class="moz-txt-link-freetext" href="http://lists.andrew.cmu.edu/pipermail/info-cyrus/">http://lists.andrew.cmu.edu/pipermail/info-cyrus/</a>
To Unsubscribe:
<a class="moz-txt-link-freetext" href="https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus">https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Nic Bernstein <a class="moz-txt-link-abbreviated" href="mailto:nic@onlight.com">nic@onlight.com</a>
Onlight llc. <a class="moz-txt-link-abbreviated" href="http://www.onlight.com">www.onlight.com</a>
219 N. Milwaukee St., Ste. 2A v. 414.272.4477
Milwaukee, Wisconsin 53202 f. 414.290.0335
</pre>
</body>
</html>