2011-03-04 17:19:26 +00:00
|
|
|
### use case: The Archivist
|
2010-10-19 23:28:29 +00:00
|
|
|
|
|
|
|
|
Bob has many drives to archive his data, most of them kept offline, in a
|
|
|
|
|
safe place.
|
|
|
|
|
|
|
|
|
|
With git-annex, Bob has a single directory tree that includes all
|
2010-10-31 23:57:05 +00:00
|
|
|
his files, even if their content is being stored offline. He can
|
2010-10-19 23:28:29 +00:00
|
|
|
reorganize his files using that tree, committing new versions to git,
|
2011-02-15 05:58:23 +00:00
|
|
|
without worry about accidentally deleting anything.
|
2010-10-19 23:28:29 +00:00
|
|
|
|
|
|
|
|
When Bob needs access to some files, git-annex can tell him which drive(s)
|
|
|
|
|
they're on, and easily make them available. Indeed, every drive knows what
|
2011-03-04 17:04:49 +00:00
|
|
|
is on every other drive.
|
2011-03-04 17:12:48 +00:00
|
|
|
<small>[[more about location tracking|location_tracking]]</small>
|
2011-03-04 16:31:01 +00:00
|
|
|
|
2011-03-09 05:57:30 +00:00
|
|
|
Bob thinks long-term, and so he appreciates that git-annex uses a simple
|
2011-03-04 16:31:01 +00:00
|
|
|
repository format. He knows his files will be accessible in the future
|
2011-03-04 17:15:04 +00:00
|
|
|
even if the world has forgotten about git-annex and git.
|
2011-03-04 17:12:48 +00:00
|
|
|
<small>[[more about future-proofing|future_proofing]]</small>
|
2010-10-19 23:28:29 +00:00
|
|
|
|
2011-02-15 05:58:23 +00:00
|
|
|
Run in a cron job, git-annex adds new files to archival drives at night. It
|
2010-10-19 23:28:29 +00:00
|
|
|
also helps Bob keep track of intentional, and unintentional copies of
|
|
|
|
|
files, and logs information he can use to decide when it's time to duplicate
|
2011-03-04 17:04:49 +00:00
|
|
|
the content of old drives.
|
2011-03-04 17:12:48 +00:00
|
|
|
<small>[[more about backup copies|copies]]</small>
|
