I'm trying to follow the directions on this tips page to easily back up some large home videos to Glacier. I followed the steps and everything worked fine until the git annex copy
, at which point it claimed it was successful but had uploaded 0 bytes, as well as dumping the usage message for glacier-cli
at the terminal (without any error):
Emily $ git annex copy --to glacier README
copy README (gpg) (checking glacier...) (to glacier...)
100% 0.0 B/s 0s
glacier <command> [args]
Commands
vaults - Operations with vaults
jobs - Operations with jobs
upload - Upload files to a vault. If the vault doesn't exits, it is
created
Common args:
--access_key - Your AWS Access Key ID. If not supplied, boto will
use the value of the environment variable
AWS_ACCESS_KEY_ID
--secret_key - Your AWS Secret Access Key. If not supplied, boto
will use the value of the environment variable
AWS_SECRET_ACCESS_KEY
--region - AWS region to use. Possible values: us-east-1, us-west-1,
us-west-2, ap-northeast-1, eu-west-1.
Default: us-east-1
Vaults operations:
List vaults:
glacier vaults
Jobs operations:
List jobs:
glacier jobs <vault name>
Uploading files:
glacier upload <vault name> <files>
Examples :
glacier upload pics *.jpg
glacier upload pics a.jpg b.jpg
ok
(Recording state in git...)
Doing a glacier vaults
also does not show any new vaults, and getting the usage message is obviously not normal.
I tried doing a manual upload to a vault I already had sitting around from some years ago called TVault
, and that looked to work fine:
Emily $ glacier upload TVault README
Uploading README to TVault... done. Vault returned ArchiveID [omitted]
(The update date hasn't updated on the management console yet, but I understand that may take up to a day.)
Does anyone know what's going on, or is there at least a way to get a useful error message to output?
Sounds like you're running the boto glacier command rather than the glacier-cli tool. Unfortunately they have the same name (my intention was to deprecate the boto tool but boto upstream deprecated boto entirely instead). The current plan is to rename glacier-cli to glcr, but I haven't got round to doing that yet.
Try making sure that "glacier" runs the glacier-cli tool rather than boto's glacier.
Nice catch! I couldn't find any install option for
glacier-cli
, so I just added a symlink to the source distribution and figured that would take care of it.But:
Oops. I changed the location of the symlink to somewhere earlier in the path, uninited and reinited the repository, and it uploaded the README.
Unfortunately, now I'm getting a different error, some kind of Unicode issue, when I try to upload one of the files I actually want to back up:
Here's my complete session setting up the repository, in case it contains other useful information:
Thanks a lot for your help!
Note that, since version 5.20150219, git-annex probes to see if the "glacier" program in PATH is the one from boto, and fails with a nicer error message.
The UnicodeDecodeError is mentioned in the thread for glacier too. There is a workaround posted in that thread. It would probably be good to nudge the boto maintainers to apply the fix, which has been available for at least 3 months now.