git-annex/doc/assistant/archival_walkthrough.mdwn
Joey Hess e213ef310f git-annex (5.20140717) unstable; urgency=high
* Fix minor FD leak in journal code. Closes: #754608
  * direct: Fix handling of case where a work tree subdirectory cannot
    be written to due to permissions.
  * migrate: Avoid re-checksumming when migrating from hashE to hash backend.
  * uninit: Avoid failing final removal in some direct mode repositories
    due to file modes.
  * S3: Deal with AWS ACL configurations that do not allow creating or
    checking the location of a bucket, but only reading and writing content to
    it.
  * resolvemerge: New plumbing command that runs the automatic merge conflict
    resolver.
  * Deal with change in git 2.0 that made indirect mode merge conflict
    resolution leave behind old files.
  * sync: Fix git sync with local git remotes even when they don't have an
    annex.uuid set. (The assistant already did so.)
  * Set gcrypt-publish-participants when setting up a gcrypt repository,
    to avoid unncessary passphrase prompts.
    This is a security/usability tradeoff. To avoid exposing the gpg key
    ids who can decrypt the repository, users can unset
    gcrypt-publish-participants.
  * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet
    exist, since it is not automatically created for Gnome 3 users.
  * Windows: Move .vbs files out of git\bin, to avoid that being in the
    PATH, which caused some weird breakage. (Thanks, divB)
  * Windows: Fix locking issue that prevented the webapp starting
    (since 5.20140707).

# imported from the archive
2014-07-17 11:27:25 -04:00

32 lines
1.4 KiB
Markdown

Normally, the git-annex assistant makes your files be available
wherever you use it, and so a copy of each file is stored in each repository.
That's perfect for files you're using right now, but what about files you're
not using any more?
You could just delete those files, but it's better to archive them, so
you can access them later. All you need to get started archiving your old
files is a USB drive, or an [Amazon Glacier](http://aws.amazon.com/glacier/)
account.
The webapp makes it easy to make a repository on either a USB drive,
or on Amazon Glacier. Once the repository is created, be sure to
put it in either the small archive, or full archive repository group.
[[!img repogroups.png]]
Now when you're done with a file, just move it into a directory named
"archive". The assistant will notice you put it there, and next time it
has the opportunity (when you plug in the USB drive, or when it can
talk to Amazon Glacier over the network), will move the file's
content to your archive repository.
You'll no longer be able to open the file once it's been archived.
If you later want to access it, you can just copy or move it out
of the archive directory, and the assistant will retrieve its
content from the archive.
Note that retrieving data from Amazon Glacier takes 4 to 5 hours.
### screencast
[[!inline feeds=no template=bare pages=videos/git-annex_assistant_archiving]]