From 926f669ebcbbad5020b0ebb6007799017f6cc64f Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawnb2yfWzJ2lYQw1UTm6XVZ4y8qashNagZA" Date: Sun, 22 Feb 2015 14:25:35 +0000 Subject: --- doc/forum/Repository_backup.mdwn | 5 +++++ 1 file changed, 5 insertions(+) create mode 100644 doc/forum/Repository_backup.mdwn diff --git a/doc/forum/Repository_backup.mdwn b/doc/forum/Repository_backup.mdwn new file mode 100644 index 000000000..39501f700 --- /dev/null +++ b/doc/forum/Repository_backup.mdwn @@ -0,0 +1,5 @@ +What's the best way of backing up the git repository itself? I feel fairly comfortable using a special remote to create an offsite backup in S3 or Glacier or whatnot, but restoring from those still requires I have a working repository somewhere that can map chunks back to files, no? + +I can probably just create a repo that has no content, tar it up, and store it on my backup medium (or on bitbucket or wherever), but that seems kinda hackish--it'd be nice to handle this within git-annex. In fact, it'd be really neat if I could handle this with any existing special remote--for example, if there were a way to commit and restore the git repo state (and symlink tree) to the remote. But that doesn't seem to exist. Is there a recommended approach for this? Am I just missing something obvious? + +Thanks. -- cgit v1.2.3