diff options
6 files changed, 62 insertions, 0 deletions
diff --git a/doc/forum/A_little_help_with_headless_server_configuration.mdwn b/doc/forum/A_little_help_with_headless_server_configuration.mdwn new file mode 100644 index 000000000..3dc52be30 --- /dev/null +++ b/doc/forum/A_little_help_with_headless_server_configuration.mdwn @@ -0,0 +1,2 @@ +Attempting to setup a multiple server file share. I am really not sure how to configure and setup the headless system for sharing? Seems easy enough with the webapp and have my windows system appear to be working not sure how to get my Linux headless systems to sync up as well any help would be greatly appreciated. + diff --git a/doc/forum/Modus_operandi_for_local_full_backup.mdwn b/doc/forum/Modus_operandi_for_local_full_backup.mdwn new file mode 100644 index 000000000..587c18852 --- /dev/null +++ b/doc/forum/Modus_operandi_for_local_full_backup.mdwn @@ -0,0 +1,20 @@ +Hello, +I've been for several hours soaking up on git annex and I don't see how to efficiently achieve the following. Your thoughts welcome. + +Let's say I have a computer with a main disk and a backup disk. I currently use rsnapshot to rsync from main to backup and take periodic snapshots. Once the backup disk is filled up I archive it and I start with a fresh one. + +This is neat but for the lack of intelligent history. I'm contemplating moving to a VCS solution so changes through time can be tracked more easily. + +Let's say I want to move to git-annex as a way of keeping history, maybe even across backup disks. The common part would be to rsync from main to backup and then commit. I see the following showstoppers: + +1) If I put the backup repo in direct mode, past versions of files are lost since they never enter either plain git nor annex control. + +2) If I put the backup repo in indirect mode, rsync destroys all soft links resulting in unnecessary copying over. It also seems to cause further breakage when a regular file appears where there was a symlink. I know no rsync option to sync through links to the target files (rsync -K only works for folders). + +3) I could put the repo in direct mode, rsync, commit, put in indirect to save versions, and repeat at every backup. Seems kinda inefficient, there are hundreds of gigas in files. + +4) I can't have the main disk under annex and use the back disk as a remote because the main disk contains many git repos (whose history I don't mind losing with rsync -C, or I wouldn't consider git-annex for backup at all). Also I'm not partial to populate the main disk with something only related to backup. + +If rsync -K worked with files there would be no problem. I'm missing the right flag here? Or something else that can be done on the git-annex side? + +Thanks in advance. diff --git a/doc/forum/Modus_operandi_for_local_full_backup/comment_1_fa8ac55ebd94312a36b284047b6cf932._comment b/doc/forum/Modus_operandi_for_local_full_backup/comment_1_fa8ac55ebd94312a36b284047b6cf932._comment new file mode 100644 index 000000000..b6cc7e989 --- /dev/null +++ b/doc/forum/Modus_operandi_for_local_full_backup/comment_1_fa8ac55ebd94312a36b284047b6cf932._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="https://id.koumbit.net/anarcat" + subject="why use rsync at all?" + date="2015-11-11T01:13:00Z" + content=""" +i basically exclude git-annex repositories from my backups now. i have a `numcopies` setting to a satisfactory number (say 2 or 3) that ensures that there are at least 2 copies of every file. then i send copies off to external drives, when they are full, i create a new repository on a new drive. + +old versions are kept as long as you don't `dropunused`. +"""]] diff --git a/doc/forum/Modus_operandi_for_local_full_backup/comment_2_fc2ac75608e91018f67c3753e9b09f76._comment b/doc/forum/Modus_operandi_for_local_full_backup/comment_2_fc2ac75608e91018f67c3753e9b09f76._comment new file mode 100644 index 000000000..5556f6697 --- /dev/null +++ b/doc/forum/Modus_operandi_for_local_full_backup/comment_2_fc2ac75608e91018f67c3753e9b09f76._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="alejandro@2e9e229fdf45d44cd300a5681432552693d458ab" + nickname="alejandro" + subject="comment 2" + date="2015-11-11T08:29:09Z" + content=""" +Hi anarcat, if I understand you correctly you're using method 4) in my original post. That is, having the source of backups as a git annex repo. However, all my readings on this site seem to indicate poor interaction with nested git repositories, that I would have. Isn't that so? +"""]] diff --git a/doc/forum/Modus_operandi_for_local_full_backup/comment_3_6089f53d8af5746f2a410d0214567943._comment b/doc/forum/Modus_operandi_for_local_full_backup/comment_3_6089f53d8af5746f2a410d0214567943._comment new file mode 100644 index 000000000..f388d57b8 --- /dev/null +++ b/doc/forum/Modus_operandi_for_local_full_backup/comment_3_6089f53d8af5746f2a410d0214567943._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="https://id.koumbit.net/anarcat" + subject="comment 3" + date="2015-11-11T14:53:11Z" + content=""" +that is so: git annex doesn't \"backup\" very well other git repositories. it's probably possible, but that's not really what git-annex is designed for. git-annex is [[not]] a backup system: it's more like an archival system. so if you want to backup your whole system and keep history, the [[not]] page recommends [[bup]], but i would also recommend [borg](http://borgbackup.readthedocs.org/). + +if you have git repos: backup those using your regular backup system, git-annex won't help you there. you can clone the repos using git, use rsync and whatnot. git itself keeps history and unless you royally mess up, git is pretty forgiving. + +for large files: create topical git-annex repositories. i have one for \"music\", \"video\", \"podcasts\", and so on. those are managed on a per-repo basis. + +so when i do my \"backups\" (which include \"archiving\" as well now), i connect the hard drives in my computer, run the `borg` (or `bup`) backup and then run `git annex sync --content` on all my git-annex repositories. that way new files in the git-annex repositories are synced to the external drive and files not managed by git-annex (yes, including non-git-annex git repos) are backed up as well. + +hope that helps +"""]] diff --git a/doc/forum/Modus_operandi_for_local_full_backup/comment_4_4c27aae1361465993fb60997bb0eadf8._comment b/doc/forum/Modus_operandi_for_local_full_backup/comment_4_4c27aae1361465993fb60997bb0eadf8._comment new file mode 100644 index 000000000..7daf4a7a2 --- /dev/null +++ b/doc/forum/Modus_operandi_for_local_full_backup/comment_4_4c27aae1361465993fb60997bb0eadf8._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="alejandro@2e9e229fdf45d44cd300a5681432552693d458ab" + nickname="alejandro" + subject="comment 4" + date="2015-11-11T15:22:05Z" + content=""" +I see, so your comments basically match my grasp on the situation. Thanks for the borg pointer, I have been reading on bup too and from posts in the mailing list I'm afraid it might not be mature enough for my particular use case. +"""]] |