<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body smarttemplateinserted="true">
<div id="smartTemplate4-quoteHeader">
<div style="font-size:10.0pt;font-family:Verdana,Arial">Jason,<br>
<br>
What you mention is highly related to the replication backup we
were talking about in the previous mails. The idea is the same,
they replicate from master. Then, in a pure replica solution,
the replica is stopped, a copy of its files (in the native
format) is made and it's started again to continue replication.<br>
<br>
The Cyrus Backups also replicates all data from master, but
stores it in a different format and has some additional
functionality to assist in backing up the files, but AFAIK it's
not yet complete, e.g. I'm not sure it's possible to make
incremental backups with it, not sure about the SEEN state, the
recovery process appears not trivial, etc.<br>
<br>
In both cases, a copy of the master data is made, which requires
twice the space of real usage (Cyrus Backups tries to apply
compression on stored data, not sure how well it works).<br>
<br>
What is really needed, IMO, for SME environments is the ability
for Cyrus to sync to disk all data, so one can take a hot copy
of that data with standard UNIX tools and then handle it
accordingly. Once a recovery is needed, one just copies a backup
to the Cyrus dir and starts the service. The data would be in
the exact same state as when the backup took place. This is
discussed in the github issue mentioned in the previous mail.<br>
<br>
</div>
<div style="border:none;border-top:solid #B5C4DF
1.0pt;padding:3.0pt 0cm 0cm
0cm;font-size:10.0pt;font-family:"Tahoma","sans-serif""><b>From:</b>
Jason L Tibbitts Iii<br>
<b>Sent:</b> Thursday, May 10, 2018 14:10<br>
<b>To:</b> Arnaldo Viegas De Lima<br>
<b>Cc:</b> Info-cyrus<br>
<b>Subject:</b> Re: Backup methods<br>
</div>
<br>
</div>
<span type="cite"
cite="mid:38953_1525972205_w4AHA3W8025844_ufavabvl9na.fsf@epithumnia.math.uh.edu"
style="display: block; word-break: break-all; margin: 7px 0 0 0;
padding: 0; line-height:0"></span>
<pre wrap="">Cyrus does have an integrated backup system (see
<a class="moz-txt-link-freetext" href="https://cyrusimap.org/imap/reference/admin/backups.html">https://cyrusimap.org/imap/reference/admin/backups.html</a>) which I'm not
sure has been mentioned in this thread. But you still have to have
enough space to keep the compressed backups on disk in order to move
them to tape or whatever archival storage you're using. There is
discussion of the storage requirements in the documentation. I don't
think any of it is particularly unreasonable, but I haven't actually
tried it myself.
Technically I don't think you need a separate machine (though that's
simpler); it may just be possible to have a second cyrus server
listening on different ports to act as the replication target. I
probably wouldn't do it that way anyway; old hardware with some cheap
disk would suffice to stage the backups until they're sent to tape or
wherever.
As for it all being marked "experimental", I'm sure that if bugs were
found (and reported), they would be fixed. It probably just needs more
testing and back and forth with the devs to flesh out the documentation
and add any missing functionality.
- J<
----
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>
<br>
</body>
</html>