diff options
| author |  http://xgm.de/oid/ <Horus@web> | 2017-11-30 12:32:53 +0000 |
|---|---|---|
| committer |  admin <admin@branchable.com> | 2017-11-30 12:32:53 +0000 |
| commit | 33f22fdd9775a92e0155b9b299d23c5aca68608e (patch) | |
| tree | 21269f4cde37257a1621b4fd4f2b3fa9448b947a | |
| parent | da23d651e086ef358ea8023f5342ece6a7b25114 (diff) | |
| -rw-r--r-- | doc/forum/How_to_organise_backup_to_S3__63__.mdwn | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/forum/How_to_organise_backup_to_S3__63__.mdwn b/doc/forum/How_to_organise_backup_to_S3__63__.mdwn new file mode 100644 index 000000000..25ead06aa --- /dev/null +++ b/doc/forum/How_to_organise_backup_to_S3__63__.mdwn @@ -0,0 +1,10 @@ +Hello, + +what is the best way to use git-annex as a backup tool to S3? As far as I know, even if all data is copied to S3, I need a checkout of the git repo, correct? And of course the private key used. + +- Is there a way to also save the repository data to S3? To have something like ```git annex restore-from-external-remote ...``` + +- If not, how do you organise the backup so that it is disaster proof? Upload the repo to some other external server regularly? + +Thanks, +Florian |