On 9/5/2014 13:36, Matt Welland wrote:
On Fri, Sep 5, 2014 at 12:10 PM, Ron W <ronw.m...@gmail.com
<mailto:ronw.m...@gmail.com>> wrote:
Still need to keep the Fossil repo backed up.
Is there really a need for a backup if you have offsite fossils to which
you regularly sync?
Probably not.
I do it anyway because I'm pretty irregular in how often I sync each
offsite clone to the master. It makes me feel better to have a cron job
to backstop me.
This also allows me to do a few things differently than a simple fossil
clone sync:
1. "sqlite3 $repo .dump | xz > $repo.sql.xz" gives a somewhat smaller
file than the binary repo, and it is theoretically readable if you have
to do some deep disaster recovery.
2. You can follow that with a GPG pass to encrypt it for semi-secure
offsite storage, such as Dropbox or Google Drive. Running whole-archive
XZ-compressed data through GPG gives an attacker less of a foothold than
the individually-compressed blobs in the binary Fossil repo.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
