Trouble with large backup
David Smalley
david at brightbox.co.uk
Fri Apr 24 16:30:34 UTC 2009
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
We've recently started to use Brackup to sync our bacula backup data
over to s3. After a couple of successful test runs we set it to work
on our 500gb~ of backups and it went on a few days.
Unfortunately we had to kill the backup a few times and restart it
while we got traffic shaping in place to stop saturating our outbound
connection. Every night we had to kill the process and then restart it
after the bacula backups had completed.
Now when I come to try a test restore/list_backups/gc on the backup
I'm getting some funny results..
$brackup-target -v amazon gc
Unexpected line in metafile /tmp/1SQBmeinz5/o1m7MXxCX2, line 1: ????
n_???fsk???+?|?LiU??OK(y????Q??9??E??T??jv??w????|T0????1z?? at /usr/
local/share/perl/5.8.8/Brackup/Metafile.pm line 45, <$__ANONIO__> line
1.
$ brackup-target -v amazon list_backups
Backup File Backup Date Size
(B)
- ----------- -----------
- --------
Argument "\x{32}\x{30}..." isn't numeric in numeric comparison (<=>)
at /usr/local/bin/brackup-target line 122.
Argument "\x{32}\x{30}..." isn't numeric in numeric comparison (<=>)
at /usr/local/bin/brackup-target line 122.
Argument "\x{32}\x{30}..." isn't numeric in localtime at /usr/local/
share/perl/5.8.8/Brackup/TargetBackupStatInfo.pm line 34.
bacula-1240436350 Thu 01 Jan 1970 00:33:29 5388249
Argument "\x{32}\x{30}..." isn't numeric in localtime at /usr/local/
share/perl/5.8.8/Brackup/TargetBackupStatInfo.pm line 34.
bacula-1240512974 Thu 01 Jan 1970 00:33:29 5397846
$ brackup-restore --from=bacula-20090423.brackup --to=/tmp -v --
just="a_backup-incpool_3"
Your Amazon AWS access key? <key>
Your Amazon AWS secret access key? <secret>
Your Amazon AWS prefix? (Leave empty if none) <prefix>
* restoring a_backup-incpool_3 to /tmp/a_backup-incpool_3
gpg: cancelled by user
gpg: decryption failed: secret key not available
Error doing restore: Failed to decrypt with gpg: Inappropriate ioctl
for device
When I check /tmp I see a file of zero bytes.
I'm wondering if gpg is failing because brackup doesn't have a
complete backup of the file and so therefore it's unable to work out
which gpg key it needs to decrypt?
I'm starting to worry that we've just sent 450gb of inaccessible
backups up to s3...
Any help appreciated.
David
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
iEYEARECAAYFAknx6SsACgkQ/jcv4JaFGCJtSgCfdUo4SYx9JxZ46c0lsNiU8L/c
X+MAn1N3fmaFoj0YbL3Lcgl7O6kpBknD
=7vUE
-----END PGP SIGNATURE-----
More information about the brackup
mailing list