Hi,
We have an running amanda environment (Amanda-3.2.1) based on Ubuntu
11.10 backing up
some XEN hosts.
Last week we did a full disaster recovery test and run into some
problems using the
amrestore tool.
In our config we have:
define tapetype LTO-3 {
comment "Created by amtapetype; compression enabled"
length 413997056 kbytes
filemark 0 kbytes
speed 51186 kps
blocksize 1024 kbytes
}
I we run "amrestore /dev/nst0 host /" it exits with
"ERROR: /bin/gzip exited with status 1"
If we try "amrestore --cconfig conf /dev/nst0 host /" it works
but it depends on the amanda.conf file being present and it's not
since it's a bare metal restore.
Our workaround is to do "amrestore -r /dev/nst0 host /" to read the RAW
files of the tape and then "dd if=host._.XXXX bs=1024k skip=1 | gzip -dc
| tar xv" to
extract the files. It works for us but it's not ideal.
amrestore is documented to have a -b <blocksize> option but it does not
work.
We tried "amrestore -b 1024k /dev/nst0 host /" but the perl code expects
an integer and
aborts with a usage.
"amrestore -b 1048576 /dev/nst0 host /" dies with
"ERROR: /bin/gzip exited with status 1" indicating the $opt_blocksize is
not working.
Is it possible to get amrestore to automatically detect the block-size?
Skipping all zero blocks
after the amanda header until start of data?
Best Regards,
Stefan Gustafsson
Expisoft AB, Sweden
