I've recently begun testing the restore procedures in order to write a script
to allow VERY easy restores (In case I'm not available) and noticed upon
trying to restore a directory structure on any host, locally or remotely,
amrestore (using dump to record and restore to restore) gives this error after
trying to load the specified disk/drive image and actually perform the
restore.
amrestore: 0: skipping start of tape: date 20001214 label Daily-04
amrestore: 1: skipping homer._.spool.20001214.0
amrestore: 2: skipping smb.sda3.20001214.1
amrestore: 3: skipping homer.hda1.20001214.1
amrestore: 4: skipping smb.sda2.20001214.0
amrestore: 5: restoring homer.md0.20001214.1
Error 32 (Broken pipe) offset 32768+32768, wrote 0
amrestore: pipe reader has quit in middle of file.
amrestore: skipping ahead to start of next file, please wait...
and immediately "exit 1" appears... Is this a problem with restore or
amrestore? Also, I've been trying to get a network restore working and do not
see a way to tell amrecover to specify a remote tapedrive (to recover from
client machines) or specify where to restore too (server restore directly to
clients.) I see that restore has the ability to restore from a remote device,
but restore uses the output of amrecover as it's source for extraction,
(negating it's ability to use a remote tape unless restore understands
amanda's tape format.) Does anyone have a workaround for this or an option for
amrecover to see a remote tapedrive? Or even a way to get restore to
understand an amanda tape... Any ideas would be appreciated.
Thanks ahead of time,
--
Thomas J. Hudak
Jr. Systems Administrator
Sistina Software Inc.
Phone: 612.379.3951 Fax: 612.379.3952
PGP signature
