No Subject
unsubscribe [EMAIL PROTECTED]
Gnutar
"exclude (list)" only works with GNUTAR. When we don't want backup one subdirectory, for example, we want to back up /chroot partition, but not /chroot/ftp/. we need to set : --- program "GNUTAR" #this is only for this partition, others are DUMP exclude "/chroot/ftp" - is this right? --weihai
Re: Amanda with two tape devices
* Miguel Nuno de Almeida Vasconcelos Ribeiro [EMAIL PROTECTED] (Thu, Apr 05, 2001 at 09:46:35AM +0100) Can it be done ? Yes Can amanda use who tape devices to perform a single backup? No What can I expect of it? Good performance Where can I find Info ? Here. Basically what you do (or what I did) is to set up different configurations (differtn disklists/tapelists) for each tapedevice, and work from there. Half your diskspace for tape1, the other ahlf for tape2 (or if you have different capaicty tapedrives, simply use more for one than the other) Currently listening to: Phish - Layla (11-29-98) Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O Standing above the crowd, he had a voice so strong and loud =`\, we'll miss him (=)/(=) Ranting and pointing his finger, At everything but his heart we'll miss him
Adding tapes
Title: Clear Day Folks, I am planning to increase the number of tapes in my rotation. Do I need to change any other "constant" then number of tapes in tape cycle. Dr Prabhakar Ganapathy ( Dr.Prab)Unix Systems AdminSNET Internet Services203-985-4724
Re: Yet another Insecure Port ...
The ports that worked best for me were: --with-portrange=2064,2320 --with-udpportrange=830,870 Also, some other firewall wierdness I've had (with RedHat6.2's ipchains) was once in a while a fragmented packet is sent, for whatever reason. My amanda client's firewall log would show 3 denied packets from the tape server, with source and destination ports of 65535. To get around this, you need a rule that allows fragmented packets, such as this: -A input -s server_ip/32 -d client_ip/32 -f -j ACCEPT On Wed, 04 Apr 2001, Doug Silver wrote: Brand new build of amanda 2.4.2p2 server config build: /configure --with-gnutar=/usr/local/bin/tar --with-portrange=900,950 --with-udpportrange=900,950 (etc) client config build: ./configure --with-gtar=/usr/local/bin/gtar --without-server --with-portrange=900,950 --with-udpportrange=900,950 Server binaries: -rwsr-x--- 1 root wheel 68759 Apr 4 15:46 /usr/local/libexec/calcsize* -rwsr-x--- 1 root wheel 231765 Apr 4 15:47 /usr/local/libexec/dumper* -rwsr-x--- 1 root wheel 58227 Apr 4 15:46 /usr/local/libexec/killpgrp* -rwsr-x--- 1 root wheel 309711 Apr 4 15:47 /usr/local/libexec/planner* -rwsr-x--- 1 root wheel 56004 Apr 4 15:46 /usr/local/libexec/rundump* -rwsr-x--- 1 root wheel 56761 Apr 4 15:46 /usr/local/libexec/runtar* -rwsr-x--- 1 root wheel 322122 Apr 4 15:47 /usr/local/sbin/amcheck* Client: ls: /usr/local/libexec/dumper: No such file or directory ls: /usr/local/libexec/planner: No such file or directory -rwsr-x--- 1 root wheel 71756 Apr 4 17:22 /usr/local/libexec/calcsize* -rwsr-x--- 1 root wheel 62521 Apr 4 17:22 /usr/local/libexec/killpgrp* -rwsr-x--- 1 root wheel 60112 Apr 4 17:22 /usr/local/libexec/rundump* -rwsr-x--- 1 root wheel 60905 Apr 4 17:22 /usr/local/libexec/runtar* amcheck -c test Amanda Backup Client Hosts Check ERROR: frog.hoop-t.net: [host cat.hoop-t.net: port 62870 not secure] Client check: 1 host checked in 0.076 seconds, 1 problem found I'm not seeing any errors through the firewall, so I'm not sure how to further debug this. Any suggestions? Has anyone got Amanda to work using the udpportrange/portrange options through a firewall? Thanks! ~ Doug Silver 619 235-2665 Quantified Systems, Inc ~ Here's the client amandad.debug packet stuff: sending ack: Amanda 2.4 ACK HANDLE 000-00300D08 SEQ 986430352 amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-00300D08 SEQ 986430352 ERROR [host cat.hoop-t.net: port 62870 not secure] amandad: got packet: Amanda 2.4 ACK HANDLE 000-00300D08 SEQ 986430352 amandad: pid 56308 finish time Wed Apr 4 17:25:53 2001 -- Jason Hollinden SMG Systems Admin
Re: more with ADIC-1200 + SunOS 5.8 'sgen' driver and mtx problems
On Wednesday 04 April 2001 3:21 pm, Rhett Saunders wrote: [storage-element-number][drive#] mtx [ -f loader-dev ] [eepos eepos-number] transfer storage-element-number storage-element-number mtx [ -f device ] eject # mtx -f /dev/rsst1 first mtx: No such device or address mtx: No such device or address mtx: Request Sense: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 mtx: READ ELEMENT STATUS Command Failed I wonder if this is related to a problem I had when setting up AMANDA using chg-scsi on a solaris box I had lying around. When doing ioctls on the scsi-generic device, the ioctl would fail unless there was a valid buffer supplied to return data in, even if the particular SCSI command was positional (i.e. move tape) and therefore wasn't going to return any data. This resulted in it simply not working for no readily apparent reason, until I bodged a small buffer into SCSI_Move() in scsi-changer-driver.c so that it always supplied one to SCSI_ExecuteCommand() -- Tim Smith ([EMAIL PROTECTED]) Rebel SpecForces foil unauthorised cloning attempt on General Madine. "I'm beside myself." says General.
large filesystem problems
Hello. I have recently added a disk that is roughly 60gb in size. One of the partitions is about 51gb. This particular machine is running bsdi4.2. This and the tapeserver are running amanda 2.4.2. My tape server is a redhat 6.1 machine, and is successfully backing up three other systems. I am using dump, no compression, and level 0. When I run amdump, everything appears to be ok, but I use amcheck and it tells me that it is "getting estimate", on both the large 51gb part, and the smaller 50mb part. When I try to backup only the 50mb part, it runs perfectly fine. This has all started by introducing this large partition. I have spent a couple of hours looking through the mailing list and found people with similiar problems, but they all seemed to be using tar. I am not. Any help would be greatly appreciated. Thank You, Jeff Heckart MICS Staff [EMAIL PROTECTED]
Re: Yet another Insecure Port ...
From a security perspective, you normally don't want to allow packet fragments. In most cases, turning off packet fragmentation is generally what you want. Why? Well, because some rules can not be properly applied to packet fragments which may create potential security concerns. Greg Jason Hollinden wrote: The ports that worked best for me were: --with-portrange=2064,2320 --with-udpportrange=830,870 Also, some other firewall wierdness I've had (with RedHat6.2's ipchains) was once in a while a fragmented packet is sent, for whatever reason. My amanda client's firewall log would show 3 denied packets from the tape server, with source and destination ports of 65535. To get around this, you need a rule that allows fragmented packets, such as this: -A input -s server_ip/32 -d client_ip/32 -f -j ACCEPT On Wed, 04 Apr 2001, Doug Silver wrote: Brand new build of amanda 2.4.2p2 server config build: /configure --with-gnutar=/usr/local/bin/tar --with-portrange=900,950 --with-udpportrange=900,950 (etc) client config build: ./configure --with-gtar=/usr/local/bin/gtar --without-server --with-portrange=900,950 --with-udpportrange=900,950 Server binaries: -rwsr-x--- 1 root wheel 68759 Apr 4 15:46 /usr/local/libexec/calcsize* -rwsr-x--- 1 root wheel 231765 Apr 4 15:47 /usr/local/libexec/dumper* -rwsr-x--- 1 root wheel 58227 Apr 4 15:46 /usr/local/libexec/killpgrp* -rwsr-x--- 1 root wheel 309711 Apr 4 15:47 /usr/local/libexec/planner* -rwsr-x--- 1 root wheel 56004 Apr 4 15:46 /usr/local/libexec/rundump* -rwsr-x--- 1 root wheel 56761 Apr 4 15:46 /usr/local/libexec/runtar* -rwsr-x--- 1 root wheel 322122 Apr 4 15:47 /usr/local/sbin/amcheck* Client: ls: /usr/local/libexec/dumper: No such file or directory ls: /usr/local/libexec/planner: No such file or directory -rwsr-x--- 1 root wheel 71756 Apr 4 17:22 /usr/local/libexec/calcsize* -rwsr-x--- 1 root wheel 62521 Apr 4 17:22 /usr/local/libexec/killpgrp* -rwsr-x--- 1 root wheel 60112 Apr 4 17:22 /usr/local/libexec/rundump* -rwsr-x--- 1 root wheel 60905 Apr 4 17:22 /usr/local/libexec/runtar* amcheck -c test Amanda Backup Client Hosts Check ERROR: frog.hoop-t.net: [host cat.hoop-t.net: port 62870 not secure] Client check: 1 host checked in 0.076 seconds, 1 problem found I'm not seeing any errors through the firewall, so I'm not sure how to further debug this. Any suggestions? Has anyone got Amanda to work using the udpportrange/portrange options through a firewall? Thanks! ~ Doug Silver 619 235-2665 Quantified Systems, Inc ~ Here's the client amandad.debug packet stuff: sending ack: Amanda 2.4 ACK HANDLE 000-00300D08 SEQ 986430352 amandad: sending REP packet: Amanda 2.4 REP HANDLE 000-00300D08 SEQ 986430352 ERROR [host cat.hoop-t.net: port 62870 not secure] amandad: got packet: Amanda 2.4 ACK HANDLE 000-00300D08 SEQ 986430352 amandad: pid 56308 finish time Wed Apr 4 17:25:53 2001 -- Jason Hollinden SMG Systems Admin -- Greg Copeland, Principal Consultant Copeland Computer Consulting -- PGP/GPG Key at http://www.keyserver.net DE5E 6F1D 0B51 6758 A5D7 7DFE D785 A386 BD11 4FCD --
[GNUTAR program not available]
Hi Folk,
I change the gtar-Version from version 1.13. to 1.13.17
and the same error occured...
**
in
vi config.site
are the Entry:
GNUTAR=/usr/sbin/tar
**
**
amanda@daphne:/usr/local/etc/amanda/config which tar
/usr/sbin/tar
**
**
-rwsr-x--- 1 root bin 1019424 Apr 5 13:50 amcheck
-rwxr-xr-x 1 amanda bin 1799 Apr 5 13:50 amcheckdb
-rwxr-xr-x 1 amanda bin 3924 Apr 5 13:50 amcleanup
-rwxr-xr-x 1 amanda bin 3566 Apr 5 13:50 amdump
amanda@daphne:/usr/local/etc/amanda/config tar --version
tar (GNU tar) 1.13.17
Copyright 2000 Free Software Foundation, Inc.
This program comes with NO WARRANTY, to the extent permitted by law.
You may redistribute it under the terms of the GNU General Public License;
see the file named COPYING for details.
Written by John Gilmore and Jay Fenlason.
amanda@daphne:/usr/local/etc/amanda/config
**
**
amanda@daphne:/usr/local/sbin amcheck config
Amanda Tape Server Host Check
-
Holding disk /bkup: 3842892 KB disk space available, that's plenty
NOTE: skipping tape-writable test
Tape DailySet1-000 label ok
Server check took 6.586 seconds
Amanda Backup Client Hosts Check
ERROR: daphne.webcom.de: [GNUTAR program not available]
!!!--- that's the point I did'nt get :-(
Client check: 1 host checked in 0.745 seconds, 1 problem found
(brought to you by Amanda 2.4.2)
amanda@daphne:/usr/local/etc/amanda/config
**
**
These dumps were to tape DailySet1-000.
The next tape Amanda expects to use is: DailySet1-003.
FAILURE AND STRANGE DUMP SUMMARY:
daphne.web /var/log lev 0 FAILED [Request to daphne.webcom.de timed out.]
daphne.web /etc lev 0 FAILED [Request to daphne.webcom.de timed out.]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:01
Run Time (hrs:min) 0:01
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- --
Filesystems Dumped0 0 0
Avg Dump Rate (k/s) -- -- --
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 0.00.00.0
Tape Used (%) 0.00.00.0
Filesystems Taped 0 0 0
Avg Tp Write Rate (k/s) -- -- --
NOTES:
planner: Adding new disk daphne.webcom.de:/etc.
planner: Adding new disk daphne.webcom.de:/var/log.
driver: WARNING: got empty schedule from planner
taper: tape DailySet1-000 kb 0 fm 0 [OK]
**
does anyone have some ideas?
It whold be very nice :-)
Bernd Zimmermann
Re: large filesystem problems
* Jeff Heckart [EMAIL PROTECTED] (Thu, Apr 05, 2001 at 09:42:50AM -0400) Hello. I have recently added a disk that is roughly 60gb in size. One of the partitions is about 51gb. This particular machine is running bsdi4.2. This and the tapeserver are running amanda 2.4.2. My tape server is a redhat 6.1 machine, and is successfully backing up three other systems. I am using dump, no compression, and level 0. When I run amdump, everything appears to be ok, but I use amcheck and it tells me that it is "getting estimate", on both the large 51gb part, and the smaller 50mb part. When I try to backup only the 50mb part, it runs perfectly fine. This has all started by introducing this large partition. I have spent a couple of hours looking through the mailing list and found people with similiar problems, but they all seemed to be using tar. I am not. Same problem. The getting estimate takes forever and then some, so you may have to change your etime to someting larger (7200 for 2 hours). (and yes, i wouldn;t be surprrised if it indeed takes 2 hours to ewstimate a latrge disk, esp if it's full and you need to get 3 estimate (level 0, current incremental level, current incremental level +1). Alternatively you can patch client-src/sendsize.c as below, define USE_GENERIC_CALCSIZE and recompile sendsize /* Now in the child process */ if(strcmp(est-program, "DUMP") == 0) dump_calc_estimates(est); else #ifndef USE_GENERIC_CALCSIZE # ifdef SAMBA_CLIENT if (strcmp(est-program, "GNUTAR") == 0 est-amname[0] == '/' est-amname[1] == '/') smbtar_calc_estimates(est); else # endif # ifdef GNUTAR if (strcmp(est-program, "GNUTAR") == 0) gnutar_calc_estimates(est); else # endif #endif generic_calc_estimates(est); Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: large filesystem problem
Hello, Check /tmp/amanda/ for log files of the tar attempt. Specifically look at sendsize.debug. This will give you the output of your tar. What size is your tape drive? What happens after "getting estimate"? Andrew On Thu, 5 Apr 2001, Jeff Heckart wrote: Hello. I have recently added a disk that is roughly 60gb in size. One of the partitions is about 51gb. This particular machine is running bsdi4.2. This and the tapeserver are running amanda 2.4.2. My tape server is a redhat 6.1 machine, and is successfully backing up three other systems. I am using dump, no compression, and level 0. When I run amdump, everything appears to be ok, but I use amcheck and it tells me that it is "getting estimate", on both the large 51gb part, and the smaller 50mb part. When I try to backup only the 50mb part, it runs perfectly fine. This has all started by introducing this large partition. I have spent a couple of hours looking through the mailing list and found people with similiar problems, but they all seemed to be using tar. I am not. Any help would be greatly appreciated. Thank You, Jeff Heckart MICS Staff
FreeBSD Build
What is required to build amanda-2.4.2p2 on FreeBSD 4.2? I can't use the ported version because I have a CVS version of amanda installed on my clients which are all Linux and produced timeout errors with the version that FreeBSD has ported. I have tried to build p2, but it fails at amoverview. make: don't know how to make amoverview. Stop *** Error code 1 Thanks Casey Scott
Tape Duplication
Hello, Is there any way to duplicate a tape with amanda? Andrew
Strange Failure: dumps too big
Hi, This night backup I got the following message: FAILURE AND STRANGE DUMP SUMMARY: host2 sd0h lev 0 FAILED [dumps too big, but cannot incremental dump new disk] The real strange thing is that this is a read-only file system and didn't grow up since yesterday, and it's not the biggest FS in this backup set. It has only 502MB. The amanda version is 2.4.1p1-19981003. Any help? - Marcelo
Re: FreeBSD Build
cd /usr/ports/misc/amanda24-server make install Andrew On Thu, 5 Apr 2001, C Scott wrote: What is required to build amanda-2.4.2p2 on FreeBSD 4.2? I can't use the ported version because I have a CVS version of amanda installed on my clients which are all Linux and produced timeout errors with the version that FreeBSD has ported. I have tried to build p2, but it fails at amoverview. make: don't know how to make amoverview. Stop *** Error code 1 Thanks Casey Scott
linux kernel-2.4.2 issue
My amanda backup server runs Debian GNU/linux. I've had it running kernel version 2.2.16 for months and it has been working great, backing up a small network of ten machines. Kudos to the Amanda team. I recently compiled a 2.4.2 kernel for the backup server. If I boot this kernel, then one of my clients (coredump) fails consistently to backup. The amanda mail report says "FAILED [nak error:amandad busy]". All partitions on coredump fail with this error. Further investigation shows that the backups for coredump fail in the estimation phase. Coredump is also a debian system, kernel 2.4.3-pre8. If I revert to kernel version 2.2.16 on the amanda server, then coredump backs up with no errors. Obviously I'm staying with linux kernel 2.2.16 on the server for now. I can provide more detailed information if anyone is interested. -John -- John Palkovic Software Engineer HyperFeed Technologies
amanda issue
Title: amanda issue Hi, I'm installing amanda software on Sun Solaris box. I make userand as amanda. i logged in as amanda and run ./configure --with-user=amanda --with-group=amanda . works fine after that i logeed in as root and give a command make it gives me an error:- rm -fr .libs/libamanda.la .libs/libamanda.* .libs/libamanda-2.4.2p1.* ar cru .libs/libamanda.a alloc.o amflock.o debug.o dgram.o error.o file.o fileheader.o match.o protocol.o regcomp.o regerror.o regexec.o regfree.o security.o statfs.o stream.o token.o util.o version.o versuff.o pipespawn.o ../libtool: ar: not found make[1]: *** [libamanda.la] Error 1 make[1]: Leaving directory `/export/home/amanda/amanda-2.4.2p1/common-src' make: *** [all-recursive] Error 1 my directory path is :- # echo $PATH /usr/local/bin:/usr/sbin:/usr/bin kindly let me know how to resolve this Anurag
Re: amanda issue
amanda issueHi, I'm installing amanda software on Sun Solaris box. I make userand as amanda. i logged in as amanda and run ./configure --with-user=amanda --with-group=amanda . works fine after that i logeed in as root and give a command make it gives me an error:- ../libtool: ar: not found ^^^ add /usr/ccs/bin to your path - re-run make -Ben
Re: block device and amanda
But after to do searched in fac and other documents, i don't read if Amanda supports block device(hard drive) ... There is a development branch of the latest 2.4.2 release that supports using disk instead of tape. You'll need to get it from the CVS tree (see the FAQ) and use branch "amanda-242-tapeio". E.B John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: linux kernel-2.4.2 issue
* John Palkovic [EMAIL PROTECTED] (Thu, Apr 05, 2001 at 12:08:23PM -0500) My amanda backup server runs Debian GNU/linux. I've had it running kernel version 2.2.16 for months and it has been working great, backing up a small network of ten machines. Kudos to the Amanda team. I recently compiled a 2.4.2 kernel for the backup server. If I boot this kernel, then one of my clients (coredump) fails consistently to backup. The amanda mail report says "FAILED [nak error:amandad busy]". All partitions on coredump fail with this error. Further investigation shows that the backups for coredump fail in the estimation phase. Coredump is also a debian system, kernel 2.4.3-pre8. If I revert to kernel version 2.2.16 on the amanda server, then coredump backs up with no errors. Obviously I'm staying with linux kernel 2.2.16 on the server for now. I can provide more detailed information if anyone is interested. Hmm, This 2.4 kernel, does this also imply glibc2.2 ? I have a couple of suse 7.1 boxes (kernel 2.4.X, glibc2.2) and amanda works fine. I did however reinstall the cvorrect tar version (1.13.19) and I use the sendisze hack (see prebious post about large file systems). So, maybe you need to check if you are using the ciorrect tar version. Kind regards, -- Gerhard den Hollander Phone +31-10.280.1515 Technical Support Jason Geosystems BV Fax +31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
Re: Sector Level Backups
I would like to use "dd" , or some similar tool to make exact images=20 of a drive as a full backup, rather than dump or tar. ... Alexandre's answer is correct about how to do this with Amanda. But I'm curious why you would want to. If you're backing up a disk that contains file systems, the result will be almost useless unless you've unmounted all the file systems while the backup is running. And dumping all that "free space" is just a waste of time, bandwidth and tape. Dave John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] P.S. Please turn off "send as HTML" in your mailer. It's just a waste of bandwidth.
timed out
I'm not sure why this happens: FAILURE AND STRANGE DUMP SUMMARY: corp hdc3 lev 0 FAILED [Request to corp timed out.] corp hda3 lev 0 FAILED [Request to corp timed out.] corp hda1 lev 0 FAILED [Request to corp timed out.] this error happens every night, i have already verified that: - the client (corp) is properly configured (correct entries are in /etc/inetd.conf) and is listening and responding on the proper ports - the server does not find this problem on client (corp) when i run ./amcheck - the server and user (amanda) are set up in .amandahosts and .rhosts on the client (corp) - there is no firewall preventing direct communication between client and server. i've run amandad on client (corp) manually and it runs without err. Any suggestions? thanks in advance, Rob
results missing
Having this problem where two of my directories say RESULTS MISSING in the log files. Anyone know what that means? Is it because I didn't have enough tape to do a level 0? thanks e = --Eff Edwards __ Do You Yahoo!? Get email at your own domain with Yahoo! Mail. http://personal.mail.yahoo.com/
Re: linux kernel-2.4.2 issue
* John Palkovic [EMAIL PROTECTED] (Thu, Apr 05, 2001 at 02:04:07PM -0500) Tar is coredump:/tmp tar --version tar (GNU tar) 1.12 on both server and client. The amanda patches were applied to this tar. OK, I remember going to 1.13.19 after someone here suggested that this was better than (even_ 1.12 w/ amanda patches because under some strange circumstances it could coredump. When I upped my boxes to suse 7.1/2.4/glibc2.2 I also got a new tar (1.13.whatever0 and noticed it dump core everytime. When I went and copied my 1.13.19 over the current tar things started functioning again. I never tried booting back to 2.2.18 and see what happened then. It woudln't surprise me if there is something in the combo 2.4kernel/glibc2.2/amanda2.4.2 that causes a coredump in the 1.12 So, maybe you need to check if you are using the ciorrect tar version. If I do nothing but boot a kernel 2.4.2 on the server, the backups fail. If I revert to 2.2.16 on the server, everything is fine. Well, checking a new tar version is a small effort. If you want I can send you my binary, so you can drop it in and see if the dumops work again. Currently listening to: Porcupine Tree - Untitled Gerhard, [@jasongeo.com] == The Acoustic Motorbiker == -- __O Hypocrites and Zealots =`\, are struggling for the throne, (=)/(=) Kings and queens and presidents All younger then the Stones
Re: large filesystem problems
When I run amdump, everything appears to be ok, but I use amcheck and it tells me that it is "getting estimate" ... Huh? Amcheck doesn't issue that kind of message. Could you post exactly what you did and what it said back? What version of Amanda are you using? What version of dump? What file of file system? Take a look at /tmp/amanda/sendsize*debug and see if it has any clues. Jeff Heckart John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: little question
Sorry, but I can't see any info: amstatus config --file /usr/local/var/amanda/config/amdump.2 Add --stats and --summary to that command to see the extra information. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Linux and p2
Does the lastest release, p2, have the changes in BIND necessary to make Linux systems work that a CVS version from a few weeks ago would have? p1 wouldn't work on my Linux machines. Huh? I'm not sure what you mean by "changes in BIND". Oh, maybe you mean the bind() system call? If so, then yes, it should be fixed. Note that p2 has not officially been released (in spite of what SourceForge may say). The developers are still hassling over a detail and there may be another tar image uploaded. Casey Scott John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: [GNUTAR program not available]
ERROR: daphne.webcom.de: [GNUTAR program not available] This says that when you ran ./configure for daphne.webcom.de, GNU tar was not in the path (or it was a different path). You need to rerun ./configure (do a "make distclean" first) then rebuild/reinstall Amanda. You could also look at an amandad*debug file on daphne for GNUTAR and see if it's listed and if so what the path is. That's what Amanda is looking for (and not finding). Bernd Zimmermann John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Adding tapes
I am planning to increase the number of tapes in my rotation. Do I need = to change any other "constant" then number of tapes in tape cycle. You don't need to, but it depends a little on what you're trying to accomplish. For instance, if you're increasing the number because the dumps won't fit on a tape, you also need to increase dumpcycle to spread things out more. If you just want more "history" (just keep the dumps around longer), then tapecycle is all you need to change. Dr Prabhakar Ganapathy ( Dr.Prab) John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] P.S. Please turn off "send as HTML" in your mailer. It's just a waste of bandwidth. Your two sentences used up over 11 KBytes.
Re: Tape Duplication
Is there any way to duplicate a tape with amanda? It depends on what you mean by "duplicate". If you mean "write a second tape at the same time as the first with exactly the same data", that's not available at the moment but will be easy to do with some code now in the sources. Someone just needs to write the "driver". If you mean "make a copy of an Amanda tape after a run", you can do that with a simple shell script and "dd" loop, or jens persson just posted a new Amanda program, amclone, that will probably do what you want. Look at the mailing list archives around 21-Mar for "amclone". Andrew John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
RE: amanda issue
kindly let me know now what will i do. I want to make this Sun box make as a Backup Server because this box contain a Tape Drive. Waiting for you reply I would highly suggest you read the documentation in the DOCS directory. Also the amanda website has a faq-o-matic page that answers some frequently asked questions. anurag -Ben
Re: FAILED [data timeout] with 2.4.2p1 on Suse 7.0
The self check goes OK, the estimates go OK, but the backup fails with data timeout messages. I have to say, this client has never before been in any amanda config, I was waiting till the upgrade to introduce it. ... I am attaching the debug files, inparticular sendbackup.debug which seems to have died before completing the run. H. "data timeout" says Amanda waited a long time without getting any data at all from the client. What Amanda processes, if any, are still running on the client? According to sendbackup*debug, sendbackup (and amandad) is still running the GNU tar. If it's not still there, something killed it. If you have process accounting turned on, it may tell you what signal they were killed with (if that's what happened). John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: results missing
Having this problem where two of my directories say RESULTS MISSING in the log files. It probably said more than this in the E-mail. Please post more detail, if it's available. What happens if you run amcheck? ... Is it because I didn't have enough tape to do a level 0? No, that wouldn't do it. It's more likely a communications problem between the Amanda server and client. e John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amcheck error
I'm wandering it's amanda configuration problem ... Probably. What Amanda changer are you using? How did you configure it? What are the specifications of the device, i.e. how many slots, how many drives, what are their slot number addresses, etc? Mariko Tagawa John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: more with ADIC-1200 + SunOS 5.8 'sgen' driver and mtx problems
Well, I've tried the 'sst' driver and it works only slightly better than the 'sgen' driver. With the 'sst' driver I can send as many 'mtx inquiry' commands as I like and they all work. What about "mtx -f /dev/rsst5 status"? # mtx -f /dev/rsst5 first mtx: No such device or address ... I don't know what this means, but obviously something is producing incorrect results. Any ideas on what I can look at? We need to see exactly what mtx tried to do. Unfortunately, mtx it not too good at that (see below). Anyway, has anyone done much testing with the 'sst' driver in SunOS 5.8? It seems the bulk of people tend to use Linux or Windows so I guess Solaris testing is not the primary focus of the Amanda development group. Ummm, you've got that twisted a bit. I use only Solaris and AIX and I'm an Amanda developer, but don't use any of the Amanda changers (it's a long story :-), and also do not use mtx. So it's the mtx testing that might be a bit behind, not Solaris. And for that, maybe you should ask the mtx people since it's their program that's not working here, not Amanda. Be that as it may, I have a robot and sst on Solaris 2.6 and should at least be able to get some more debugging output into the code for you to try. What version of mtx are you using? FYI, 1.10 works with inquiry for me but fails (I/O error) for status. Version 1.11pre2 doesn't work at all (I/O error). I'm pretty sure I can get at least those things to work for me, and possibly in the process, get the going for you. Craig. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: FAILED [data timeout] with 2.4.2p1 on Suse 7.0
On Thu, Apr 05, 2001 at 04:31:36PM -0500, John R. Jackson wrote: The self check goes OK, the estimates go OK, but the backup fails with data timeout messages. I have to say, this client has never before been in any amanda config, I was waiting till the upgrade to introduce it. ... I am attaching the debug files, inparticular sendbackup.debug which seems to have died before completing the run. H. "data timeout" says Amanda waited a long time without getting any data at all from the client. What Amanda processes, if any, are still running on the client? None at all (started by amanda that is) According to sendbackup*debug, sendbackup (and amandad) is still running the GNU tar. If it's not still there, something killed it. Actually, /usr/local/bin/gnutar is a wrapper (to stop and start databases) so I have stuck some debugging in there, and I am pretty confident that tar is never even executed. If you have process accounting turned on, it may tell you what signal they were killed with (if that's what happened). OK, thanks, I'll give it a go. -- _ __ CSC Computer Sciences Ltd. Tel : +44 1622 622342 /_| _/ ( _ '_// Pegasus Place, Lodge Rd,Mob : +44 7714 072031 ( |/)(/(/ __)//)/ //) Weavering, Maidstone Email : [EMAIL PROTECTED] / Kent ME14 5EH England. Home : [EMAIL PROTECTED]
FreeBSD dump fails
sendsize.x.debug shows that all dumps are failing with: DUMP: bad sblock magic number DUMP: The ENTIRE dump is reported 30 Gb partition. Is there a 2 Gb partition size limit? Any idea what might be causing this?
Re: FreeBSD dump fails
sendsize.x.debug shows that all dumps are failing with: DUMP: bad sblock magic number DUMP: The ENTIRE dump is reported 30 Gb partition. Is there a 2 Gb partition size limit? ... There may be, but I doubt it is the problem. Any idea what might be causing this? It is not pointing dump at the right place. For instance, dump is trying to process a file/directory instead of a device. Or the dump it is trying to run does not understand the file system type, for instance, running ufsdump on vxfs. Take a look at the dump command Amanda actually ran (also listed in the sendsize*debug file) and make sure it is right. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: FreeBSD dump fails
The sendsize.debug on the failing machine does not show a device being userd. I examined the same file on another machine that is working, and it shows "DUMP: Dumping /dev/sda1 (/(dir var)) to standard output. The problem maching is running FreeBSD 4.2 and the agreeable maching is running Debian 2.2. Should I update the Dump? The disklist entries are identical, except for hostname. On Thu, 5 Apr 2001, John R. Jackson wrote: sendsize.x.debug shows that all dumps are failing with: DUMP: bad sblock magic number DUMP: The ENTIRE dump is reported 30 Gb partition. Is there a 2 Gb partition size limit? ... There may be, but I doubt it is the problem. Any idea what might be causing this? It is not pointing dump at the right place. For instance, dump is trying to process a file/directory instead of a device. Or the dump it is trying to run does not understand the file system type, for instance, running ufsdump on vxfs. Take a look at the dump command Amanda actually ran (also listed in the sendsize*debug file) and make sure it is right. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: LSM - Logical Storage Manager Drives
I have configured the system so that amcheck is happy, but amdump reports disk is offline. I have set the device permissions like so: brw-r root system /dev/vol/rootvol (logical volume) Is your Amanda user (the one inetd/xinetd runs amandad as) in group "system"? What's in /tmp/amanda/sendsize*debug? Walter John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] The sendsize*debug file reveals that the client is trying to use dump instead of vdump upon an advfs file system! How do I configure the client to use vdump instead? Walter
Re: Sector Level Backups
On Apr 5, 2001, "John R. Jackson" [EMAIL PROTECTED] wrote:
But I'm curious why you would want to. If you're backing up a disk that
contains file systems, the result will be almost useless unless you've
unmounted all the file systems while the backup is running.
One of the reasons I could think of to do this is to preserve
information of deleted files that might still be there, that could
then be used for some investigation or as evidence in trial. You'd
probably not want to do this on a regular basis, though, so I'd
probably do this kind of operation as a one-shot thing, without
Amanda.
--
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: LSM - Logical Storage Manager Drives
On Apr 5, 2001, [EMAIL PROTECTED] wrote:
The sendsize*debug file reveals that the client is trying to use dump
instead of vdump upon an advfs file system!
How do I configure the client to use vdump instead?
You get /etc/fstab or equivalent to indicate that directory is mounted
from an advfs.
--
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: Sector Level Backups
Congratulations Alexander, You hit the nail on the head. I am imaging
drives for computer forensics purposes, and am interested in finding faster
easier ways to obtain these images. Images made with dd, when taken from a
read-only mounted drive, are superb evidence. The real fun is getting the
naughty bits off the drive images.
- Original Message -
From: "Alexandre Oliva" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: "Dave Hecht" [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, April 05, 2001 8:21 PM
Subject: Re: Sector Level Backups
On Apr 5, 2001, "John R. Jackson" [EMAIL PROTECTED] wrote:
But I'm curious why you would want to. If you're backing up a disk that
contains file systems, the result will be almost useless unless you've
unmounted all the file systems while the backup is running.
One of the reasons I could think of to do this is to preserve
information of deleted files that might still be there, that could
then be used for some investigation or as evidence in trial. You'd
probably not want to do this on a regular basis, though, so I'd
probably do this kind of operation as a one-shot thing, without
Amanda.
--
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
Advice: NFS vs SMB - looking for the voice of experience
I have just a couple M$oft Win2K boxes that I would like my newly installed Amanda system to backup. I do have NFS servers running on them and presently mount the data directory's, via NFS, onto a Linux box. Keeping in mind that I have 50 GB of data (very little) , and have a 12 hour window for backups (yes, small network in an office) and I really am not worried about preserving ACL's - My question is: Which is easiest to maintain/setup - NFS mount the Win2k volumes onto the Linux box and use a gnu-tar-index backup, or install samba and use smbclient. I lean towards NFS, is there any reason I should not? Thanks for your input. Dave
Re: Advice: NFS vs SMB - looking for the voice of experience
On Apr 5, 2001, "Dave Hecht" [EMAIL PROTECTED] wrote:
Which is easiest to maintain/setup - NFS mount the Win2k volumes onto the
Linux box and use a gnu-tar-index backup, or install samba and use
smbclient. I lean towards NFS, is there any reason I should not?
I'd much rather use NFS than SMB. It's generally far more efficient.
However, God only knows how much crap an NFS server running on
MS-Windows would have to work against, so it might be that it actually
takes longer to run.
I'd probably do some testing with both tar over NFS and smbtar before
making a decision, then post the results here for the benefit of
others in the same situation (hint, hint :-)
--
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: LSM - Logical Storage Manager Drives
From: Alexandre Oliva [EMAIL PROTECTED] Date: Fri Apr 6, 2001 3:24am Subject: Re: LSM - Logical Storage Manager Drives On Apr 5, 2001, [EMAIL PROTECTED] wrote: The sendsize*debug file reveals that the client is trying to use dump instead of vdump upon an advfs file system! How do I configure the client to use vdump instead? You get /etc/fstab or equivalent to indicate that directory is mounted from an advfs. The entry in the fstab looks good and looks like this on both machines: root_domain#root / advfs rw 1 0 More info: This was working fine in 2.4.2p1 but now that I have upgraded to 2.4.2p2 its not working on any client or even the server anymore. I have had to place a #undef DUMP in the config.h to get around this but I thought someone should be informed. Walter Zambotti
Re: Advice: NFS vs SMB - looking for the voice of experience
... I lean towards NFS, is there any reason I should not? I know very little about this, but the one thing that popped to mind is whether an MS NFS server would give a tar running as root on a client (to NFS) enough access to get to everything. The normal action is to convert all root requests to "nobody", which will not work well for backups. Dave John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: FreeBSD dump fails
The sendsize.debug on the failing machine does not show a device being userd. I examined the same file on another machine that is working, and it shows "DUMP: Dumping /dev/sda1 (/(dir var)) to standard output. ... So that says Amanda was not able to convert the disklist name it was given into a device name. Are both systems running the same version of Amanda client? What version(s) are you running? What name did you use in disklist? Does that name show up in /etc/fstab (or whatever the equivalent is for the OS with a problem)? To test this, you can cd to client-src and "gmake getfsent", then run it with the disklist name as an argument. It will show you the result of looking up several built-in "standard" names and also any names from the command line. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: LSM - Logical Storage Manager Drives
The entry in the fstab looks good and looks like this on both machines: root_domain#root / advfs rw 1 0 That would seem to be reasonable. This was working fine in 2.4.2p1 but now that I have upgraded to 2.4.2p2 its not working on any client or even the server anymore. OK, I can guess which pair of changes are involved. But since I don't have access to a system like this, either you'll have to work on the problem (with guidance) or someone else with such a system will have to dig into it. So, are you up to taking debugging patches from me, or looking into it yourself, or providing a temporary, non-privileged, account? To test the problem, go to client-src and "gmake getfsent", then run it. It will dump out several standard lookups Amanda makes, including "/". Walter Zambotti John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Advice: NFS vs SMB - looking for the voice of experience
On Wed, 4 Apr 2001, Dave Hecht wrote: I have just a couple M$oft Win2K boxes that I would like my newly installed Amanda system to backup. I do have NFS servers running on them and presently mount the data directory's, via NFS, onto a Linux box. Keeping in mind that I have 50 GB of data (very little) , and have a 12 hour window for backups (yes, small network in an office) and I really am not worried about preserving ACL's - My question is: Which is easiest to maintain/setup - NFS mount the Win2k volumes onto the Linux box and use a gnu-tar-index backup, or install samba and use smbclient. I lean towards NFS, is there any reason I should not? I would prefer NFS mounted volumes for the following reasons: smbtar currently only supports doing incremental dumps via a single archive bit, i.e. you only get level 0 and level 1 dumps. If you have a dumpcycle of say two weeks the level 1 dump just before the a level 0 dump will collect all changes of the last two weeks, which can be quite a lot. However this depends on how often you data changes. With NFS there is no such issue. Hope this helps, Martin Martin Apel, Dipl.-Inform.t e c m a t h A G Group Manager Software Development Human Solutions Division phone +49 (0)6301 606-300Sauerwiesen 2, 67661 Kaiserslautern fax +49 (0)6301 606-309Germany [EMAIL PROTECTED] http://www.tecmath.com
