Re: [fossil-users] backing up repo to cloud service
On 02/05/16 22:17, Steve Schow wrote: > I wish to include my fossil repos in backup to cloud backup service. > > what is the best approach for doing this? if a fossil operation is in the > middle of trying to do something when the automated cloud backup daemon > decides to backup the repo file, I am presuming the backed up file could be > in an inconsistent….non-atomic state. > > Would it be preferable to do a sqlite dump or something of this nature and > back that up to cloud service? This is what I have done; not exactly what you're asking, but it can be used to accomplish the same thing. I have set up a json interface which can be used to get a list of repositories on our main development server. A script on another system will use this interface to clone any repository which hasn't been cloned already, and pull changes from all the already cloned repositories. Once this has been done all the cloned/pulled repositories are backed up. This has the added benefit that I don't need to store credentials for logging in to the backup server on the main development system. -- Kind Regards, Jan ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] backing up repo to cloud service
On 5/2/16, Steve Schow wrote: > I wish to include my fossil repos in backup to cloud backup service. > > what is the best approach for doing this? I run my own private cloud :-) I lease cheap server slices from Linode and Hurricane Electric (at geographically distributed data centers) and have clones of all my Fossil repositories on each. They automatically sync with one another using a cron job. Here at the office, we have many machines, which all serve as additional local backups by periodically running "fossil all pull". If you want to make a guaranteed-consistent backup copy of a repository fail named "x.fossil" you can run the following command: fossil sql -R x.fossil ".backup x.bu" Then, since nobody is using x.bu, it can be backed up using a generic backup mechanism without having to worry about the backup catching it in the middle of a transaction, and thus in an inconsistent state. -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] backing up repo to cloud service
On May 2, 2016, at 3:21 PM, Richard Hipp wrote: > If you want to make a guaranteed-consistent backup copy of a > repository fail named "x.fossil" you can run the following command: > >fossil sql -R x.fossil ".backup x.bu" When I try that I get -R unknown option. ?? > > I lease cheap server slices from Linode and Hurricane Electric (at > geographically distributed data centers) and have clones of all my > Fossil repositories on each. They automatically sync with one another > using a cron job. > > Here at the office, we have many machines, which all serve as > additional local backups by periodically running "fossil all pull". > If that linode service provided more diskspace or a little cheaper I would definitely consider using it for my entire backup using rsync. However for my purposes, I’m using Crashplan at $4/month for unlimited space..and I have about 2TB of other stuff to backup, so I’d just prefer to get my fossil backed up there along with everything else. I’m gonna ponder that linode service though, its interesting. I might be able to use that in some way. That would definitely be an excellent way to back up an SCM such as fossil! Truthfully, I view the cloud backup as a last ditch backup in case the house burns down, as I have everything here backed up 1-3 times within the LAN. There are 4 computers with fossil and they are going to replicate the repos for sure, though I should make sure ALL repos are being replicated for that purpose. I view that as the primary backup method. Going to the cloud is really for worst case scenario…and if I have to restore from a SQL dump in that case…that’s fine….as long as its a complete backup. ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] backing up repo to cloud service
On 5/2/16, Steve Schow wrote: > On May 2, 2016, at 3:21 PM, Richard Hipp wrote: > >> If you want to make a guaranteed-consistent backup copy of a >> repository fail named "x.fossil" you can run the following command: >> >>fossil sql -R x.fossil ".backup x.bu" > > > When I try that I get -R unknown option. ?? Really? What does "fossil version" say? -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] backing up repo to cloud service
scratch that, I didn’t read you instructions carefully enough. Not sure what the -R is…but it works if I copy and paste your line. the resulting file, is that an actual atomically sound repo file, or some other kind of file that would need to be used for an import restore of some kind? On May 2, 2016, at 6:17 PM, Richard Hipp wrote: > On 5/2/16, Steve Schow wrote: >> On May 2, 2016, at 3:21 PM, Richard Hipp wrote: >> >>> If you want to make a guaranteed-consistent backup copy of a >>> repository fail named "x.fossil" you can run the following command: >>> >>> fossil sql -R x.fossil ".backup x.bu" >> >> >> When I try that I get -R unknown option. ?? > > Really? What does "fossil version" say? > > -- > D. Richard Hipp > d...@sqlite.org > ___ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] backing up repo to cloud service
On 5/2/16, Steve Schow wrote: > scratch that, I didn’t read you instructions carefully enough. Not sure > what the -R is…but it works if I copy and paste your line. > > the resulting file, is that an actual atomically sound repo file, or some > other kind of file that would need to be used for an import restore of some > kind? It is an atomically sound repo file - a fact which can verify by doing "fossil ui x.bu" or "fossil dbstat -R x.bu" -- D. Richard Hipp d...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
