can not connect
Dear all, When I use the amcheck, I have the following errors. I use the RPMs by Redhat 7.0. In my /etc/amanda/DailySet1/amanda.conf, I use tapedev "/dev/nst0" my tape drive is HP DAT 3. Can anyone tell me what is wrong? Yours, Richard Ao [root@ns31 sbin]# ./amcheck DailySet1Amanda Tape Server Host Check-/var/tmp: 26421008 KB disk space available, that's plenty.ERROR: cannot overwrite active tape DailySet100. (expecting a new tape)NOTE: skipping tape-writable test.Server check took 3.354 seconds.protocol packet receive: Connection refusedprotocol packet receive: Connection refusedprotocol packet receive: Connection refused Amanda Backup Client Hosts CheckWARNING: localhost: selfcheck request timed out. Host down?Client check: 1 host checked in 29.996 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1)
Re: problem with amdump
Vinche wrote: fatboy /lib lev 0 FAILED [Request to fatboy timed out.] I suspect the estimates took too long. Increase etimeout in amanda.conf. planner: Last full dump of fatboy:/usr/apache/archive on tape DailySet107 overwritten on this run. Either you demand full backups too often, or use too few tapes (which is actually an equivalent way of saying the same thing). Increase dumpcycle in amanda.conf and/or use more tapes. -- Regards Chris Karakas Dont waste your cpu time - crack rc5: http://www.distributed.net
Re: amanda to blame for NT crashes?
[EMAIL PROTECTED] said: Any more ideas now? How can this "ATTR_ARCH" flag be reasonably used here? The ATTR_ARCH flag doesn't get mapped to any standard Unix flag. Mapping it to the executable flag would be very strange. ext2 provides an ioctl() call which lsattr uses to get/set extended ext2-specific flags. You could implement a similar call for the fat-based filesystems, and add support in Amanda for using it to query (and later reset) the state of the ATTR_ARCH bit. -- dwmw2
Re: amanda to blame for NT crashes?
Have you tried fiddling with the tcp flags in /etc/smb.conf? Perhaps some settings cause odd behaviour more than some.
Re: can not connect
Hi, did you read the message I posted yesterday regarding installing amanda on RH7.0 machines If not send me and E-mail and I will forward it to you!!! Bye, Antonino Casile richard wrote: Dear all, When I use the amcheck, I have the following errors. I use the RPMs by Redhat 7.0. In my /etc/amanda/DailySet1/amanda.conf, I use tapedev "/dev/nst0" my tape drive is HP DAT 3. Can anyone tell me what is wrong? Yours, Richard Ao [root@ns31 sbin]# ./amcheck DailySet1 Amanda Tape Server Host Check - /var/tmp: 26421008 KB disk space available, that's plenty. ERROR: cannot overwrite active tape DailySet100. (expecting a new tape) NOTE: skipping tape-writable test. Server check took 3.354 seconds. protocol packet receive: Connection refused protocol packet receive: Connection refused protocol packet receive: Connection refused Amanda Backup Client Hosts Check WARNING: localhost: selfcheck request timed out. Host down? Client check: 1 host checked in 29.996 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1)
missing file header
Hi, i have a problem. When I want to restore my backup to the harddisk, i get the message: missing file header. I started recovering with following commands amrecover and amrestore, but i get the same error. Please help me, the amanda server must run. many thanks for your help. Roshan amidxtaped.debug: amidxtaped: debug 1 pid 740 ruid 37 euid 37 start time Tue Dec 5 17:03:19 2000 amidxtaped: version 2.4.2 SECURITY USER amanda bsd security: remote host amanda1.popken.de user amanda local user amanda amandahosts security check passed 6 amrestore_nargs=6 -h -p /dev/nst0 amanda1 ^/usr$ 20001205 Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = "amrestore" argv[1] = "-h" argv[2] = "-p" argv[3] = "/dev/nst0" argv[4] = "amanda1" argv[5] = "^/usr$" argv[6] = "20001205" amrestore: 0: skipping start of tape: date 20001205 label VOL8 amrestore: missing file header block amrestore: 1: reached end of tape: date 20001205 amidxtaped: amrestore terminated normally with status: 1 Rewinding tape: done amidxtaped: pid 740 finish time Tue Dec 5 17:03:23 2000
Re: 'exclude' with samba-backups
Eric Wadsworth [EMAIL PROTECTED] wrote: I'm just starting out, but I understood that excludes didn't work with samba shares when using GNUTAR. I've been working around that limitation, AFAIK exclude works with samba in 2.4.2 but didn't work in 2.4.1p1. The results of my backups verify this. certainly open to suggestions... if the excludes actually work on samba shares, let me know! As said above they seem to work, but I can use only one expression for exclusion per share; I wasn't successful in trying to exclude more than one expression, neither by exclude-file, nor by a list of expressions. Regards, Lipo -- Roland E. Lipovits Vienna, Austria
Re: Why no reports? (fwd)
This was it! This installs the patch! Thanks so much. Tomorrow we'll see if this patch solved the huge report problem. My latest report was 24 megs in size! The emailer doesn't handle it very well. :) Eric Eric Wadsworth [EMAIL PROTECTED] wrote: I'm using samba version 2.0.6 on a FreeBSD machine. Using amanda 2.4.1p1 right now, and I dropped the samba 2 patch into the 'files' directory of the FreeBSD ports skeleton, but I don't know how to tell if the patch actually made it in, as the patch modified the configure command itself. I've added these three lines to /usr/ports/misc/amanda24/Makefile (after the DISTNAME= line): PATCH_SITES=http://www.amanda.org/patches/2.4.1p1/ PATCHFILES= samba2-2418.diff PATCH_DIST_STRIP= -p1 and added a line to /usr/ports/misc/amanda24/distinfo too (in the old ports layout this was /usr/ports/misc/amanda24/files/md5 IIRC): MD5 (samba2-2418.diff) = 6a66c8750a4ebeed1de7f43613035c7f HTH Lipo -- Roland E. Lipovits Vienna, Austria === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
Re: 'exclude' with samba-backups
On 5 Dec 2000, Roland E. Lipovits wrote: Eric Wadsworth [EMAIL PROTECTED] wrote: I'm just starting out, but I understood that excludes didn't work with samba shares when using GNUTAR. I've been working around that limitation, AFAIK exclude works with samba in 2.4.2 but didn't work in 2.4.1p1. The results of my backups verify this. Hmmm... Right now I'm using 2.4.1p1 and I'll probably continue using it until 2.4.2 is added to the FreeBSD ports collection. certainly open to suggestions... if the excludes actually work on samba shares, let me know! As said above they seem to work, but I can use only one expression for exclusion per share; I wasn't successful in trying to exclude more than one expression, neither by exclude-file, nor by a list of expressions. That's annoying. If you discover a way to exclude multiple directories, let me know. Then I'll probably make the jump over 2.4.2 at that time. --- Eric Regards, Lipo -- Roland E. Lipovits Vienna, Austria
Re: amanda to blame for NT crashes?
On Dec 5, 2000, Chris Karakas [EMAIL PROTECTED] wrote:
according to David Woodhouse [EMAIL PROTECTED] in the
linux-kernel mailing list:
Hi, David! :-)
---snip
We do, however, correctly set the archive bit whenever we modify or
create a file on a FAT filesystem, so it should be usable for its
intended purpose.
You just need to make sure your backup program uses the ATTR_ARCH
flags to decide whether to back up each file, and resets the flag
after/before doing the backup.
---snip
Any more ideas now? How can this "ATTR_ARCH" flag be reasonably used
here?
Hmm... You'd have to try to get GNU tar and/or Samba to reasonably
use these flags. Maybe their maintainers would be willing to help you
out?
--
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: Huge incrementals on all samba shares?
On Dec 5, 2000, Eric Wadsworth [EMAIL PROTECTED] wrote:
Amanda has now run 4 times on my network. The past three times it
has included samba shares for various NT workstations. Why are the
incrementals so huge on these?
One of the possible reasons: if the username with which you access the
SMB server doesn't have permission to change attributes of files, it
won't be able to remove the `archive' flag, that is used to decide
whether to include a file in an incremental backup or not.
--
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: Huge incrementals on all samba shares?
Wow, I think that's it. I made a backup user with "Read-only" permissions on all of the NT machines. Yay! I'm off to change a bunch of backup user setting on a bunch of people's NT boxes now Thanks! --- Eric Alexandre Oliva wrote: On Dec 5, 2000, Eric Wadsworth [EMAIL PROTECTED] wrote: Amanda has now run 4 times on my network. The past three times it has included samba shares for various NT workstations. Why are the incrementals so huge on these? One of the possible reasons: if the username with which you access the SMB server doesn't have permission to change attributes of files, it won't be able to remove the `archive' flag, that is used to decide whether to include a file in an incremental backup or not. === Eric Wadsworthemail: [EMAIL PROTECTED] Conceptual Systems and Software http://www.consys.com ===
Re: 'exclude' with samba-backups
I'm just starting out, but I understood that excludes didn't work with samba shares when using GNUTAR. I've been working around that limitation, when possible, by sharing only the directories that need to be backed up. This has obvious flaws, of course. For example, most of the NT systems don't have the hard drives organized to make this simple, so the whole mess gets backed up, including: * NT swap file * Operating system files * web browser caches * application files All of these things are just a waste of time and space to back up. I'm certainly open to suggestions... if the excludes actually work on samba shares, let me know! --- Eric On 5 Dec 2000, Roland E. Lipovits wrote: I'm using samba-backups with an exclude-statement (specified in the disklist-file). As far as I read from the files in /tmp/amanda the exlusion is only used when backuping, not when estimating. Bug or feature? (BTW: amanda-2.4.2) Regards, Lipo -- Roland E. Lipovits Vienna, Austria
Re: 'exclude' with samba-backups
On Tue, Dec 05, 2000 at 04:08:03AM +0100, Roland E. Lipovits wrote: I'm using samba-backups with an exclude-statement (specified in the disklist-file). As far as I read from the files in /tmp/amanda the exlusion is only used when backuping, not when estimating. Bug or feature? (BTW: amanda-2.4.2) amanda-2.4.2 use the 'du' command of smbclient to get the estimate. This command doesn't understand exclude. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Frusturating problem with amcheck
I've been playing with this for over a day now and still havent got it so that it's working all the time.. I dont even know where to go from here... except using this tape backup server for target practice... if anybody could give me a hand, even just a hint as to why this isnt working, i would really appreciate it... The most frusturating thing about this problem is that it's intermittent.. sometimes the check goes through fine, other times I got the error "selfcheck request timed out". There was nothing specific to my situation in the faq-o-matic, this is what I'm getting in my /tmp/amanda/amanda.debug: amandahosts security check passed amandad: running service "/opt/amanda/libexec/selfcheck" amandad: error receiving message: Connection refused however, the selfcheck.debug file says that everything ran fine: selfcheck: debug 1 pid 14527 ruid 34 euid 34 start time Tue Dec 5 10:22:08 2000 /opt/amanda/libexec/selfcheck: version 2.4.1p1 checking disk sdb1: device /dev/sdb1: OK checking disk sda3: device /dev/sda3: OK checking disk sda2: device /dev/sda2: OK checking disk sda1: device /dev/sda1: OK selfcheck: pid 14527 finish time Tue Dec 5 10:22:08 2000
GDB of chg-scsi
OK, all you C gurus out there... This GDB was configured as "sparc-sun-solaris2.8"... (gdb) set args -info (gdb) run Starting program: /usr/src/amanda-2.4.2/changer-src/chg-scsi -info warning: Lowest section in /usr/lib/libintl.so.1 is .hash at 0x74 Program received signal SIGSEGV, Segmentation fault. 0xff132e5c in strlen () from /usr/lib/libc.so.1 (gdb) step Single stepping until exit from function strlen, which has no line number information. Program terminated with signal SIGSEGV, Segmentation fault. The program no longer exists. (gdb) So where do I go from here... --- Mike Taylor Coordinator of Systems Administration and Network Security Indiana State University. Rankin Hall Rm 039 210 N 7th St. Terre Haute, IN. Voice: 812-237-8843 47809 --- "You have zero privacy anyway. Get over it." --Scott McNealy, Sun MicroSystems.
Re: problem with amdump
I suspect the estimates took too long. ... Take a look at the first and last lines of sendsize*debug on fatboy. They will tell you how long the estimate took. Amanda defaults to five minutes per disk. Do the math and see if that is long enough. I'm doing full backups every day since I couldn't get /opt/amandahold work as holding disk for long time also because of timeout. ... fatboy /opt/amandahold lev 0 FAILED [disk /opt/amandahold offline on fatboy?] First, why are you trying to back up the holding disk? If that's all that's in there, it's basically scratch space for Amanda and should not be part of the normal backups. Is it a file system all by itself? Or is it part of /opt? Second, that message says nothing about a timeout. It says the backup program Amanda tried to run (are you using dump or GNU tar?) could not do the job for some reason. To find out why, you need to look at the sendsize*debug or sendbackup*debug files on the client (fatboy). Or run amcheck -- it may have had something interesting to say. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: missing file header
... When I want to restore my backup to the harddisk, i get the message: missing file header. ... What happens if you do this: $ mt -f /dev/nst0 rewind $ amrestore no-such-host What about this: $ mt -f /dev/nst0 rewind $ mt -f /dev/nst0 fsf 1 $ amrestore no-such-host What operating system are you using? What kind of tape drive? Roshan John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Rebuilt Tape Server
Hello, We recently had a hard-disk failure on our tape backup server. And while I was rebuilding the system I decided to upgrade the OS from RedHat 5, to RedHat 7.0. And it has version 2.4.1p1 of Amanda installed. I copied all the configuration files over from the old install. And when I run amcheck I receive this: --[snip]-- [backup@sol backup]$ /usr/sbin/amcheck DailySet1 Amanda Tape Server Host Check - /holding-disk/dumps/amanda: 26478440 KB disk space available, that's plenty. NOTE: skipping tape-writable test. Tape Dailydumps1 label ok. Server check took 27.733 seconds. protocol packet receive: Connection refused protocol packet receive: Connection refused protocol packet receive: Connection refused Amanda Backup Client Hosts Check WARNING: sol: selfcheck request timed out. Host down? Client check: 5 hosts checked in 29.644 seconds, 1 problem found. (brought to you by Amanda 2.4.1p1) --[snip]-- Whey would it be saying connection refused? I have checked the xinted file for amandaidx and amidxtape, and they both appear to be correct. Any ideas? Thanks. .~. /v\ -- // \\ JA /( )\ ^`~`^ L I N U X [---] Justin Ainsworth PHONE: (530) 879-5660x108 System Administrator FAX: (530) 879-5676Sunset Net LLC WEB: http://www.sunset.net 1915 Mangrove Ave EMAIL: [EMAIL PROTECTED] Chico, CA 95926 [---]
Re: CHG-SCSI
This is all on a Sun E3500 with Solaris 8. devfsadm: driver failed to attach: sst Warning: Driver (sst) successfully added to system but failed to attach Are you running a 64 bit kernel? Did you compile sst for 64 bit? I don't know that that's the problem, it's just the only thing I can think of. note however, that even tho they are in the devlinks.tab that the links for sst and jb are not being created. That probably won't happen until the drives can get themselves loaded properly once. Of course I get the: /usr/local/libexec/chg-scsi -info Segmentation Fault (core dumped) I think this is just some simple bad code (as compared with complex bad code :-) that is not expecting the device open to fail, or something down that path. Yes, it should be fixed to not do this, but is not your real problem. and I also followed the sgen directions: ... # /usr/src/amanda-2.4.2/contrib/sst/sstest /dev/scsi/changer/c2t10d0 open Device opened Why are you using sstest on the sgen device? I thought sst and sgen used completely different ioctl formats. I thought someone posted intructions on using sgen with chg-scsi in the last month or two. I'd start by searching for sgen. Mike Taylor John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: GNU tar estimates for vfat filesystems (Was: How do I check level 1 sizes?)
Alexandre Oliva wrote: On Dec 1, 2000, Chris Karakas [EMAIL PROTECTED] wrote: Do you mean that just by undefining GNUTAR_LISTED_INCREMENTAL_DIR, AMANDA is going to call tar using --incremental, instead of --listed-incremental? That's right. ... However, you'll still be missing the `--newer' flag, that is passed when GNUTAR_LISTED_INCREMENTAL_DIR is used. You may have to work around this problem by reading/storing timestamps in the `filename' argument. I am in the process of undefining GNUTAR_LISTED_INCREMENTAL_DIR and recompiling. I have had a look at the sources and, as I understand it, the --newer flag is passed *only* when I *don't* use GNUTAR_LISTED_INCREMENTAL_DIR. From client-src/sendsize.c, around line 1220: #ifdef GNUTAR_LISTED_INCREMENTAL_DIR " --listed-incremental ", incrname, #else " --incremental", " --newer ", dumptimestr, #endif So, actually, the --newer flag *will* be passed if I undef GNUTAR_LISTED_INCREMENTAL_DIR and I don't miss anything, do I? -- Regards Chris Karakas Dont waste your cpu time - crack rc5: http://www.distributed.net
Re: GNU tar estimates for vfat filesystems (Was: How do I check level 1 sizes?)
I am in the process of undefining GNUTAR_LISTED_INCREMENTAL_DIR and recompiling. ... I think (but am not 100% certain) you can do this when you ./configure by adding --without-gnutar-listdir. Make sure you do a "make distclean" before re-running ./configure. Check config/config.h for GNUTAR_LISTED_INCREMENTAL_DIR after running ./configure to see if it's defined or not for this (re)build. Chris Karakas John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: GDB of chg-scsi
Thanks, I have moved on from there. When I saw the strlen I decided it was probably haveing problems with the chg-scsi.conf. Now I am up to: flash:/amanda# /usr/src/amanda-2.4.2/changer-src/chg-scsi -info none drive number error (0 -1) chg-scsi: requested drive number (0) greater than number of supported drives (-1) Here is my chg-scsi.conf number_configs 2 eject 1 # Tapedrives need an eject command sleep 30 # Seconds to wait until the tape gets ready cleanmax10 # How many times could a cleaning tape get used changerdev /dev/rmt/rssta # # Next comes the data for drive 0 # config 0 drivenum0 dev /dev/rmt/0cbn # the device that is used for the startuse0 # The slots associated with the drive 0 enduse 19 # statfile/usr/local/etc/amanda/tape0-slot # The file where the cleancart 20 # the slot where the cleaningcartridge for drive 0 cleanfile /usr/local/etc/amanda/tape0-clean # The file where the usagecount /usr/local/etc/amanda/backup/totaltime tapestatus /usr/local/etc/amanda/DailySet1/tape0-status labelfile /usr/local/etc/amanda/DailySet1/labelfile # Use this if you # Next comes the data for drive 1 config 1 drivenum1 dev /dev/rmt/1cbn # the device that is used for the tapedrive 0 startuse21 # The slots associated with the drive 0 enduse 39 # statfile/usr/local/etc/amanda/tape1-slot # The file where the cleancart 20 # the slot where the cleaningcartridge for drive 0 cleanfile /usr/local/etc/amanda/tape1-clean # The file where the usagecount /usr/local/etc/amanda/backup1/totaltime tapestatus /usr/local/etc/amanda/DailySet1/tape1-status labelfile /usr/local/etc/amanda/DailySet1/labelfile # Use this if you # # This is the end And here is the debug output. chg-scsi: debug 1 pid 18423 ruid 0 euid 0 start time Tue Dec 5 14:31:28 2000 ARG [0] : /usr/src/amanda-2.4.2/changer-src/chg-scsi ARG [1] : -info Number of configurations: 2 Tapes need eject: Yes Tapes need sleep: 30 seconds Cleancycles : 10 Changerdevice : /dev/rmt/rssta Labelfile : /usr/local/etc/amanda/DailySet1/labelfile Tapeconfig Nr: 0 Drivenumber : 0 Startslot : 0 Endslot : 19 Cleanslot : 20 Devicename: /dev/rmt/0cbn changerident : none SCSITapedev : none tapeident : none statfile : /usr/local/etc/amanda/DailySet1/tape0-status Slotfile : /usr/local/etc/amanda/tape0-slot Cleanfile : /usr/local/etc/amanda/tape0-clean Usagecount: /usr/local/etc/amanda/backup/totaltime Tapeconfig Nr: 1 Drivenumber : 1 Startslot : 21 Endslot : 39 Cleanslot : 20 Devicename: /dev/rmt/1cbn changerident : none SCSITapedev : none tapeident : none statfile : /usr/local/etc/amanda/DailySet1/tape1-status Slotfile : /usr/local/etc/amanda/tape1-slot Cleanfile : /usr/local/etc/amanda/tape1-clean Usagecount: /usr/local/etc/amanda/backup1/totaltime # START OpenDevice OpenDevice : /dev/rmt/rssta # START SCSI_Inquiry SCSI_Inquiry start length = 56: # START DecodeSCSI SCSI_ExecuteCommand : INQUIRY 12 00 00 00 38 00 # STOP DecodeSCSI 08 80 02 02 21 00 00 00 53 50 45 43 54 52 41 20SPECTRA. 31 30 30 30 30 20 20 20 20 20 20 20 20 20 20 201... 30 35 30 30 31 35 00 00 00 00 00 00 00 00 00 00050015.. 00 00 00 00 00 00 00 00 SCSI_Inquiry : end 0 # START PrintInquiry qualifier 0 type8 data_format 2 ansi_version2 ecma_version0 iso_version 0 type_modifier 0 removable 1 vendor_info SPECTRA prod_ident 1 prod_version0500 vendor_specific 15 using ident = generic, type = Generic driver tape/robot [generic] # START OpenDevice OpenDevice : /dev/rmt/0cbn # START SCSI_Inquiry SCSI_Inquiry start length = 56: # START DecodeSCSI SCSI_ExecuteCommand : INQUIRY 12 00 00 00 38 00 # STOP DecodeSCSI 01 80 02 02 1F 00 00 30 53 4F 4E 59 20 20 20 20...0SONY 53 44 58 2D 35 30 30 43 20 20 20 20 20 20 20 20SDX.500C 30 31 63 64 00 00 00 00 00 00 00 00 00 00 00 0001cd 00 00 00 00 00 00 00 00 SCSI_Inquiry : end 0 # START PrintInquiry qualifier 0 type1 data_format 2 ansi_version2 ecma_version0 iso_version 0 type_modifier 0 removable 1 vendor_info SONY prod_ident SDX-500C prod_version01cd vendor_specific using ident = generic, type = Generic driver tape/robot [generic] need_eject set to 1 ## START get_drive_count get_drive_count : fd 4 # START GenericElementStatus # START SCSI_ModeSense SCSI_ModeSense start length = 255: # START DecodeSCSI SCSI_ExecuteCommand : MODE SENSE 1A 08 3F 00 FF 00 # STOP DecodeSCSI SCSI_ModeSense end: 0 # START DecodeModeSense 35 00 00 00
Re: GNU tar estimates for vfat filesystems (Was: How do I check level 1 sizes?)
On Dec 5, 2000, Chris Karakas [EMAIL PROTECTED] wrote:
Alexandre Oliva wrote:
On Dec 1, 2000, Chris Karakas [EMAIL PROTECTED] wrote:
Do you mean that just by undefining GNUTAR_LISTED_INCREMENTAL_DIR,
AMANDA is going to call tar using --incremental, instead of
--listed-incremental?
That's right.
...
However, you'll still be missing the `--newer' flag
[if you go for keeping GNUTAR_LISTED_INCREMENTAL_DIR defined and using
a wrapper script instead.
, that is passed when GNUTAR_LISTED_INCREMENTAL_DIR is
^ not
used. You may have to work around this problem by reading/storing
timestamps in the `filename' argument.
So, actually, the --newer flag *will* be passed if I undef
GNUTAR_LISTED_INCREMENTAL_DIR and I don't miss anything, do I?
Right.
--
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: Amanda 2.4.2 and HP-UX 11.00
I see from the readme file that amanda was not tested on HP-UX 11.00. That file probably has not been updated for ages. Don't take the lack of a reference to mean it hasn't been done. Has anyone ever gotten this to work under 11.00 or should I give up? Do I take it from this you're having trouble? What, **exactly**, is going wrong? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] P.S. Please turn off "send as HTML, too" in your mailer. It's just annoying and a waste of bandwidth.
No-rewind tape device on Linux Redhat...?
Hello all, I am fairly new to Linux Administration, new enough to not know very much about tape drives at all. I have a Sony DAT SCSI tape drive that uses 4 GIG/8 GIG with hardware compression tapes. I am trying to set it up with AMANDA but I have no idea which device is the no-rewind tape device and not even the faintest clue about how to tell if hardware compression is enabled or disabled. Is there anyone out there that can guide me to any resources that will help me out, or better yet tell me how to know what tape devices are what in Red Hat Linux release 6.1 (Cartman) Kernel 2.2.12-20 on an i586? Any help will be greatly appreciated. Thanks for your time Isaac D. Flemming
Re: Frusturating problem with amcheck
amandad: error receiving message: Connection refused This message happens two places in amandad, both right after doing a dgram_recv. That function, in turn, calls select() and recvfrom(), and those are the **only** two things it calls. According to my Solaris man pages, ECONNREFUSED is not one of the error codes they can return. So the first question is, what OS are you using? The second is, in the man pages you have for select (the system call) and recvfrom, what can cause ECONNREFUSED? If nothing is listed, I'd start asking your OS folks what's up with their documentation and while they're at it, what can cause the error. If you want to narrow it down a bit, add a couple of dbprintf calls in dgram_recv to see which call is doing the deed. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Frusturating problem with amcheck
On Dec 5, 2000, "John R. Jackson" [EMAIL PROTECTED] wrote:
amandad: error receiving message: Connection refused
This message happens two places in amandad, both right after doing
a dgram_recv.
The second is, in the man pages you have for select (the system
call) and recvfrom, what can cause ECONNREFUSED?
I believe some OSs will generate an ECONNREFUSED reply when a datagram
is sent to a UDP port that is not open.
--
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: Amanda 2.4.2 and HP-UX 11.00
John and the list, sorry for the HTML. The current problem I am having is with the "make install" as follows: creating libamanda.la (cd .libs rm -f libamanda.la ln -s ../libamanda.la libamanda.la) /usr/bin/sh ../config/mkinstalldirs /usr/local/lib /usr/bin/sh ../libtool --mode=install /usr/sbin/install libamanda.la /usr/loca l/lib/libamanda.la /usr/sbin/install .libs/libamanda.lai /usr/local/lib/libamanda.la find: cannot stat /usr/local/lib/libamanda.la install: libamanda.lai was not found anywhere! *** Error exit code 2 Stop. *** Error exit code 1 Stop. *** Error exit code 1 Stop. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of John R. Jackson Sent: Tuesday, December 05, 2000 3:51 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: Amanda 2.4.2 and HP-UX 11.00 I see from the readme file that amanda was not tested on HP-UX 11.00. That file probably has not been updated for ages. Don't take the lack of a reference to mean it hasn't been done. Has anyone ever gotten this to work under 11.00 or should I give up? Do I take it from this you're having trouble? What, **exactly**, is going wrong? John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] P.S. Please turn off "send as HTML, too" in your mailer. It's just annoying and a waste of bandwidth.
Re: Amanda 2.4.2 and HP-UX 11.00
On Dec 5, 2000, "Terry Rossi" [EMAIL PROTECTED] wrote:
John and the list, sorry for the HTML. The current problem I
am having is with the "make install" as follows:
Did `make all' create common-src/libamanda.la?
--
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: Frusturating problem with amcheck
Hmmm well the OS in question is Linux 2.2.17... I don't know how much that
helps though it sounds like the UDP packets arent being fired off right
once in awhile... I know UDP is non-error-correcting is there any way to
ask amanda to do this via tcp?
On Dec 5, 2000, "John R. Jackson" [EMAIL PROTECTED] wrote:
amandad: error receiving message: Connection refused
This message happens two places in amandad, both right after doing
a dgram_recv.
The second is, in the man pages you have for select (the system
call) and recvfrom, what can cause ECONNREFUSED?
I believe some OSs will generate an ECONNREFUSED reply when a datagram
is sent to a UDP port that is not open.
--
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
--
The day Microsoft makes something that doesn't suck is probably the day they
start making vacuum cleaners.
Re: Frusturating problem with amcheck
Hmmm well the OS in question is Linux 2.2.17... On the client and the server? Any nasty icky firewall things in between? is there any way to ask amanda to do this via tcp? Sure. Just write the code and put it in :-). It's on the (very long) list of things to do. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
SCSI Changers and amlabel
Hi, I have installed amanda 2.4.2-19991216-beta1 installed on FreeBsd 4.2 My tape robot is a BreeceHill Qt2.15, which has 15 slots and one DLT 4000 drive. I have configured amanda to use the chg-multi script. My tape device is /dev/nrsa0 and my changer is /dev/ch0. My quiestions is this: Do I configure my changer.conf slots as slot 0 /dev/nrsa0 to . . slot 15 /dev/nrsa0 or slot 0 /dev/ch0 to . . slot 15 /dev/ch0 Also do I have to load each tape into the drive using the chio comannd before I can use amlabel or will the amlabel command automatically move the tape from each slot into the default tape drive before labelling? Thanks in advance
Re: No-rewind tape device on Linux Redhat...?
hello Isaac, this is an example, but if your auto-rewind device is /dev/st0, the non-rewind device is /dev/nst0. If you want to crontol hardware compression on/off , you may use the "mt" command (have a look at the man page) for example: mt -f /dev/st0 datcompression off .. but compression control may depend on your tape device SCSI implementation. Pierre. Hello all, I am fairly new to Linux Administration, new enough to not know very much about tape drives at all. I have a Sony DAT SCSI tape drive that uses 4 GIG/8 GIG with hardware compression tapes. I am trying to set it up with AMANDA but I have no idea which device is the no-rewind tape device and not even the faintest clue about how to tell if hardware compression is enabled or disabled. Is there anyone out there that can guide me to any resources that will help me out, or better yet tell me how to know what tape devices are what in Red Hat Linux release 6.1 (Cartman) Kernel 2.2.12-20 on an i586? Any help will be greatly appreciated. Thanks for your time Isaac D. Flemming
Re: SCSI Changers and amlabel
My tape robot is a BreeceHill Qt2.15, which has 15 slots and one DLT 4000 driv e. I have configured amanda to use the chg-multi script. ... The chg-multi changer is meant to emulate a changer using multiple tape drives. That's not what you have. My guess is you want chg-scsi or chg-chio (since you mentioned having chio). Also do I have to load each tape into the drive using the chio comannd before I can use amlabel or will the amlabel command automatically move the tape from each slot into the default tape drive before labelling? Once you get the right changer configured, you will be able to use the "slot XXX" parameters on amlabel to have it load the tape for you. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
EXB-8900 tapetype, please
Greetings; Does anyone have the tapetype definiton for the Exabyte 8900 drive? We are using a Mammoth-LT and 125m tapes in an Exabyte EZ-17 autoloader; nothing was found in the online archives. Thanks, tony --== Sent via Deja.com http://www.deja.com/ ==-- Before you buy.
Re: Amanda 2.4.2 and HP-UX 11.00
Yes it did. Permissions are wide open, the make was done as root. Did `make all' create common-src/libamanda.la?
Re: amanda to blame for NT crashes?
(Joi and David, please just read on) Alexandre Oliva wrote: On Dec 4, 2000, Chris Karakas [EMAIL PROTECTED] wrote: when you use SAMBA for the vfat partitions of your dual boot system, it does not work. What do you mean? It works for me. Or are you talking about backing up vfat partitions while running GNU/Linux, in which case Samba isn't used at all; all you need is GNU tar? I mean, I have tried both, without success. Here's what I tried: Common part in both situations: The vfat partitions are mounted under /dos as /dos/c, /dos/d etc. This is done in boot time from fstab: /dev/hda3 /dos/cvfat defaults,uid=500,gid=101,umask=002 0 0 /dev/hda5 /dos/dvfat defaults,uid=500,gid=101,umask=002 0 0 etc. uid is user chris, gid is group windows. AMANDA is member of the group. This way *all* files get the permissions -rwxrwxr-x, i.e. they become executables, even if they are not (probably due to the umask I use). (That's the first thing that annoys me in mount: I can't map the archive bit to the fictitious executable bits, as SAMBA is able to do when the files are on ext2 partitions). Now, for the two cases I have tested: 1. The Linux/AMANDA server becomes a SAMBA server too. The /dos/c, /dos/d directories are exported as C and D respectively. In disklist I would have //bacchus/c and //bacchus/d as the directories to be backed up with tar, where bacchus is the Linux/AMANDA/SAMBA server. 2. No SAMBA in this case. I just tell AMANDA to use tar to backup the directories /dos/c, /dos/d etc. In both cases, incrementals are almost as large as full backups. It was not always so: I had to boot Windows a few times (which I do not do very often) to get this behaviour, so it is seems to be the problem of inodes on vfat not being constant between mounts (after some kernel, I think 2.2.5). But, this is also curious: Even if I do not boot between two successive AMANDA runs (i.e. the vfat filesystems stay mounted with the same inode numbers), even then, a level 1 incremental which is done the day after a level 0 was done, is almost as big as level 0. I can't figure what's going on. From now on, I have set "dumpcycle 0" for the vfat filesystems. Which has just given me yet another idea for you to try: set up your GNU/Linux box as a Samba server, and run your backups pretending the GNU/Linux box is actually running MS-Windows, i.e., arrange for it to be backed up through Samba. This will use Samba's mechanism of creating incrementals, which are quite different from those of GNU tar, and might get you around the problems you're facing with vfat, GNU tar, the Linux kernel or whatever :-) This is exactly my case 1. Joi Ellis may remember that I contacted him offline for this problem 6 months ago. I came to the coclusion that I could not map the archive bit on some (even fictitious) execute bit, which would then be used by SAMBA as an archive bit to compute incrementals and that this was the reason incrementals were so big. So the problem seems to be the vfat driver in mount, which cannot map the archive bit at anything meaningful, although it sets it correctly, according to David Woodhouse [EMAIL PROTECTED] in the linux-kernel mailing list: ---snip We do, however, correctly set the archive bit whenever we modify or create a file on a FAT filesystem, so it should be usable for its intended purpose. You just need to make sure your backup program uses the ATTR_ARCH flags to decide whether to back up each file, and resets the flag after/before doing the backup. ---snip Any more ideas now? How can this "ATTR_ARCH" flag be reasonably used here? -- Regards Chris Karakas Dont waste your cpu time - crack rc5: http://www.distributed.net
