On 3/20/01, 8:20:12 PM, "John R. Jackson" <[EMAIL PROTECTED]>
wrote regarding Re: Samba restores don't work ... :
...
> Go to amrecover.debug and look at the smbclient command. What
happens
> if you do something like this on the (sun26) client:
> rsh <AmandaServer> mt -f /dev/autodrive_norewind rewind
> rsh <AmandaServer> amrestore -hp /dev/autodrive_norewind \
> sun26 //nt4/StarTeamVault | \
> smbclient <WhateverTheOtherArgsAre>
> In particular, does smbclient whine about anything? What if you
change
> -d0 to -d1 (or -d2, etc) on smbclient? You should see more debugging
> information.
...
Using -d3 we have:
# amrestore -ph /dev/autodrive_norewind sun26 "^//nt4/StarTeamVault$"
20010320 | smbclient //nt4/StarTeamVault XXXXX -U backup%backup -d3
-Tx - ./Java/Server-16-Feb-01-12-46-32-ORG.Log
Client started (version 2.0.7).
resolve_lmhosts: Attempting lmhosts lookup for name nt4<0x20>
resolve_hosts: Attempting host lookup for name nt4<0x20>
Connecting to www.xxx.yyy.zzz at port 139
Domain=[MASTER] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]
tree connect failed: ERRDOS - 71
amrestore: 0: skipping start of tape: date 20010320 label Daily02
...
amrestore: write error: Broken pipe
On a different NT machine:
# amrestore -ph /dev/autodrive_norewind sun26 "^//nt5b/GoldMine$"
20010319 | smbclient //nt5b/GoldMine XXXXX -U backup%backup -d3 -Tx -
./SOMEBODY.ini
Client started (version 2.0.7).
resolve_lmhosts: Attempting lmhosts lookup for name nt5b<0x20>
resolve_hosts: Attempting host lookup for name nt5b<0x20>
Connecting to www.xxx.yyy.zzz at port 139
Domain=[MASTER] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]
amrestore: 0: skipping start of tape: date 20010319 label Daily01
...
checksums don't match 0 17852
abandoning restore, -1 from read tar header
amrestore: write error: Broken pipe
####################################################################
It's odd that with Full Control on the shares, the backup user can
read them all but has troubles when restoring.
Thanks,
tony
