Hi all,
having some grief getting amanda to backup an NT box (smb share).
NT 4.0 sp6a
share is "backup"
backup user owns the share, the directory, and all files within it
amandapass is setup as follows:
//bursar-new/backup$ somepassword BURSAR-NEW
BURSAR-NEW is the workgroup of the machine being backed up ie. it's not a
user in the main domain.
There's a line in disklist:
svr-new //bursar-new/backup$ comp-smb
and comp-smb is defined as:
define dumptype comp-smb {
global
comment "backing up smb partitions with compression"
compress server best
program "GNUTAR"
priority low
}
If I run amcheck I get:
Amanda Tape Server Host Check
-----------------------------
/data/amanda: 5651920 KB disk space available, using 5549520 KB.
ERROR: cannot overwrite active tape NEWC0015.
(expecting tape NEWC0005 or a new tape)
NOTE: skipping tape-writable test.
Server check took 32.177 seconds.
Amanda Backup Client Hosts Check
--------------------------------
Client check: 1 host checked in 0.569 seconds, 0 problems found.
(brought to you by Amanda 2.4.1p1)
***************************************************************
(done before my tapechange, obviously).
Amandad.debug contains:
Amanda 2.4 REP HANDLE 000-883B0508 SEQ 979854423
OPTIONS ;
running /usr/bin/smbclient \\\\bursar-new\\backup$ XXXX -E -U backup -W
BURSAR-NEW -c quit
OK //bursar-new/backup$
*************************************************************
and here looks to be a culprit... the share contains only 1 large file (3.5G
or so), and smbclient doesn't appear to understand how to read a file that
big.
calculating for amname '//bursar-new/backup$', dirname
'//bursar-new/backup$'
sendsize: getting size via smbclient for //bursar-new/backup$ level 0
sendsize: running "/usr/bin/smbclient '\\bursar-new\backup$' XXXXX -d 3 -U
backup -E -W BURSAR-NEW -c 'archive 0;recurse;dir'
"
added interface ip=127.0.0.1 bcast=127.255.255.255 nmask=255.0.0.0
added interface ip=xxx.xxx.xxx.xxx bcast=xxx.xxx.xxx.xxx nmask=255.255.255.0
Client started (version 2.0.7).
resolve_lmhosts: Attempting lmhosts lookup for name bursar-new<0x20>
resolve_wins: Attempting wins lookup for name bursar-new<0x20>
bind succeeded on port 0
Got a positive name query response from xxx.xxx.xxx.xxx ( xxx.xxx.xxx.xxx )
Connecting to xxx.xxx.xxx.xxx at port 139
Domain=[NEWADMIN] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0]
directory recursion is now on
received 3 entries (eos=1)
. DA 0 Thu Jan 18 23:23:25 2001
.. DA 0 Thu Jan 18 23:23:25 2001
daily A -192142336 Thu Jan 18 22:54:55 2001
49669 blocks of size 262144. 29096 blocks available
Total bytes listed: -192142336
.....
(no size line match in above smbclient output)
*********************************************************
is this what's causing the problem? If so, how do I get around it?
Cheers,
Chris
PS. Backups work fine aside from this one partition.
