>The first question is when using amverify I get this message:
>...
>>Skipped LB-S545A.__WS-P200A_BACKUP.20001113.0 (** Cannot do /usr/local/samba/
>bin/smbclient dumps)
>>...
> ... most replys say to edit amverify
> and add a entry to idenitfy the dump type needed..but I do not know how to
> implement this with smbclient...
As I understand it, smbtar backups are compatible with tar, so I guess
we need to add (yet another :-) hack to run tar on backups that say they
were written with smbclient.
Patches welcome. :-)
> When running either amrecover or amrestore to recover the backup, it
>seems to be very slow...
Don't know about this since I avoid PC's at all cost.
>This is how I used the amrestore/amrecover commands:
>
> Using amrestore as "amrestore -p /dev/nst2 <host> //WS-K200A/BACKUP | s
>mbclient <passwd> //WS-K200A/BACKUP -U Backup -d0 -Tx -" to recover the files
>from tape stright to the share....very slow and then stops with a broken pipe.
>..
The broken pipe may be OK. That just means something on the right hand
side of a pipe terminated while the thing on the left was still writing
data. If smbclient (or any restore program) stops after it restores the
requested file(s), and amrestore is still reading more data from tape,
it is going to issue that message, but it is innocuous.
> Using amrecover, first using smbmount to mount the share to a local dir
>ectory, and then using amrecover to restore into this directory...
I didn't think the smbmount was necessary, but then again, I know zip
about Amanda and PC's. Surely someone else on this list will pipe in.
>Mathhew Johnston
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
