amanda-2.4.4p3, file driver, chg-disk, and infinite driver retries
I'm using amanda-2.4.4p3 with the file driver and chg-disk changer for vtapes. Sometimes a dump fails and driver retries: driver: client /some/path 1 [dump to tape failed, will try again] and then it fails again and retries again, and this repeats until I kill the amanda processes. This last time this happened I caught it after driver/dumper/taper had created about 200 0 length dump files in the vtape directory. The client machine it was trying to dump from was offline. It had gone offline sometime after the planner stage and so the planner had included it. There was no indication that this retrying was ever going to stop. I have been using amanda for years with tapes and I never experienced this behaviour before so it came as quite a surprise. Is there any way to limit this retrying by driver? Thanks, -- Todd Pfaff [EMAIL PROTECTED] Research High-Performance Computing Support ABB 132, McMaster University, Hamilton, Ontario, Canada, L8S 4M1 phone: voice: 905-525-9140 ext 22920 fax: 905-528-3773
Re: amanda-2.4.4p3, file driver, chg-disk, and infinite driver retries
Thanks to Jon LaBadie, Gene Heskett, and Jean-Louis Martineau for replies. Jean-Louis supplied me with a patch which I modified slightly and that I'm now using. It turns out that some code in server-src/driver.c will allow a dump to be retried indefinitely, if dumper returns TRYAGAIN and taper returns DONE. See around line 2203 in 2.4.4p3 server-src/driver.c. I've been using amanda for years with real tapes but I've just started using vtapes this past week and this is the first time I've noticed such behaviour. This is a working amanda configuration that I've used to dump many hundreds of gigabytes already, both to real tapes in the past and to vtapes in recent days. But consistently with vtapes, if a client is alive during planning and was added to the schedule, and then this client goes offline before the dump starts, this condition will occur whereby dumper says TRYAGAIN, taper says DONE, forever until killed (or until taper gets an error for some other reason I guess). -- Todd Pfaff [EMAIL PROTECTED] Research High-Performance Computing Support ABB 132, McMaster University, Hamilton, Ontario, Canada, L8S 4M1 phone: voice: 905-525-9140 ext 22920 fax: 905-528-3773
Re: Compiling amanda on an (ugh) Windows box?
there is a sourceforge group named Amanda Backup Win32 Clients http://sourceforge.net/projects/amanda-win32/ On Wed, 29 Aug 2001, Gene Heskett wrote: Does anyone know of a decent compiler for windows thats not a bank breaker? I'd like to see if its buildable for the general run of W95 and W98 machines. And has anyone made amanda work as client on a windows box other than via samba? In other words, am I just spinning my wheels to even think about it? Cheers, Gene -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: FW: chg-scsi
I've just been through this (ie. using the newer, supported chg-scsi from the 2.5.0 cvs development source with an amanda-2.4.2p2 server) so the procedure is fresh in my mind. Here's what you do. - build and install your 2.4.2p2 server - get the 2.5.0 source via cvs - first, login to cvs server - just press enter when prompted for password cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot/amanda login - next, get the source - this will retrieve the entire 2.5.0 source from the cvs server into your current directory cvs -z3 -d:pserver:[EMAIL PROTECTED]:/cvsroot/amanda co amanda - build the amanda-2.5.0 server from this source (you may need the autoconf tools to proceed with this, but don't ask me any questions about this, you're on your own) - when the build is finished, copy changer-src/chg-scsi to your amanda-2.4.2p2 server libexec directory That's it! Works great with an Exabyte 215 changer and Mammoth2 drive. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: Incremental Backup and Backup NT from Unix server
On 31 May 2001, Alexandre Oliva wrote: And yet another thing to note here is that Cygwin has (recently?) gained a program named cygrunsrv, that could be used to start a Cygwin-built [x]inetd, that could then fire amandad natively on Windows. I haven't got to the trouble of going down this path, but it seems like someone with a lot of Windows machine to back up could observe a significant speed up avoiding all of the SMB overhead, gaining more levels of incremental backups meanwhile. has anyone successfully built the amanda (2.4.2p2?) client using cygwin? last time i tried, i didn't get very far and gave up for lack of time. this cygrunsrv sounds interesting since it was an important missing piece of the whole amanda-on-windows puzzle, so i'll revisit this sometime soon. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: Antwort: Incremental Backup and Backup NT from Unix server
On 31 May 2001, Alexandre Oliva wrote: I downloaded tar-1.13.tar.gz from http://www.gnu.org/directory/tar.html Is this the right version of gtar? No, see docs/INSTALL. I found this package gives me tar instead of gtar executable. This doesn't matter. Amanda's configure looks for gnutar, gtar and tar. I have a suggestion related to this. Get a known-good version of gnutar and install it somewhere specific to amanda, like /usr/local/amanda/libexec/gnutar, and explicitly tell configure to use this path rather than let it find tar somewhere else. This avoids the problem of a good tar being later replaced with a bad tar during an upgrade or patch installation. In my case, I'm still using gnutar-1.12 on all my amanda clients. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
amflush, chunks, cruft warnings
when running amflush on amanda dumps containing chunk files, can the warning messages about cruft files that correspond to chunks be ignored? for example... NOTES: amflush: visual._1.0.1: ignoring cruft file. are these chunks really being taped along with the rest of the dump, despite the warning message? -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: amflush, chunks, cruft warnings
On Thu, 10 May 2001, John R. Jackson wrote: when running amflush on amanda dumps containing chunk files, can the warning messages about cruft files that correspond to chunks be ignored? Yes (as I recall). Or you can upgrade your server to 2.4.2p2 where the problem is fixed :-). are you sure it's fixed? the server i'm running amflush on is running amanda 2.4.2p2. and, yes, i know i'm running the amflush from the 2.4.2p2 installation (ie. 'which amflush' returns the expected path). -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: amflush, chunks, cruft warnings
On Thu, 10 May 2001, John R. Jackson wrote: are you sure it's fixed? ... H. I sure thought it was. Do you have one of those chunks still laying around? no, amflush removed them. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
amanda server behind linux ipchains firewall
I have an amanda 2.4.2p2 server behind a linux ipchains firewall that is attempting to backup amanda 2.4.2p2 clients outside the firewall. The firewall is also IP-masquerading. I've read the information in the FAQ-O-Matic about amanda from behind a firewall and I've followed the instructions there, but my system is still not working. The clients outside the firewall still fail with either: ERROR: client1: [host firewall-host: port 62940 not secure] or WARNING: client2: selfcheck request timed out. Host down? I've built amanda-2.4.2p2 for both the server and clients with: PORTRANGE=850,859 UDPPORTRANGE=850,859 and I've opened up incoming forwarded connections from the outside network for tcp and udp ports 850-859 on the firewall host. Is my situation more involved because of the IP-masquerading firewall? Does anyone know what I've missed? -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: amanda server behind linux ipchains firewall
On Sun, 22 Apr 2001, John R. Jackson wrote: Since you're running 2.4.2p2, you should be able to see a line like this in /tmp/amanda/amcheck.*.debug: amcheck: dgram_bind: socket bound to 0.0.0.0.853 That tells you what port amcheck started out on (853 in this case). on each client, or on the server? i see no amcheck debug files on the clients. on the server i see two such files from my most recent amcheck run, containing: # cat amcheck.2001042216.debug amcheck: debug 1 pid 29377 ruid 10001 euid 0 start time Sun Apr 22 10:00:06 2001 amcheck: dgram_bind: socket bound to 0.0.0.0.856 amcheck: pid 29377 finish time Sun Apr 22 10:00:06 2001 # cat amcheck.2001042216000.debug amcheck: debug 1 pid 29382 ruid 10001 euid 0 start time Sun Apr 22 10:00:06 2001 amcheck: dgram_bind: socket bound to 0.0.0.0.684 amcheck: pid 29382 finish time Sun Apr 22 10:00:36 2001 I'm real fuzzy about firewalls, but this will let you at least confirm Amanda is staying within the range you asked it to. Once you know that, it's got to be a firewall port translation problem, i.e. it took that nice, innocent 853 and translated it into a icky, bad 62940. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: restoring from chunked holding disk files
On Fri, 20 Apr 2001, John R. Jackson wrote: I want to restore a filesystem from some amanda holding disk chunk files: -rw--- 1 backup backup 2147385344 Apr 20 04:04 mmri1001._2.0 -rw--- 1 backup backup 2147385344 Apr 20 04:17 mmri1001._2.0.1 -rw--- 1 backup backup 1540063232 Apr 20 04:30 mmri1001._2.0.2 So, I need to do something like this: cat mmri1001._2.0* | amrestore -p - mmri1001 /2 | tar tf - |p Wow, are you ever working too hard :-). Tell me about it. I've been working on a disaster recovery all day and I'm a bit frazzled. If those files are truely in the holding disk (i.e. you didn't bring them back from tape), amrestore (certainly in 2.4.2 and I think before that) already knows how to read from the holding disk and will do all the chaining for you. So it would be: amrestore -p /path/to/mmri1001._2.0 | tar tf ... Excellent, thanks. I'm glad it's easier than I was making it out to be. If that doesn't work for some reason, go down a layer and use subshells with dd: ( dd if=mmri1001._2.0 bs=32k skip=1 ; \ dd if=mmri1001._2.0.1 bs=32k skip=1 ; \ dd if=mmri1001._2.0.2 bs=32k skip=1 ) | gunzip | tar ... (remove the gunzip if you're not using software compression, of course). Well, that's cool too. This was pretty much what I was asking for, I just wasn't sure how to accomplish it. But I'm trying your simpler suggestion above first. Thanks again John. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: restoring from chunked holding disk files
On Fri, 20 Apr 2001, John R. Jackson wrote: To deal with multiple holding disks and chunks being scattered around, the header on the files contains a link to the next file. It's absolute and valid from the server point of view. I suspect that's something we need to think about in the future (I can see it causing other problems), but is certainly nailing you right now. Any chance you can create temporary symlinks on the client to emulate the server holding disk structure? Like "ln -s /net/mmri1011/2 /2"? yup, already thought of that workaround, even though i didn't understand the cause of the problem. i did this and it's working... ln -s /net/mmri1011/2/amanda /2/amanda -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: Failure on W2k client
Ok, I think finally understand what Marty is trying to say. Marty, there are many people on this list who have been using samba for years and understand it very well and how it interacts with amanda, and if we couldn't understand the gist of your initial question, don't blame our lack of understanding of the english language. :-) Marty says his samba setup works, but because of the fallback from wins to broadcast the lookup takes longer than amanda is willing to wait. Amanda times out and as far as amanda is concerned, smbclient failed. I'm not even sure what the implications of this are or how to make it work more efficiently, I'm just interpreting what he stated. Marty, is this correct? Now, this said, I still think the problem is with samba. You should 'fix' your samba setup so that it doesn't take so long to do a lookup. Todd On Wed, 4 Apr 2001, David Lloyd wrote: Marty! I suggest you put your asbestos, flame resistant suit on... Again: THIS IS NOT AMANDA'S FAULT! IT IS SMBCLIENT'S FAULT! You obviously cannot understand what I am saying, or you have not followed this thread. If you cannot understand English I will have this translated into any other language that I have a character set for: SMBCLIENT CAN CONTACT MY WINDOWS 2000 SERVER. IT DOES NOT FAIL. IT WORKS VIA BROADCAST AND AMANDA FAILS TO SEE THAT IT WORKS. Or to reword this: SAMBA IS ABLE TO CONTACT MY WINDOWS 2000 SERVER; SMBCLIENT CAN CONTACT IT. HOWEVER, IT DOES THIS VIA BROADCAST AND AMANDA FAILS. As far as I'm concerned SMB is working correctly. It is setup to use wins, wins fails and it therefore contacts my Windows 2000 server by broadcast and connects. Perfectly. So how is it smbclient's fault when smbclient works? I can't understand your English... DSL -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: Failure on W2k client
My last message should have been directed to David Lloyd, not Marty Shannon. Sorry Marty! -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: Samba Report
On Thu, 29 Mar 2001, David Lloyd wrote: using 2.4.2p1...I assure you that: //NAME/directory user%password Doesn't work for me... what happens if you run: smbclient //NAME/directory -U user%password or smbclient //NAME/directory -U password that is essentially what amanda is doing in the two different cases you've tried (plus a few more smbclient arguments that shouldn't affect the behaviour you're experiencing). if those commands do not work as expected, then solve the samba problem and amanda should work as expected. a note about this should probably be written in the docs/SAMBA file because 99% of the problems people have with amanda/samba backups are samba problems that should be debugged independently of amanda. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: Samba Report
uhhh, are you sure you have amanda-2.4.2p1 installed, and are you certain that you don't have a previous version installed somewhere? this looks suspiciously like you have an older version of sendbackup-gnutar running. in fact, i just had a close look at the 2.4.2p1 source code, and i guarantee you that whatever is running and generating the log below is not 2.4.2p1. it's likely 2.4.1x. if you have the locate command on your system, try 'locate sendbackup-gnutar' and see what that turns up. On Fri, 30 Mar 2001, David Lloyd wrote: Hmmm! Amanda is running: sendsize.debug:sendsize: spawning "/usr/bin/smbclient" in pipeline sendsize.debug:sendsize: argument list: "smbclient" "\\THESHARE\thedirectory" "the_password" "-d" "0" "-U" "backup" "-E" "-c" "archive 1;recurse;du" And it's working. Notably the command it says its running doesn't work by hand so I suspect that it's a different command being implemented. Now I'm getting more confused. I think I might point AMANDA at my remote samba server and do a packet trace to work out EXACTLY what it is sending over... that is essentially what amanda is doing in the two different cases you've tried (plus a few more smbclient arguments that shouldn't affect the behaviour you're experiencing). if those commands do not work as expected, then solve the samba problem and amanda should work as expected. Then explain the above. a note about this should probably be written in the docs/SAMBA file because 99% of the problems people have with amanda/samba backups are samba problems that should be debugged independently of amanda. Oh, I downloaded the patched version (as opposed to patching it myself) and it displays the same behaviour... DSL -- And though you turn from me To glance behind The Phantom of the Opera is there... Inside your mind! -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
Re: Samba Report
On Thu, 29 Mar 2001, Todd Pfaff wrote: if you have the locate command on your system, try 'locate sendbackup-gnutar' and see what that turns up. sorry, that should be 'locate sendbackup'. there is no program sendbackup-gnutar, the source module sendbackup-gnutar.c is used to build program sendbackup, but sendbackup-gnutar.c is where the smbclient calling code is found. -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
RE: amanda mail report size
On Fri, 16 Mar 2001, Ben Hyatt wrote:
So, in source /usr/local/src/amanda-2.4.1p1/example/config.site
add the CFLAGS entry, run configure and rebuild? (make clean, make make
install)
here's how i do it (for amanda, and similarly for other packages)...
mkdir /usr/local/src/amanda
mkdir /usr/local/src/amanda/2.4.2p1
create /usr/local/src/amanda/2.4.2p1/Makefile (attached)
create /usr/local/src/amanda/2.4.2p1/config.site (attached)
create /usr/local/src/amanda/2.4.2p1/amanda-2.4.2p1.tar.gz (distribution)
cd /usr/local/src/amanda/2.4.2p1
make ! 0-make-log
then you have a record of exactly how you configured and built amanda-X in
the Makefile and config.site. to rebuild at any time, just make again.
it's a very easy way to maintain local builds of software packages.
--
Todd Pfaff \ Email: [EMAIL PROTECTED]
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University \
Hamilton, Ontario, Canada L8S 4M1 \
PACKAGE=amanda
VERSION=2.4.1p1
RELEASE=${PACKAGE}-${VERSION}
SHELL=/bin/sh
CONFIG_SITE=/usr/local/src/amanda/${VERSION}/config.site
#all: clean unpack patch build-client build-server install-client install-server
server: clean unpack patch build-server
client: clean unpack patch build-client
clean:
/bin/rm -rf ${RELEASE}
unpack:
umask 022;\
gnutar zxf ${RELEASE}.tar.gz;\
chown -R 0.0 ${RELEASE}
patch:
umask 022;\
patch -p0 -t patches/samba2-2418.diff
build-client:
umask 022;\
cd ${RELEASE};\
CONFIG_SITE=$(CONFIG_SITE); export CONFIG_SITE;\
./configure \
--without-server \
;\
make
build-server:
umask 022;\
cd ${RELEASE};\
CONFIG_SITE=$(CONFIG_SITE); export CONFIG_SITE;\
./configure \
;\
make
install-client:
umask 022;\
cd ${RELEASE};\
make install;\
cd /usr/local/amanda/lib;\
ln -s libamanda-2.4.1p1.so.0.0.0 libamanda-2.4.1p1.so;\
ln -s libamclient-2.4.1p1.so.0.0.0 libamclient-2.4.1p1.so;\
ln -s libamserver-2.4.1p1.so.0.0.0 libamserver-2.4.1p1.so;\
ln -s libamtape-2.4.1p1.so.0.0.0 libamtape-2.4.1p1.so;\
mkdir -p /usr/local/amanda/etc/gnutar-lists;\
chown backup.backup /usr/local/amanda/etc/gnutar-lists
install-server: install-client
install: install-client
# see srcdir/examples/config.site for details
CC=cc
CFLAGS=-DIGNORE_SMBCLIENT_ERRORS
sbindir=$prefix/bin
CONFIG_DIR=$prefix/etc
DEFAULT_SERVER=amandahost
FORCE_USERID=yes
CLIENT_LOGIN=backup
SETUID_GROUP=backup
USE_RUNDUMP=yes
SAMBA_CLIENT=/usr/local/samba/bin/smbclient
GNUTAR=$prefix/libexec/gnutar
GNUTAR_LISTDIR=$CONFIG_DIR/gnutar-lists
BSD_SECURITY=yes
USE_AMANDAHOSTS=yes
RE: amanda mail report size
On Thu, 15 Mar 2001, Ben Hyatt wrote:
I have 8 samba shares which get backed up - due to open files I get a lot
of errors from samba.
I added 2 samba shares to the disklist (previous instance had 6 samba shares
defined) my previous reports were never this big.
you can patch amanda to be less verbose when samba (or other) errors are
encountered. you only need to do this on the samba client that is the
host for the smbclient backups. that is, if your disklist looks like:
host1 //pchost/driveC comp-user-tar
host1 //pchost/driveD comp-user-tar
host2 / comp-user
you only need to patch amanda for host1.
there are two patches you can apply that affect two different aspects of
the smbclient backup.
1) client-src/sendbackup-gnutar.c
look for this code segment:
#ifdef IGNORE_SMBCLIENT_ERRORS
/* This will cause amanda to ignore real errors, but that may be
* unavoidable when you're backing up system disks. It seems to be
* a safe thing to do if you know what you're doing. */
{ DMP_NORMAL, "^ERRDOS - ERRbadshare opening remote file", 1},
{ DMP_NORMAL, "^ERRDOS - ERRbadfile opening remote file", 1},
{ DMP_NORMAL, "^ERRDOS - ERRnoaccess opening remote file", 1},
{ DMP_NORMAL, "^ERRSRV - ERRaccess setting attributes on file", 1},
{ DMP_NORMAL, "^ERRDOS - ERRnoaccess setting attributes on file", 1},
#endif
if you define IGNORE_SMBCLIENT_ERRORS then these smbclient error messages
will be treated as DMP_NORMAL and they will not cause a full error report
to be generated (ie. amanda will output all messages from the dump if any
non-DMP_NORMAL lines are detected. this is the problem you are seeing.).
you can define IGNORE_SMBCLIENT_ERRORS in your configure stage by, for
example, putting the following in config.site:
CFLAGS=-DIGNORE_SMBCLIENT_ERRORS
2) if you don't care to see any DMP_NORMAL lines in the report, only
DMP_STRANGE lines, look at client-src/sendbackup.c for this code:
typ = parse_dumpline(str);
switch(typ) {
case DMP_NORMAL:
case DMP_SIZE:
startchr = '|';
break;
default:
case DMP_STRANGE:
startchr = '?';
break;
}
fprintf(stderr, "%c %s\n", startchr, str);
and add a "return" statement after the "case DMP_NORMAL" line:
case DMP_NORMAL:
return;
so that the fprintf is not called for DMP_NORMAL lines. the downside to
this is that you will not see any of the possibly useful DMP_NORMAL
information when there is a DMP_STRANGE error. this could make debugging
the problem more difficult. it would be useful if this was a run-time
configurable feature.
--
Todd Pfaff \ Email: [EMAIL PROTECTED]
Computing and Information Services \ Voice: (905) 525-9140 x22920
ABB 132 \ FAX: (905) 528-3773
McMaster University \
Hamilton, Ontario, Canada L8S 4M1 \
RE: Samba/Win2k/RH7.0/Amanda
try this... - edit your disklist file and comment out everything except one of the smbclient backup entries - run amdump - look at the debug files in /tmp/amanda/ (i'm not sure which one, maybe sendbackup.debug, maybe rundump.debug) you should see the smbclient command line in there. try to run that same command line manually. On Mon, 26 Feb 2001, Holm-Hansen wrote: Date: Mon, 26 Feb 2001 14:29:19 -0600 From: Holm-Hansen [EMAIL PROTECTED] To: jrj [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: amanda-users [EMAIL PROTECTED] Subject: RE: Samba/Win2k/RH7.0/Amanda smbclient is able to connect via command line and to list the contents of the w2k box. amcheck reports that: ERROR: 192.168.1.10: [PC SHARE //win2kbox/C$ access error: host down or invalid password?] Client check: 1 host checked in 0.822 seconds, 1 problem found I checked and rechecked amandapass and my winbox's passwords. Since I can smbclient to the winbox with the username amanda and password that I have set in amandapass I assume that this is not the problem. the selfcheck.debug file is as follows: selfcheck: debug 1 pid 22058 ruid 505 euid 505 start time Fri Feb 23 17:07:37 2001 /usr/local/libexec/selfcheck: version 2.4.2p1 checking disk /usr/local: device /usr/local: OK checking disk /u1: device /u1: OK checking disk /root: device /root: OK checking disk /boot: device /boot: OK checking disk /etc: device /etc: OK checking disk /home: device /home: OK selfcheck: pid 22058 finish time Fri Feb 23 17:07:38 2001 I don't know if it's supposed to list the samba connection here. Also, I can use smbmount to mount the win2k partition onto the linux filesystem tree and back it up that way. I don't know if this is a good solution. Are there problems with this? Thanks again. Andrew = Original Message From [EMAIL PROTECTED] = In addition to John Verify that you can use smbclient via command-line to connect and list the contents on the Win2K box. Snippet: Before our NT Admins started using Veritas to backup the Windoze machines I tested amanda under a multi-domain setup PROD and DEV. I had a problem connecting to the SHARE by name //machine/sharename. I could not authenticate using the DEV amanda - user:"backup" password:"I forget" or even as myself(Domain Admin) under the DEV domain in which the machine was bound and all the permissions seemed OK. Although under my PROD(Domain Admin) login I could connect to the SHARE list the contents. In short: Ran out of time to figure it out but if you get smbclient working command line with the logins for amanda.. Amanda will work. Bob --- "John R. Jackson" [EMAIL PROTECTED] wrote: I don't know if there are logs elsewhere that contain more information about the problem. What's in /tmp/amanda/selfcheck*debug? Andrew John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/ -- Todd Pfaff \ Email: [EMAIL PROTECTED] Computing and Information Services \ Voice: (905) 525-9140 x22920 ABB 132 \ FAX: (905) 528-3773 McMaster University \ Hamilton, Ontario, Canada L8S 4M1 \
