SMB-Share: ERRnoaccess
Dear reader, I try to integrate an smb share hosted on an amanda client. After amcheck DailySet1 I find in amandad.debug: ... amandad: running service "/usr/local/libexec/selfcheck" added interface ip= ...[snip] ... Anonymous login successful Domain=[BERLIN] OS=[Windows NT 4.0] Server=[NT LAN Manager 4.0] tree connect failed: ERRDOS - ERRnoaccess (Access denied.) amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-484A0508 SEQ 982164839 OPTIONS ; running /usr/bin/smbclient ntbox\\TestDir -E -U (see amandapass) -c quit ERROR [PC SHARE //ntbox/TestDir access error: host down or invalid password?] OK /home/oracle OK /sbin/dump executable OK /sbin/restore executable OK /bin/gtar executable OK /etc/amandates read/writable OK /usr/local/var/amanda/gnutar-lists/. read/writable OK /usr/bin/smbclient executable OK [/etc/amandapass is readable, but not by all] OK /usr/bin/gzip executable OK /etc/dumpdates read/writable OK /dev/null read/writable OK /tmp/amanda has more than 64 KB available. OK /var/adm/amanda has more than 64 KB available. OK /etc has more than 64 KB available. ... Is there something missconfigured during installing amanda? I miss the password phrase in /usr/bin/smbclient ntbox\\TestDir -E -U (see amandapass) -c quit If I try /usr/bin/smbclient ntbox\\TestDir PASSWD -E -U AMANDAUSER -c quit with PASSWORD defined in /etc/amandapass and AMANDAUSER used in --with-user=... at config time it works. Any idea? Thank you mike
dump problem on SCO OpenServer client?
I got the following in the sendsize.debug file on a SCO OpenServer client. Am I correct in assuming that the version of dump on SCO OpenServer is not what is expected? Do I need to grab a GNU version? It seems like most people are backing up Linux or Sun boxes. Has anyone out there had any luck with backing up SCO clients? sendsize: debug 1 pid 25302 ruid 3005 euid 3005 start time Tue Feb 13 21:01:02 2 001 /usr/local/libexec/sendsize: version 2.4.2p1 calculating for amname '/dev/rroot', dirname '/dev/rroot' sendsize: getting size via dump for /dev/rroot level 0 sendsize: running "/bin/dump 0Esf 1048576 - /dev/rroot" running /usr/local/libexec/killpgrp Usage: dump [-?CDVcgl -L[v] -a[v] -f[v] -h[dnv] -o[v] -r[dnv] -s[dnv] -t[nv] -T index1[, index2]] file(s) ... . (no size line match in above dump output) . asking killpgrp to terminate sendsize: pid 25302 finish time Tue Feb 13 21:01:03 2001 Erick Bodine Xpedite Systems Inc Boulder CO
Re: Listing tape content
Joseph Del Corso wrote: I was just curious if there was a way, and if so what the command line syntax (linux) was to do it, to see a list of the files/directories, space used, etc, by a dump. You can use amtoc to parse your latest logfile: $ amtoc be/log/log.20010214.0 # Server:/partition date level size[Kb] 0 BE15: 20010214 - - 1 ente:/mp3/2 20010214 1 30 2 james:/boot 20010214 1 17 3 apollo:/ 20010214 1 64 [...] 33 total:on_tape - - 3184960 33 total:origin - - 3190101 Specifically is there a way to see how much space was used by a dump cycle, and to see what files went into $ amadmin be balance due-date #fs orig KBout KB balance --- 2/14 Wed2 2442825 2442848 -14.9% 2/15 Thu1 2966448 2966464+3.3% 2/16 Fri8 2659673 2630880-8.4% 2/17 Sat3 2525887 2525920 -12.1% 2/18 Sun4 2718537 2718592-5.3% 2/19 Mon1 2765636 2765632-3.7% 2/20 Tue2 3663590 3663616 +27.6% 2/21 Wed2 3444650 3444672 +19.9% 2/22 Thu5 2854480 2852672-0.7% 2/23 Fri5 2709900 2710016-5.6% --- TOTAL 33 28751626 28721312 2872131 (estimated 10 runs per dumpcycle) the dump. Can I just do a mount on the tape devices (after putting the device in /etc/fstab) ? or is there some kind of mt, or other, command that will show me the contents of a tape? No, you can't mount tapes. They're just read-/writeable like a terminal (character device) but you can't read or write a random block like on a disc (block device). To store files and directories on them, you have to put your file system or your subdirectory into a single data stream. That's what dump and tar are for (tar = tape archive). To scan the contents of a tape, you can use amrecover: # amrecover $TAPE no-such-host It will print the dump/tar images residing on the tape.
Webbased backup overview
Please find attached a small perl script I wrote today. It parses the output of amadmin config find and generates an html page out of the result listing for the last 7 days the dump results for all disks that amadmin find is able to locate. It uses the Date::Calc perl module available from CPAN (or your linux distro ;) ). It's decidedly *NOT* fancy but it fulfills a need . (the only fancy thing it does is mark level 0 dumps as bold, and failed dumps in red, so that you can see in one glimps whether there was a 0dump in your last dump cycle. Usage: amadmin config find | backupstart.pl output.html konqueror output.html (or netscape or ...) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O With judicious application of shaving foam water =`\, and scraping with a razor of it's prickly hind quarters (=)/(=) Whether it wriggles like fury, or curls up in a ball That blasted hedgepod can be buggered for sure. backupstats.pl
Bad pattern match on disklist
Using Solaris 8 based server, amanda_2.4.1p1. Same results appear with Solaris 2.5.1 based server. Summary: amrestore and amadmin act on the wrong filesystem when the disklist mount point is a substring of another mountpoint. Is this a bug with the disklist pattern matching? Background: From amanda(8), describing the disklist: diskdevice The name of the disk device to be backed up. It may be a full device name, a device name without the /dev/ prefix, e.g. sd0a, or a mount point such as /usr. ^^ Hence, I should be able to use / /var /export/home /export/home1 /export/home2 : /export/homeN My "ssm1" disklist: hostx / comp-user hostx /varcomp-user hostx /export/home2 comp-user hostx /export/home3 comp-high hostx /export/home4 comp-high All are unique filesystems on hostx. The amdump using dump (ufsdump on Soalris) works fine. But odd behavior with amadmin and amrestore occurs when the mount point is a substring of other mount points. e.g.: amadmin ssm1 info hostx / Current info for hostx /export/home4: : Current info for hostx /export/home3: : Current info for hostx /export/home2: : Current info for hostx /var: : Current info for hostx /: Why am I getting information about filesystems other than "/"? The worst behavior is doing a restore. If I want to restore, and the tape holds another file system first, I will restore from the mismatched system first (e.g., I want to amrestore "/", but /export/home4 appears on the tape first). Is this a bug with the pattern matching? It's as if the pattern match is like a "grep" instead of an exact match on the mount point. I looked in the server-src source, but could not find it. Mario Obejas Engineering Automation Computing Raytheon Electronic Systems 310-334-7201 (Voice) 310-366-4867 (Pager)
Re: Configuration question
Would it be feasable to do one of the following two things: Keep the the old files in a diferent directory and only backup certain directories. Or possable gzip the old ones so that they arent so large. I usually find that gzip will compress dumped database files to 10x smaller than they were. or Just use amanda like it normally does things and it will only backup ones that it does not allready have. If you have to keep the databases that are x days old then every 10 days it would back all of them up and you would not have to wory about overwriting your old tapes with new ones. That way you would always have one of every database on tapes and one on the partition. Regards, Ryan Williams - Original Message - From: "Wood, David" [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, February 14, 2001 8:46 PM Subject: Configuration question Hi, I have a filesystem "/sybase_dumps". Each night a script dumps Sybase databases to this filesystem and the files are quite large. There is a purge script which cleans out the filesystem of files more than X days old - we need to keep X days worth of dump files on-line. Basically, I only want Amanda to backup new dump files (as much as possible) within this filesystem. Does anyone have advice on how to configure Amanda for this filesystem? I've thought about using the 'incronly' strategy; however, the usefulness of this strategy breaks down when dump levels reach 9. I've thought about switching to GNUTAR and tinkering with the source to have DUMP_LEVELS = 2147483647 (size of int); however, I'm afraid of breaking other parts of the code (will I?). I imagine the bump parameters are going to give me grief too. Thanks for any advice ... David
Re: Listing tape content
On Feb 14, 2001, "Bernhard R. Erdmann" [EMAIL PROTECTED] wrote:
To scan the contents of a tape, you can use amrecover:
# amrecover $TAPE no-such-host
s/amrecover/amrestore/
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: Bad pattern match on disklist
On Feb 15, 2001, Mario Obejas [EMAIL PROTECTED] wrote:
amadmin ssm1 info hostx /
See `man amdmin'. disk is a regular expression in 2.4.1p1; use `/$'.
In 2.4.2, a new pattern matching scheme was introduced. `/' should no
longer match other disks in 2.4.2.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
broken pipe
Hi!
At first i installed amanda for a long time on a tape server and amanda works
fine.
After insatlling amanda on a client i have this problems.
---Begin Amanda Mail
These dumps were to tapes Daily01, Daily02.
Tonight's dumps should go onto 2 tapes: Daily03, Daily04.
FAILURE AND STRANGE DUMP SUMMARY:
fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
fileserver sdc1 lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:10
Run Time (hrs:min) 3:45
Dump Time (hrs:min)2:41 2:41 0:00
Output Size (meg) 44392.544392.50.0
Original Size (meg) 44392.544392.50.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped4 4 0
Avg Dump Rate (k/s) 4713.1 4713.1--
Tape Time (hrs:min)2:41 2:41 0:00
Tape Size (meg) 44392.644392.60.0
Tape Used (%) 111.0 111.00.0
Filesystems Taped 4 4 0
Avg Tp Write Rate (k/s) 4710.0 4710.0--
FAILED AND STRANGE DUMP DETAILS:
/-- fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
sendbackup: start [fileserver:sdc1 level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 0 dump: Thu Feb 15 04:14:16 2001
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/sdc1 (/drive/drive3) to standard output
| DUMP: Label: none
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 13086232 tape blocks.
| DUMP: Volume 1 started at: Thu Feb 15 04:14:58 2001
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 10.23% done, finished in 0:43
| DUMP: 21.75% done, finished in 0:35
| DUMP: 33.32% done, finished in 0:30
| DUMP: 44.95% done, finished in 0:24
| DUMP: 57.16% done, finished in 0:18
| DUMP: 68.34% done, finished in 0:13
| DUMP: 80.59% done, finished in 0:0
\
NOTES:
taper: tape Daily01 kb 44245472 fm 4 writing file: No space left on device
taper: retrying fileserver:sdc1.0 on new tape: [writing file: No space left
on device]
taper: tape Daily02 kb 13135584 fm 1 [OK]
-- End Message from Amanda
Whats the problem of amanda?
Bye Juergen
Re: broken pipe
On Feb 15, 2001, Juergen Knott [EMAIL PROTECTED] wrote:
fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"]
fileserver sdc1 lev 0 FAILED [dump to tape failed]
[snip]
taper: tape Daily01 kb 44245472 fm 4 writing file: No space left on device
Looks like tape full.
taper: tape Daily02 kb 13135584 fm 1 [OK]
Looks like Amanda recovered correctly, restarting the dump in the
following tape.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: broken pipe
Am Donnerstag, 15. Februar 2001 08:40 schrieben Sie: On Feb 15, 2001, Juergen Knott [EMAIL PROTECTED] wrote: fileserver sdc1 lev 0 FAILED ["data write: Broken pipe"] fileserver sdc1 lev 0 FAILED [dump to tape failed] [snip] taper: tape Daily01 kb 44245472 fm 4 writing file: No space left on device Looks like tape full. Ok, the tape is full, taper: tape Daily02 kb 13135584 fm 1 [OK] Looks like Amanda recovered correctly, restarting the dump in the following tape. and used the next tape. Also the backup is finnished correctly? Bye Juergen -- Dies ist eine Microsoft freie Mail!
access as amanda not allowed from amanda@foo.sys.si.tlan] amandahostsauth failed
Banzai! I get the above message when trying to backup one specific host. Client and server are bot v2.4.2 and if I do amcheck as root then everything works fine, if I do it as user amanda, then it fails. I have users root and amanda in .amandahosts. Any ideas what could be wrong? Thanks, -- David Klasinc Turbolinux Inc. http://www.turbolinux.com
Re: broken pipe
On Feb 15, 2001, Juergen Knott [EMAIL PROTECTED] wrote:
Also the backup is finnished correctly?
I'd guess so, but you didn't post the part of the report that says
which dumps made to which tape, so I can't tell for sure.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicampoliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist*Please* write to mailing lists, not to me
Re: access as amanda not allowed from amanda@foo.sys.si.tlan] amandahostsauth failed
* David Klasinc [EMAIL PROTECTED] (Thu, Feb 15, 2001 at 08:53:33AM +0100) Banzai! I get the above message when trying to backup one specific host. Client and You get a message saying Banzai ! Did you install the WWII - japanese slang add-on to Amanda ? [Just kidding] server are bot v2.4.2 and if I do amcheck as root then everything works fine, if I do it as user amanda, then it fails. I have users root and amanda in ..amandahosts. Any ideas what could be wrong? Ehm do you have the .amandahosts in user amandas homedir ? or only in roots homedir ? The amanda FAQ (docs/FAQ in the source tree) sez this Q: Why does `amcheck' say `access as username not allowed...' A: There must be something wrong with .amandahosts configuration (or .rhosts, if you have configured --without-amandahosts). First, if the username is not what you expect (i.e., not what you have specified in the --with-user flag, at configure time), check the inetd configuration file: you must have specified the wrong username there. Make sure you specify the names exactly as they appear in the error message after the `@' sign in .amandahosts/.rhosts. You'll need a fully-qualified domain name or not, depending on how your client resolves IP addresses to host names. HTH Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Also by the time I'm 60, I want to get better at the art of living. =`\, And still be riding an acoustic motorbike. (=)/(=) -- not exactly Mark Knopfler
