heroku/WAL-E — Issue #33: not working - backup-list, backup-fetch
Author: useruph3xaiR
Created: 2012-02-28 20:23:01+00:00
State: open

Back in October, I tried out WAL-E on a test database and got it all working.

Now, I am building a new database pair for production and wanted to use WAL-E and it seems to not be completely working right.

I can do wal-push and backup-push and I can "delete everything".

But I can not get backup-list or backup-fetch to work.

Also, I didn't get as far as trying wal-fetch yet either.

$ /usr/bin/envdir /etc/wal-e.d/adchoices-db02 wal-e backup-push /data/postgresql/9.0/main
2012-02-28T19:56:21.238+00 pid=28751 wal_e.operator.s3_operator INFO MSG: start upload postgres version metadata
DETAIL: Uploading to s3://adchoices-db02/backups/basebackups_005/base_00000001000000000000000A_00000032/extended_version.txt.
2012-02-28T19:56:21.369+00 pid=28751 wal_e.operator.s3_operator INFO MSG: postgres version metadata upload complete
2012-02-28T19:56:21.455+00 pid=28751 wal_e.worker.s3_worker INFO MSG: beginning volume compression
DETAIL: Building volume 0.
2012-02-28T19:56:23.301+00 pid=28751 wal_e.worker.s3_worker INFO MSG: begin uploading a base backup volume
DETAIL: Uploading to "s3://adchoices-db02/backups/basebackups_005/base_00000001000000000000000A_00000032/tar_partitions/part_0.tar.lzo".
2012-02-28T19:56:24.867+00 pid=28751 wal_e.worker.s3_worker INFO MSG: finish uploading a base backup volume
DETAIL: Uploading to "s3://adchoices-db02/backups/basebackups_005/base_00000001000000000000000A_00000032/tar_partitions/part_0.tar.lzo" complete at 68525KiB/s.
NOTICE: pg_stop_backup complete, all required WAL segments have been archived

$ /usr/bin/envdir /etc/wal-e.d/adchoices-db02 wal-e backup-list
name	last_modified	expanded_size_bytes	wal_segment_backup_start	wal_segment_offset_backup_start	wal_segment_backup_stop	wal_segment_offs

# no output ????

$ /usr/bin/envdir /etc/wal-e.d/adchoices-db02 wal-e delete --confirm everything
2012-02-28T20:18:36.880+00 pid=28910 wal_e.main INFO MSG: deleting data in S3
2012-02-28T20:18:37.076+00 pid=28910 wal_e.worker.s3_worker INFO MSG: deleting part of a base backup
DETAIL: The key being deleted is s3://adchoices-db02/backups/basebackups_005/base_00000001000000000000000A_00000032/extended_version.txt.
2012-02-28T20:18:37.190+00 pid=28910 wal_e.worker.s3_worker INFO MSG: deleting part of a base backup
DETAIL: The key being deleted is s3://adchoices-db02/backups/basebackups_005/base_00000001000000000000000A_00000032/tar_partitions/part_0.tar.lzo.
2012-02-28T20:18:37.248+00 pid=28910 wal_e.worker.s3_worker INFO MSG: deleting part of wal logs
DETAIL: The key being deleted is s3://adchoices-db02/backups/wal_005/000000010000000000000009.lzo.
2012-02-28T20:18:37.294+00 pid=28910 wal_e.worker.s3_worker INFO MSG: deleting part of wal logs
DETAIL: The key being deleted is s3://adchoices-db02/backups/wal_005/00000001000000000000000A.00000020.backup.lzo.
2012-02-28T20:18:37.313+00 pid=28910 wal_e.worker.s3_worker INFO MSG: deleting part of wal logs
DETAIL: The key being deleted is s3://adchoices-db02/backups/wal_005/00000001000000000000000A.lzo.
2012-02-28T20:18:37.332+00 pid=28910 wal_e.worker.s3_worker INFO MSG: deleting part of wal logs
DETAIL: The key being deleted is s3://adchoices-db02/backups/wal_005/00000001000000000000000B.lzo.
2012-02-28T20:18:37.354+00 pid=28910 wal_e.worker.s3_worker INFO MSG: deleting part of wal logs
DETAIL: The key being deleted is s3://adchoices-db02/backups/wal_005/00000001000000000000000C.lzo.
2012-02-28T20:18:37.374+00 pid=28910 wal_e.worker.s3_worker INFO MSG: deleting part of wal logs
DETAIL: The key being deleted is s3://adchoices-db02/backups/wal_005/00000001000000000000000D.lzo.
2012-02-28T20:18:37.414+00 pid=28910 wal_e.worker.s3_worker INFO MSG: deleting part of wal logs
DETAIL: The key being deleted is s3://adchoices-db02/backups/wal_005/00000001000000000000000E.lzo.