OCaml C PHP
Fetching latest commit…
Cannot retrieve the latest commit at this time.
|Failed to load latest commit information.|
Copyright (C) 2008 Mauricio Fernandez <email@example.com> (C) 2007 Jean-Francois Richard <firstname.lastname@example.org> gibak -- backup tool based on Git ================================= Since gibak builds upon the infrastructure offered by Git, it shares its main strengths: * speed: recovering your data is faster that cp -a... * full revision history * space-efficient data store, with file compression and textual/binary deltas * efficient transport protocol to replicate the backup (faster than rsync) gibak uses Git's hook system to save and restore the information Git doesn't track itself such as permissions, empty directories and optionally mtime fields. Dependencies ============ gibak needs the following software at run-time: * git (tested with git version 184.108.40.206, might work with earlier versions) * rsync >= 2.6.4 (released on 30 March 2005), used to manage nested git repositories (submodules) * common un*x userland: bash, basename, pwd, hostname, cut, grep, egrep, date... Installation ============ You'll need OCaml and omake to compile gibak (it has been tested with OCaml 3.10.1). (1) Verify the compilation parameters in OMakefile. The defaults should work in most cases, but you might need to change a couple variables: * include paths for the caml headers, required in some OCaml setups * support for extended attributes. Tested on Linux and OSX. (2) run $ omake (3) copy the following executables to a directory in your path: find-git-files find-git-repos gibak ometastore Usage ===== Run gibak without any options to get a help message. The normal workflow is: $ gibak init # run once to initialize the backup system $ vim .gitignore # edit to make sure you don't import unwanted files # edit .gitignore files in other subdirectories # you can get a list of the files which will be saved # with find-git-files or gibak ls-new-files $ gibak commit # the first commit will be fairly slow, but the following # ones will be very fast .... later .... $ gibak commit The backup will be placed in $HOME/.git. "Nested Git repositories" will be rsync'ed to $HOME/.git/git-repositories and they will be registered as submodules in the main Git repository (run git help submodule for more information on submodules). You might want to use a cronjob to save snapshots of the repositories in $HOME/.git/git-repositories After you gibak init, $HOME becomes a git repository, so you can use normal git commands. If you use "gibak commit", however, new files will automatically be added to the repository if they are not ignored (as indicated in your .gitignore files), so you'll normally prefer it to "git commit". About the backup store ---------------------- The backup data is placed in $HOME/.git. You can mount an external disk there if you want your backup to reside in a different physical disk for resiliency against disk crashes. You can also clone the repository (probably using a bare repository --- without working tree --- for smaller space usage) and rsync .git/git-repositories to remote machines for further protection. License ======= The gibak script is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version. The ometastore, find-git-files and find-git-repos programs are distributed under the terms of the GNU Library General Public License version 2.1 (found in LICENSE). All .ml source files are referred as "the Library" hereunder. As a special exception to the GNU Lesser General Public License, you may link, statically or dynamically, a "work that uses the Library" with a publicly distributed version of the Library to produce an executable file containing portions of the Library, and distribute that executable file under terms of your choice, without any of the additional requirements listed in clause 6 of the GNU Lesser General Public License. By "a publicly distributed version of the Library", we mean either the unmodified Library as distributed by the author, or a modified version of the Library that is distributed under the conditions defined in clause 2 of the GNU Lesser General Public License. This exception does not however invalidate any other reasons why the executable file might be covered by the GNU Lesser General Public License.