backups

[Marius Kruger]

2009/4/8 Maritza Mendez <martitzam at gmail.com>:
> Before I can deploy a pilot project, I need an automated backup strategy for
> a shared repo hosting about 100GB of code and data.  I've found quite a bit
> of discussion and ideas on the bzr site and in irc logs.  But I have found
> few solutions.
>
> Our priorities are as follows:
>
> 1. integrity of the backup
> 2. integrity of the backup
> 3. integrity of the backup
>

Maybe you can use the bzr-repo-push[1] plugin to push all your
branches to a backup site.
You can then zip up the backup repo after the repo-push if you would
like snapshots.
Because you schedule the repo-pushes, you can know when the backup
repo will be quiet.

Another option is to bind all your branches in your main repo
to your backup repo, then it will get mirrored immediately when
a new commit comes in. But then you run the risk of forgetting
to bind a branch, and then the backup repo has to be up all the time and
your backup repo does not have quiet periods. So would probably not suit you.

[1] https://launchpad.net/bzr-repo-push

-- 
<| regards
U| Marius
H| <><