On Fri, Sep 5, 2014 at 10:55 AM, Gour <g...@atmarama.net> wrote: > On Fri, 5 Sep 2014 10:48:11 -0400 > Ron W <ronw.m...@gmail.com> wrote: > > The intermediate to advanced git users I've talked with seem to take > > the position that "version control is not a backup" means that > > "history is in the back ups". > > I just wonder how 'long' is the usual "backup history"...
Depends on who is maintaining the backups. The IT department where I work only keeps backups for 3 months. Those backups do include the VCS repositories and the company's Document Management System database. Also included are files on the file servers, so any files we copy to the servers are also backed up. Files that don't change are only on the monthly full backups. The big caveats are: (1) Only the servers are backed up. (2) If a file gets corrupted or deleted, the backups of it will be gone in as little as 59 calendar days, which can be as little as 40 business days. Since the VCS and DMS are used daily, we will find out quickly if there's a problem. Other files may go unnoticed for years. So far, we've had only "last hour" loss from corruption, and very few losses from accidental (or misguided intentional) deletion., thanks to the diligence of our IT team, as well as a lot of good luck. For my personal use, I have 2 growing stacks of hard drives. As I fill the current pair, I store them in 2 different heat and water resistant document boxes in opposite corners of my basement. From there they go to similar boxes in different relatives' house. Very important files are stored on DVDs which I remake at least once per year and store those in my safe deposit box at the bank. Far from perfect, but better than most people I know.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
