summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar https://me.yahoo.com/a/chZVFogbu55hxJc3FfeXs.RfaA--#cc6f9 <George@web>2015-04-29 21:26:51 +0000
committerGravatar admin <admin@branchable.com>2015-04-29 21:26:51 +0000
commitf4bb96f056456d7750cee9aeccba8b095cc4a4b1 (patch)
tree0818ed9fb9d617635d929840489970fccbbfc8af
parent6429d1b5cdcbbc6edf756159eaaa3c5207b5b270 (diff)
-rw-r--r--doc/forum/How_do_I_backup_my_data_to_blue_ray_disks__63__.mdwn1
1 files changed, 1 insertions, 0 deletions
diff --git a/doc/forum/How_do_I_backup_my_data_to_blue_ray_disks__63__.mdwn b/doc/forum/How_do_I_backup_my_data_to_blue_ray_disks__63__.mdwn
new file mode 100644
index 000000000..b94111e94
--- /dev/null
+++ b/doc/forum/How_do_I_backup_my_data_to_blue_ray_disks__63__.mdwn
@@ -0,0 +1 @@
+I have several TB of media on a Debian ZFS server. If I created a git-annex repo for the data, how hard would it be get git-annex (using bup I assume) to back up the files onto a set of Blu Ray disks? I realize that 8TB of data would take about 320 BR 25GB disks, but it seems like git annex would be great for identifying what disk(s) I needed to recover a file. I'm good at bash scripting, and use git daily. I have no experience with git-annex or bup however. Any links to information or suggestions is very appreciated. Thanks!