Re: no-rewind pass0 on FreeBSD
Does your kernel include device sa? Your tape should be recognized as /dev/.*sa[0-9] For instance : Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: HP C1533A 9503 Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) sa1 at ahc0 bus 0 target 10 lun 0 sa1: SEAGATE AIT 03j0 Removable Sequential Access SCSI-2 device sa1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) Sa0 is included in the Kernel, but the only thing I get is: pass0 at ahc0 bus 0 target 0 lun 0 pass0: HP C7200 140D Removable Changer SCSI-3 device pass0: 3.300MB/s transfers The system recognizes only a passthrough device. Konni
Amanda email - messages
Hi,
we use Amanda version 2.4.2p2 with HP SureStore DLT.
Every night after backup i get an email like this below, where i do not
understand all messages (our company name was replaced by company).
But the backup seems to work fine, and the speed also.
My questions:
1) What does the message about FAILURE AND STRANGE DUMP SUMMARY: mean?
2) What about the message concerning sendbackup and gtar?
3) If i want to eject the tape, it rewinds for about 1 minute. Is that normal or
should amanda rewind the tape to the beginning?
Thank you for your answers,
dalton
- mail begin --
These dumps were to tape B10.
The next tape Amanda expects to use is: B14.
FAILURE AND STRANGE DUMP SUMMARY:
bfs.comany. /var lev 0 STRANGE
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:07
Run Time (hrs:min) 6:02
Dump Time (hrs:min)3:21 3:21 0:00
Output Size (meg) 27867.927867.90.0
Original Size (meg) 43502.543502.50.0
Avg Compressed Size (%)64.1 64.1--
Filesystems Dumped4 4 0
Avg Dump Rate (k/s) 2368.5 2368.5--
Tape Time (hrs:min)3:02 3:02 0:00
Tape Size (meg) 27868.027868.00.0
Tape Used (%) 68.0 68.00.0
Filesystems Taped 4 4 0
Avg Tp Write Rate (k/s) 2607.9 2607.9--
FAILED AND STRANGE DUMP DETAILS:
/-- bfs.comany. /var lev 0 STRANGE
sendbackup: start [bfs.comany.at:/var level 0]
sendbackup: info BACKUP=/bin/tar
sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| gtar: ./log/log: socket ignored
? gtar: ./log/mail: file changed as we read it
| gtar: ./run/ndc: socket ignored
? gtar: ./spool/avmailgate/outgoing/df-02336-341A8055: Warning: Cannot stat: No
such file or directory
? gtar: ./spool/avmailgate/outgoing/qf-02336-341A8055: Warning: Cannot stat: No
such file or directory
| gtar: ./tmp/.mailgate_5.0: socket ignored
| Total bytes written: 2539571200 (2.4GB, 1.9MB/s)
sendbackup: size 2480050
sendbackup: end
\
NOTES:
taper: tape B10 kb 28536864 fm 4 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
bbackup.compa /etc06840 1824 26.7 0:03 582.4 0:04 495.9
bfs.comany.at /etc06860 1824 26.6 0:03 622.7 0:03 557.5
bfs.comany.at /home 0 4205284827369728 65.1 179:082546.5 174:492609.4
bfs.comany.at /var0 24800501163360 46.9 21:34 898.9 7:262605.9
(brought to you by Amanda version 2.4.2p2)
- mail end --
Re: Tapeless backup
Gregor Ibic wrote: Ok, I have done some symlinks to data directories and create a few tapes with amlabel. What you say is very confusing. Why did you create symlinks for? Normally symlinks are not followed when making backups. I create backup, first full and then incremental. It works ok. Apparently it did not work ok, because you seem to miss files. Why did you think it worked ok? Before incremental I add some file to the directory that I backup. Then when I try to recover files I do not get this additional file that is in incremental backup. In index files I can read it, and tha backup was ok, but when listing the disk (setdisk /... and ls) Which index file did you verify? What disk did you backup? Did you issue the correct sethost/setdate command too (if needed?). Did you run many backup runs in one day? Amanda does not yet completely support this (e.g. indexing does not work reliably iirc). I cant get this file listed. Any sugestions? Regards, Gregor -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
config.site
Hello I have configured amanda on a test server . If I modify a parameter in the config.site file , do I have to go through the following steps before the changes are applied : - run ./configure, make , make install ??? Is there a quicker way Thanx in advance M
Re: Amanda email - messages
On Mon, Feb 24, 2003 at 09:47:05AM +0100, Dalton Hubert wrote: Hi, we use Amanda version 2.4.2p2 with HP SureStore DLT. Every night after backup i get an email like this below, where i do not understand all messages (our company name was replaced by company). But the backup seems to work fine, and the speed also. My questions: 1) What does the message about FAILURE AND STRANGE DUMP SUMMARY: mean? You are backing up a very active filesystem. The dump with tar works in two stages, make a list of everything to be backed up, then back it up. Where you get messages about cannot stat, that file was removed between the two stages. Likely it was a temporary file, such as one collecting an incomming mail message, before renaming and placement in a users mailbox. But it could also be a file that someone just happened to rm before tar got a chance to back it up. This situation is one of the reasons tar is generally run with the ignore-failed-read option. Where you get messages about file changed, again the file system was very active and that particular file changed either between the time tar started reading the first byte and finished reading the last byte. The accuracy of that ONE file is definitely suspect. But it should not affect the rest of the backup. I'm not familiar with the socket ignored messages. 2) What about the message concerning sendbackup and gtar? Those are the commands reporting the above events. 3) If i want to eject the tape, it rewinds for about 1 minute. Is that normal or should amanda rewind the tape to the beginning? Amanda rewinds the tape when it needs to. Otherwise it leaves it alone. If you want the tape rewound after amdump, add an mt rewind command to the nightly cron command that runs amdump. FAILED AND STRANGE DUMP DETAILS: /-- bfs.comany. /var lev 0 STRANGE sendbackup: start [bfs.comany.at:/var level 0] sendbackup: info BACKUP=/bin/tar sendbackup: info RECOVER_CMD=/bin/gzip -dc |/bin/tar -f... - sendbackup: info COMPRESS_SUFFIX=.gz sendbackup: info end | gtar: ./log/log: socket ignored ? gtar: ./log/mail: file changed as we read it | gtar: ./run/ndc: socket ignored ? gtar: ./spool/avmailgate/outgoing/df-02336-341A8055: Warning: Cannot stat: No such file or directory ? gtar: ./spool/avmailgate/outgoing/qf-02336-341A8055: Warning: Cannot stat: No such file or directory | gtar: ./tmp/.mailgate_5.0: socket ignored | Total bytes written: 2539571200 (2.4GB, 1.9MB/s) sendbackup: size 2480050 sendbackup: end \ -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Rehberim.de - Is dünyasinin bulustugu adres.
Title: Rehberim.de Please wait Bu mail Spam degildir...Rehberim.de Avrupa'da Turklerin ve Turk Is dunyasinin Ticari ve Mesleki Rehberidir...Bu tur mailleri almak istemiyorsanz, lutfen bize iletin. Verdigimiz rahatsizliktan dolayi ozur dileriz. Remove me from this Email list
Re: no-rewind pass0 on FreeBSD
On Mon, Feb 24, 2003 at 09:23:10AM +0100, Konrad Dienst wrote: Does your kernel include device sa? Your tape should be recognized as /dev/.*sa[0-9] For instance : Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: HP C1533A 9503 Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) sa1 at ahc0 bus 0 target 10 lun 0 sa1: SEAGATE AIT 03j0 Removable Sequential Access SCSI-2 device sa1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) Sa0 is included in the Kernel, but the only thing I get is: pass0 at ahc0 bus 0 target 0 lun 0 pass0: HP C7200 140D Removable Changer SCSI-3 device pass0: 3.300MB/s transfers The system recognizes only a passthrough device. You probably want to start talking to the [EMAIL PROTECTED] mailing list to figure out why you aren't getting a tape device, (sa, sequential access). -- Scott LambertKC5MLE Unix SysAdmin [EMAIL PROTECTED]
rait attempt
I've been playing with rait I haven't been successful yet.
Is rait touchy about the tape drives being identical? My 3rd exb8505 was
dead from the get go so I tried using an ait-1 in it's place.
amlabel amdump seem to run fine, but I cannot get amrestore to pull the
backups off tape. It bypasses
the host/filesystem no matter how I enter it. Even if I leave the host/fs
field blank to restore the entire tape, it skips
right by everything.
I also tried using amdd manually, but tar always complains - typically:
Archive contains obsolescent base-64 headers
After an amlabel, st0 st2 will have the typical am header, while st1
seems to have a blank header. Is that nornal?
st0 = ait; st1,2=exb8505 all on the same scsi bus.
amanda.conf:
tapedev rait:/dev/nst{0,1,2}
define tapetype RAIT1 {
comment RAIT - AIT, 2 8505
length 2 mbytes
filemark 900 kbytes
speed 500 kbytes
}
Thanks
--
toby bluhm
philips medical systems, it support, mr development, cleveland ohio
[EMAIL PROTECTED]
440-483-5323
Re: downgrading
Hum. I thought the same originally as well. But I have about a dozen tapes reacting the same way. Half are new and half are old. I use vxa-1 v17 tapes. I find it unlikely that so many are defective/went bad all together in one shot. What does your experience say? robin On Thu, 20 Feb 2003, Gene Heskett wrote: On Thu February 20 2003 17:50, [EMAIL PROTECTED] wrote: This is what I did at the shell... # Pop in a tape. % mt -f /dev/nst0 rewind % mt -f /dev/nst0 fsf 1 % dd if=/dev/nst0 skip=1 bs=32k | tar tvf - dd: reading `/dev/nst0': Input/output error 0+0 records in 0+0 records out # Let's try another file marker on the same tape. % mt -f /dev/nst0 rewind % mt -f /dev/nst0 fsf 10 # I just want to look at the file header. % dd if=/dev/nst0 count=1 bs=32k AMANDA: FILE 20030213 host1 /boot lev 1 comp N program /bin/gtar To restore, position tape at start of file and run: dd if=tape bs=32k skip=1 | /bin/gtar -f... - 1+0 records in 1+0 records out On the first dd attempt, this showed up in the log: Feb 20 17:30:24 host1 kernel: st0: Error with sense data: Info fld=0x8000, Current st09:00: sense key Medium Error Feb 20 17:30:24 host1 kernel: Additional sense indicates Recorded entity not found I can read the other file markers...except file marker 1. robin This is resembling a bad media error more and more. On Thu, 20 Feb 2003, Jon LaBadie wrote: If I attempt to access file markers greater than 1, I don't have any problems and there are no syslog messages. But if i attempt to access file 1, it keels over and I get messages in syslog. Would you describe what you are doing to access file 1? Give the command line, output, and messages. [This E-mail scanned for viruses by Declude Virus]
tcpserver
Is there any way to make amanda work in standalone mode or with tcpserver? I really do not want to have to install inetd... -- Casey Allen Shobe / Software Developer Linux Administrator SecureWorks, Inc. / 404.327.6339 x169 / Fax: 404.728.0144 [EMAIL PROTECTED] / http://www.secureworks.net Mathematics are a medium mankind created when trying to map existance. -- Valdimar Björn Ásgeirsson
Re: config.site
On Mon February 24 2003 05:50, Madhvi Gokool wrote: Hello I have configured amanda on a test server . If I modify a parameter in the config.site file , do I have to go through the following steps before the changes are applied : - run ./configure, make , make install ??? Is there a quicker way Probably not, and you left out becoming amanda to do the ./configure make, then becoming root to do the make install. You'll likely have all sorts of permissions problems if you don't follow that sequence. Even the unpack should be done as the user amanda. Here, thats less than a 10 minute job even if I go away and do something else more interesting than watching a compile scroll by. And I do it virtually everytime Jean-Louis makes a new snapshot available on his umontreal site, sometimes several times a week. Thanx in advance M [This E-mail scanned for viruses by Declude Virus] -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.23% setiathome rank, not too shabby for a WV hillbilly
Re: downgrading
I had many VXA-1 v17 tapes act this way with amanda with 2 different internal VXA drives. I have also tried an older external drive that never showed the behavior. I have since replace the internal drive with VXA-2 (basically, in order to get more capacity out of the tapes I'm reusing) and the problem has never manifested with the VXA-2 drive. The problem only ever occurred on the first file header; subsequent file headers were ok and I have done restores from the tapes, using mt -f /dev/nst0 rewind mt -f /dev/nst0 fsf 2 amrestore I never did manage to dig to the bottom of the problem. It did not seem to be localized to specific tapes (overwriting a tape could sometimes make the problem go away) On Mon, 24 Feb 2003 [EMAIL PROTECTED] wrote: Hum. I thought the same originally as well. But I have about a dozen tapes reacting the same way. Half are new and half are old. I use vxa-1 v17 tapes. I find it unlikely that so many are defective/went bad all together in one shot. What does your experience say? robin On Thu, 20 Feb 2003, Gene Heskett wrote: On Thu February 20 2003 17:50, [EMAIL PROTECTED] wrote: This is what I did at the shell... # Pop in a tape. % mt -f /dev/nst0 rewind % mt -f /dev/nst0 fsf 1 % dd if=/dev/nst0 skip=1 bs=32k | tar tvf - dd: reading `/dev/nst0': Input/output error 0+0 records in 0+0 records out # Let's try another file marker on the same tape. % mt -f /dev/nst0 rewind % mt -f /dev/nst0 fsf 10 # I just want to look at the file header. % dd if=/dev/nst0 count=1 bs=32k AMANDA: FILE 20030213 host1 /boot lev 1 comp N program /bin/gtar To restore, position tape at start of file and run: dd if=tape bs=32k skip=1 | /bin/gtar -f... - 1+0 records in 1+0 records out On the first dd attempt, this showed up in the log: Feb 20 17:30:24 host1 kernel: st0: Error with sense data: Info fld=0x8000, Current st09:00: sense key Medium Error Feb 20 17:30:24 host1 kernel: Additional sense indicates Recorded entity not found I can read the other file markers...except file marker 1. robin
Re: Problem with compression?
On Fri, Feb 21, 2003 at 05:06:08PM -0800, Jay Lessert wrote: [Posted and Cc'ed] Why? I subscribe... :-) My last posting on this thread, we're in tapeout crunch right now... On Fri, Feb 21, 2003 at 03:43:13PM -0800, John Oliver wrote: No, not really... :-) My tapes are 20GB without compression. I'm telling amanda to use compression. It looks like it's saying it is. And it is, in fact. Therefore, I should be able to get *at least* 20GB on my tapes. You will get exactly 20GB on the tape, after Amanda compression. The tape is 20GB native, 40GB compressed. If amanda is only capable of compressing by 0%, then I would submit that its' compression algorithms either *really* suck, or simply don't work. Since I really doubt that, I would further submit that maybe amanda *isn't* compressing, after all. If you say it is, then I would appreciate an explanation of how compressing 20GB of data to just fit on a 20GB tape is a useful feature. Snipped everything else, since it's based on a debated point of order... :-) -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: no-rewind pass0 on FreeBSD
my kernel config just mentions the sa driver. (no zero or one etc) that way it should detect the sa devices on boot. Once you've got that far you may need to make the /dev/*sa0 devices by cd /dev Makedev sa0 -- Martin Hepworth Senior Systems Administrator Solid State Logic Ltd +44 (0)1865 842300 Scott Lambert wrote: On Mon, Feb 24, 2003 at 09:23:10AM +0100, Konrad Dienst wrote: Does your kernel include device sa? Your tape should be recognized as /dev/.*sa[0-9] For instance : Waiting 5 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 5 lun 0 sa0: HP C1533A 9503 Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) sa1 at ahc0 bus 0 target 10 lun 0 sa1: SEAGATE AIT 03j0 Removable Sequential Access SCSI-2 device sa1: 20.000MB/s transfers (10.000MHz, offset 15, 16bit) Sa0 is included in the Kernel, but the only thing I get is: pass0 at ahc0 bus 0 target 0 lun 0 pass0: HP C7200 140D Removable Changer SCSI-3 device pass0: 3.300MB/s transfers The system recognizes only a passthrough device. You probably want to start talking to the [EMAIL PROTECTED] mailing list to figure out why you aren't getting a tape device, (sa, sequential access). ** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses. www.mimesweeper.com **
Re: Problem with compression?
On Fri, Feb 21, 2003 at 09:10:35PM -0500, Jon LaBadie wrote: On Fri, Feb 21, 2003 at 03:49:32PM -0800, John Oliver wrote: On Fri, Feb 21, 2003 at 06:14:37PM -0500, Gene Heskett wrote: Throw in that marketing is usually a bit optimistic in saying its a 20 gigger without compression, and that always needs a fudge factor when actually estimating, and it likely this will happen. But fudging by 100%? I don't buy that... :-) You don't have to. Gene was only talking about a few percent. No... if my tape is theoretically capable of 20GB uncompressed and 40GB compressed, and after compression amanda can only fit 20GB on it, that would hypothetically demonstrate a 10GB un-compressed capacity. Or, half of what it's actually doing. I do not believe Quantum sells a 10/20 tape drive as a 20/40 I'm sure there *is* some fudging going on, but not, like I said, 100%. I'm apparently loosing about half of the capacity of my tapes, and I'm puzzled why I'm the only one who sees a problem with that... :-) Hopefully, this issue will be resolved in a couple of weeks when I get a DLT7000 library in here. But I would like to understand the basic issue here... I don't want to be limited to 35GB with a unit that should be able to approach 70. -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: Problem with compression?
On Fri, Feb 21, 2003 at 02:42:31PM -0800, Jay Lessert wrote: See also got result in amdump.1, it'll tell you if there's any difference between a level0 and level1 estimate. planner: time 10.451: got result for host backup disk /dev/hda1: 0 - 21156480K, 1 - 19996640K, 2 - 19996600K So it says that all but 1GB of your / has been touched in some way since the last level 0. Assuming this surprises you, then you start checking the output of 'find / -mtime' and 'find / -ctime'. You know what the last level 0 date was (because you checked dumpdates/amandates), For the archives... The sudden jump in the size of this backup was caused when I moved the holdingdisk. It didn't occur to me that I was moving it on to the filesystem I was backing up... :-) I just added /hold to the exclude file. So, backups will shrink dramatically tonight... I'm still interested in finding out what the flaw in my understanding of how amanda handles compression is, though. I'm sure it's something really obvious that I'm an idiot for not seeing, but I still think my tapes should be able to hold more than 20GB when compression is being used. -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
tapeless backup
I've posted this a few days ago, but I guess it slipped through the
list. Here I post it again.
I need to backup the first drive to the second hard drive on the same
machine (client + server), but encounter this when running amdump.
Here're the config. and the error mail
Thank you
==
#
# amanda.conf
org testSet # organization name for reports
mailto [EMAIL PROTECTED]# operators at your site
dumpuser amanda # the user to run dumps under
inparallel 3# maximum dumpers that will run in parallel
netusage 600 kbps # maximum net bandwidth for Amanda, in KB per sec
# our local network can provide up to 100MB/s
dumpcycle 1 day # the number of day in the normal dump cycle
runspercycle 1 day # the number of amdump runs in dumpcycle days
tapecycle 2
runtapes 1
bumpsize 20 Mb # minimum savings (threshold) to bump level 1 - 2
bumpdays 1 # minimum days at each level
bumpmult 4 # threshold = bumpsize * bumpmult^(level-1)
ctimeout 300
etimeout 300# number of seconds per filesystem for estimates.
reserve 10
tapetype HARD-DISK
labelstr ^testSet[0-9][0-9]*$ # label constraint regex:
# all tapes must match
tpchanger chg-multi
changerfile /usr/etc/amanda/testSet/changer.conf
tapedev file:/home/general/backup
define tapetype HARD-DISK {
comment Dump onto hard disk
length 10 gbytes# these numbers are not accurate
}
infofile /usr/etc/amanda/amandalog/testSet/curinfo # database
logdir /usr/etc/amanda/amandalog/testSet # log
indexdir /usr/etc/amanda/amandalog/testSet/index# index
define dumptype global {
comment Global definitions
index yes
record yes
}
define dumptype hard-disk-dump {
global
comment Back up to hard disk - dump
holdingdisk no
priority high
}
define dumptype hard-disk-tar {
hard-disk-dump
comment Back up to hard disk - tar
program GNUTAR
}
define dumptype hard-disk-tar-full {
hard-disk-dump
compress none
dumpcycle 0
}
# network interfaces
#
define interface local {
comment a local disk
use 1000 kbps
}
define interface eth0 {
comment 10 Mbps ethernet
use 400 kbps
}
#
# changer.conf
multieject 0
gravity 0
needeject 0
ejectdelay 0
statefile /usr/etc/amanda/testSet/changer.stat
firstslot 1
lastslot 1
slot 1 file:/home/general/backup/t1
#
# disklist
#
# File format is:
#
# hostname diskdev dumptype
#
# where the dumptypes are defined by you in amanda.conf.
## note: -1 is a placeholder for the spindle number
## the holding disk can't be dumped to itself, it uses a disktype that
## specifies the no-hold option (see amanda.conf).
linux /Mail hard-disk-tar-full -1 local
#
# .amandahosts
localhost amanda
linux amanda
#
# email error
-- Forwarded message --
Date: Mon, 24 Feb 2003 10:32:00 -0800
From: Amanda [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: testSet AMANDA MAIL REPORT FOR February 24, 2003
*** A TAPE ERROR OCCURRED: [new tape not found in rack].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
lnx200 /Mail lev 0 FAILED [can't switch to incremental dump]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
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 lnx200:/Mail.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
lnx200 /Mail 0 FAILED ---
(brought to you by Amanda version 2.4.2p1)
tapeless backup again
I've posted this a few days ago, but I guess it slipped through the
list. Here I post it again.
I need to backup the first drive to the second hard drive on the same
machine (client + server), but encounter this when running amdump.
Here're the config. and the error mail
Thank you
Sorry for possibly confusing you, the name lnx200 and linux are
equivalent. I just changed it to make it more readable, and obviously
forgot to change all.
==
#
# amanda.conf
org testSet# organization name for reports
mailto [EMAIL PROTECTED]# operators at your site
dumpuser amanda# the user to run dumps under
inparallel 3# maximum dumpers that will run in parallel
netusage 600 kbps# maximum net bandwidth for Amanda, in KB per sec
# our local network can provide up to 100MB/s
dumpcycle 1 day# the number of day in the normal dump cycle
runspercycle 1 day # the number of amdump runs in dumpcycle days
tapecycle 2
runtapes 1
bumpsize 20 Mb# minimum savings (threshold) to bump level 1 - 2
bumpdays 1# minimum days at each level
bumpmult 4# threshold = bumpsize * bumpmult^(level-1)
ctimeout 300
etimeout 300# number of seconds per filesystem for estimates.
reserve 10
tapetype HARD-DISK
labelstr ^testSet[0-9][0-9]*$# label constraint regex:
# all tapes must match
tpchanger chg-multi
changerfile /usr/etc/amanda/testSet/changer.conf
tapedev file:/home/general/backup
define tapetype HARD-DISK {
comment Dump onto hard disk
length 10 gbytes# these numbers are not accurate
}
infofile /usr/etc/amanda/amandalog/testSet/curinfo# database
logdir /usr/etc/amanda/amandalog/testSet# log
indexdir /usr/etc/amanda/amandalog/testSet/index# index
define dumptype global {
comment Global definitions
index yes
record yes
}
define dumptype hard-disk-dump {
global
comment Back up to hard disk - dump
holdingdisk no
priority high
}
define dumptype hard-disk-tar {
hard-disk-dump
comment Back up to hard disk - tar
program GNUTAR
}
define dumptype hard-disk-tar-full {
hard-disk-dump
compress none
dumpcycle 0
}
# network interfaces
#
define interface local {
comment a local disk
use 1000 kbps
}
define interface eth0 {
comment 10 Mbps ethernet
use 400 kbps
}
#
# changer.conf
multieject 0
gravity 0
needeject 0
ejectdelay 0
statefile /usr/etc/amanda/testSet/changer.stat
firstslot 1
lastslot 1
slot 1 file:/home/general/backup/t1
#
# disklist
#
# File format is:
#
#hostname diskdev dumptype
#
# where the dumptypes are defined by you in amanda.conf.
## note: -1 is a placeholder for the spindle number
## the holding disk can't be dumped to itself, it uses a disktype that
## specifies the no-hold option (see amanda.conf).
linux /Mail hard-disk-tar-full -1 local
#
# .amandahosts
localhostamanda
linuxamanda
#
# email error
-- Forwarded message --
Date: Mon, 24 Feb 2003 10:32:00 -0800
From: Amanda [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: testSet AMANDA MAIL REPORT FOR February 24, 2003
*** A TAPE ERROR OCCURRED: [new tape not found in rack].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.
FAILURE AND STRANGE DUMP SUMMARY:
linux /Mail lev 0 FAILED [can't switch to incremental dump]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:00
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 linux:/Mail.
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
linux /Mail 0 FAILED ---
(brought to you by Amanda version 2.4.2p1)
Re: Problem with compression?
On Mon, Feb 24, 2003 at 10:03:53AM -0800, John Oliver wrote: Hopefully, this issue will be resolved in a couple of weeks when I get a DLT7000 library in here. But I would like to understand the basic issue here... I don't want to be limited to 35GB with a unit that should be able to approach 70. OK, the basics are that a tape only holds enough bits and bytes as its native capacity. You keep thinking of USER DATA. After compression there are fewer bytes, but amanda has to measure what it puts on tape. And that can be NO MORE THAN 20 GB for your tape. Any number you see higher than that is post-compression and if amanda is compressing, which your earlier reports showed it was, then amanda is measuring, and reporting, what is acutally being put on tape. You reports will also show orig size, but the taper part doesn't care about that, it only knows what it was asked to put on tape -- ie post-compression. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Problem with compression?
On Mon February 24 2003 13:03, John Oliver wrote:
On Fri, Feb 21, 2003 at 09:10:35PM -0500, Jon LaBadie wrote:
On Fri, Feb 21, 2003 at 03:49:32PM -0800, John Oliver wrote:
On Fri, Feb 21, 2003 at 06:14:37PM -0500, Gene Heskett wrote:
Throw in that marketing is usually a bit optimistic in
saying its a 20 gigger without compression, and that always
needs a fudge factor when actually estimating, and it likely
this will happen.
But fudging by 100%? I don't buy that... :-)
You don't have to. Gene was only talking about a few percent.
No... if my tape is theoretically capable of 20GB uncompressed and
40GB compressed, and after compression amanda can only fit 20GB
on it, that would hypothetically demonstrate a 10GB un-compressed
capacity. Or, half of what it's actually doing. I do not
believe Quantum sells a 10/20 tape drive as a 20/40 I'm sure
there *is* some fudging going on, but not, like I said, 100%.
I'm apparently loosing about half of the capacity of my tapes,
and I'm puzzled why I'm the only one who sees a problem with
that... :-)
Hopefully, this issue will be resolved in a couple of weeks when I
get a DLT7000 library in here. But I would like to understand
the basic issue here... I don't want to be limited to 35GB with a
unit that should be able to approach 70.
John, I thnk we might have a language problem here. When you say
amanda only wrote 20 gigs, how are you determining that? Let me
clip in a couple of lines from last nights run report here to
demonstrate:
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:23
Run Time (hrs:min) 2:28
Dump Time (hrs:min)0:58 0:39 0:19
Output Size (meg)2252.6 2060.9 191.7
Original Size (meg) 4520.0 4004.7 515.3
Avg Compressed Size (%)49.0 51.5 26.8
(level:#disks ...)
Filesystems Dumped 35 2 33 (1:31 2:1
3:1)
Avg Dump Rate (k/s) 664.2 913.3 169.0
---
The Output size is the actual, written to tape, byte count. In your
case, you appeared to hit EOT at 20 gigs after amanda's
compression. Thats correct. Now note the Original size value
and the compression ratio achieved. My tapes are dds2's or a hair
less than 4gigs in real capacity. I have seen, when what it was
backing up was much more compressable than on this particular run,
figures in excess of 10 gigs there a time or 3. I was also running
a dumpcycle one day shorter than now at the time, just to push
amanda to the wall and see what she would do, and IMO she did right
well.
--
Cheers, Gene
AMD [EMAIL PROTECTED] 320M
[EMAIL PROTECTED] 512M
99.23% setiathome rank, not too shabby for a WV hillbilly
Re: Problem with compression?
--On Monday, February 24, 2003 10:03:53 -0800 John Oliver [EMAIL PROTECTED] wrote: On Fri, Feb 21, 2003 at 09:10:35PM -0500, Jon LaBadie wrote: On Fri, Feb 21, 2003 at 03:49:32PM -0800, John Oliver wrote: On Fri, Feb 21, 2003 at 06:14:37PM -0500, Gene Heskett wrote: Throw in that marketing is usually a bit optimistic in saying its a 20 gigger without compression, and that always needs a fudge factor when actually estimating, and it likely this will happen. But fudging by 100%? I don't buy that... :-) You don't have to. Gene was only talking about a few percent. No... if my tape is theoretically capable of 20GB uncompressed and 40GB compressed, and after compression amanda can only fit 20GB on it, that would hypothetically demonstrate a 10GB un-compressed capacity. Or, half of what it's actually doing. I do not believe Quantum sells a 10/20 tape drive as a 20/40 I'm sure there *is* some fudging going on, but not, like I said, 100%. I'm apparently loosing about half of the capacity of my tapes, and I'm puzzled why I'm the only one who sees a problem with that... :-) The only capacity number that matters on a tape is the raw 'uncompressed' capacity. The 'compressed' numbers are just a marketing ploy to make the tape capacity seem higher. Yes, some data will compress nicely, giving you the appearance of writing 40 or even 60 GB to that tape, but you are still only writing 20 GB of ones and zeroes to the tape. If you are backing up filesystems with mostly uncompressible data, then the amount of disk space used will approximate the amount of tape used, or possibly be even larger on tape if you try to compress already compressed data. I have one 5.4GB directory that is 5.3GB compressed, but a 6.2GB directory I have only uses 2.6GB compressed. Depending on your data you could get anywhere from 20 to 100 GB on that same tape, with the odds much greater of being near the low end of that range rather than the high end. Frank -- Frank Smith [EMAIL PROTECTED] Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: Problem with compression?
On Monday, February 24, 2003, at 01:03 PM, John Oliver wrote: On Fri, Feb 21, 2003 at 09:10:35PM -0500, Jon LaBadie wrote: On Fri, Feb 21, 2003 at 03:49:32PM -0800, John Oliver wrote: On Fri, Feb 21, 2003 at 06:14:37PM -0500, Gene Heskett wrote: Throw in that marketing is usually a bit optimistic in saying its a 20 gigger without compression, and that always needs a fudge factor when actually estimating, and it likely this will happen. But fudging by 100%? I don't buy that... :-) You don't have to. Gene was only talking about a few percent. No... if my tape is theoretically capable of 20GB uncompressed and 40GB compressed, and after compression amanda can only fit 20GB on it, that would hypothetically demonstrate a 10GB un-compressed capacity. Or, half of what it's actually doing. I do not believe Quantum sells a 10/20 tape drive as a 20/40 I'm sure there *is* some fudging going on, but not, like I said, 100%. I'm apparently loosing about half of the capacity of my tapes, and I'm puzzled why I'm the only one who sees a problem with that... :-) U if you are using server compression, then you (hopefully) have hardware compression turned off. If not, then you're wasting space. However, if you have hardware compression turned off, then the tape itself will store 20Gigs. Even if you have hardware compression turned on, the likelihood that you will be able to actually get 40Gigs of data onto it is vanishingly small. So, you have a tape that holds 20Gigs. Now, Amanda is compressing the data on the server. So, you have two figures -- the amount of data that Amanda receives, uncompressed, and the amount that Amanda writes out to the tape, compressed. Because there is no hardware compression enabled (and mixing software and hardware compression is _bad_), the tape drive will only write 20Gigs of data. The 20Gigs that you see Amanda writing to tape is the 20Gigs that the tape will hold. This happens to be already compressed data, but the tape knows nothing about that. Now, from what I remember, the problem is that you manage to write about 9Gigs of (already compressed, uncompressed it was closer to 14-19 gigs -- I'm not looking at the report right now) data out to the tape. This leaves another 11-odd. The next dump it tried to write to disk didn't compress at all well -- ie, it was something like 12Gigs of data, that even _after_ being compressed, was still something like 12Gigs. So, Amanda tries to write out 12Gigs to an 11Gig space, and fails. Note that, had it succeeded, the uncompressed data being stored on tape would have been close to 30Gigs -- the ~12Gigs of the last entry, plus the uncompressed ~15-19 gigs of the previous entries. HTH, Ricky
Re: tapeless backup
On Mon, Feb 24, 2003 at 10:51:06AM -0800, bao wrote: I've posted this a few days ago, but I guess it slipped through the list. Here I post it again. I need to backup the first drive to the second hard drive on the same machine (client + server), but encounter this when running amdump. Here're the config. and the error mail Thank you [[ snip ]] tapedev file:/home/general/backup [[ snip ]] (brought to you by Amanda version 2.4.2p1) This may be your problem. The file driver did not exist for 2 years after that amanda version. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
[no subject]
Has anyone seen a situation in which amcheck succeeds yet amdump fails with the following: FAILURE AND STRANGE DUMP SUMMARY: mail /home lev 2 FAILED [could not connect to mail] mail /var/spool/mail lev 2 FAILED [could not connect to mail] I know that this is an iptables problem. Because if I turn off iptables the dump succeeds. I have destination ports 10080 - 10083 open to the server for both udp and tcp packets in my iptables on the client: target prot opt source destination ACCEPT tcp -- cosmic.cosmic.ucar.edu mail.cosmic.ucar.edu tcp \ dpt:amanda ACCEPT tcp -- cosmic.cosmic.ucar.edu mail.cosmic.ucar.edu tcp \ dpt:kamanda ACCEPT tcp -- cosmic.cosmic.ucar.edu mail.cosmic.ucar.edu tcp \ dpt:amandaidx ACCEPT tcp -- cosmic.cosmic.ucar.edu mail.cosmic.ucar.edu tcp \ dpt:amidxtape ACCEPT udp -- cosmic.cosmic.ucar.edu mail.cosmic.ucar.edu udp \ dpt:amanda ACCEPT udp -- cosmic.cosmic.ucar.edu mail.cosmic.ucar.edu udp \ dpt:kamanda ACCEPT udp -- cosmic.cosmic.ucar.edu mail.cosmic.ucar.edu udp \ dpt:10082 ACCEPT udp -- cosmic.cosmic.ucar.edu mail.cosmic.ucar.edu udp \ dpt:10083 I am using a RedHat 7.2 amanda Server: amanda-server-2.4.2p2-4 on RedHat 7.2 And a RedHat 8.0 amanda Client: amanda-client-2.4.2p2-9 on RedHat 8.0 Possibly someone can guide me to getting more debug info. The logs just have lines like this: Feb 24 10:14:13 mail xinetd[8852]: START: amanda pid=32616 \ from=10.0.0.108 Mail is the host name of the client and 10.0.0.108 is the server.) Thanks. -- Dr. Karl Hudnut System Administrator UCAR - COSMIC [EMAIL PROTECTED] http://www.cosmic.ucar.edu303 497 8024
[no subject]
info help end -- Dr. Karl Hudnut System Administrator UCAR - COSMIC [EMAIL PROTECTED] http://www.cosmic.ucar.edu303 497 8024
Re: Problem with compression?
On Mon, Feb 24, 2003 at 02:27:18PM -0500, Matt Hyclak wrote: You're getting your math confused, I think. If your tapetype defines compression, then what is in your holding disk is already compressed. Your tape drive should be in non-compression mode then and should hold 20GB of *already compressed* data. What space that data takes up when uncompressed should be close to 40GB, but depends on how well it compressed. If I remember correctly, amanda had already written about 10GB of *already compressed* data to the drive, and was then trying to write a 20GB *uncompressed* partition after that. Amanda thought that the 20GB would compress to 10GB and therefore fit on the 20GB capacity tape, but she was wrong. So, if she had been able to get it all on there, you would have had about 20GB of already compressed data, which would expand to about 40GB when uncompressed. OK, now *here's* an explanation that made its' way through my thick skull! :-) Thanks, Matt. I'm not sure if I fell more or less stupid now... :-) -- John Oliver, CCNAhttp://www.john-oliver.net/ Linux/UNIX/network consulting http://www.john-oliver.net/resume/ *** sendmail, Apache, ftp, DNS, spam filtering *** Colocation, T1s, web/email/ftp hosting
Re: your mail
On Mon, 24 Feb 2003 at 1:52pm, Karl Hudnut wrote Has anyone seen a situation in which amcheck succeeds yet amdump fails with the following: FAILURE AND STRANGE DUMP SUMMARY: mail /home lev 2 FAILED [could not connect to mail] mail /var/spool/mail lev 2 FAILED [could not connect to mail] I know that this is an iptables problem. Because if I turn off iptables the dump succeeds. I have destination ports 10080 - 10083 open to the server for both udp and tcp packets in my iptables on the client: You need more than that. Look in docs/PORT.USAGE for details on how amanda allocates ports. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Binding amanda to specific interface
[ On Sunday, February 23, 2003 at 23:14:37 (-0500), Mark Radabaugh wrote: ] Subject: Binding amanda to specific interface I'm trying to run Amanda on FreeBSD on a machine with multiple IP's bound to the ethernet interface. Amanda seems to insist on picking the alias interface rather than the primary interface and there doesn't seem to be a switch to control the behaviour. If you're talking about the listening side, well Amanda itself doesn't listen on any sockets -- that's done by inetd and on FreeBSD you have to have separate inetd instances listening on each different IP#. As for the local addresses chosen for outgoing connections, well normally the kernel makes the right choice depending on your routing table -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]
Re: Problem with compression?
On Mon, Feb 24, 2003 at 10:43:12AM -0800, John Oliver wrote: The sudden jump in the size of this backup was caused when I moved the holdingdisk. It didn't occur to me that I was moving it on to the filesystem I was backing up... :-) I just added /hold to the exclude file. So, backups will shrink dramatically tonight... Yeah, that would do it... I'm still interested in finding out what the flaw in my understanding of how amanda handles compression is, though. I'm sure it's something really obvious that I'm an idiot for not seeing, but I still think my tapes should be able to hold more than 20GB when compression is being used. A tape with a raw capacity of 20G can hold no more than 20G of data. Period. amanda has nothing to do with this and it cannot be changed except by buying a tape drive which is capable of (reliably) writing data to the tape at a higher density than the tape was designed for. However, the 20G of data that amanda writes is 20G of compressed data, which will generally expand to substantially more than 20G of uncompressed data. The communication problem here appears to be that, when others on the list are talking about the compressed size of the data, you're interpreting it as the uncompressed size.
Re: your mail
CCed back to the list for the archives... On Mon, 24 Feb 2003 at 3:01pm, Karl Hudnut wrote Thanks for your help. I don't seem to have that documentation in any of the rpms I have here. It doesn's seem to be in the tarballs from amanda.org either. Can you help me find it? ?? I just downloaded amanda-2.4.3.tar.gz via the link http://prdownloads.sourceforge.net/amanda/amanda-2.4.3.tar.gz?download on http://www.amanda.org/download.html and there's an entire directory in there called 'docs'. I also wonder if you have any comment on amcheck succeeding and amdump failing. Amcheck just connects to the amandad port (UDP 10080) on the client. It doesn't check that the client can actually open the TCP connections back to the server. Grepping through my own mail archives, here's a summary of port usage I posted back in 2001: The amanda server sends a UDP sendbackup request from a privileged port (not necessarily the same one as above) to port 10080 on the client. The amanda client sends a UDP ACK from port 10080 to the originating privileged port on the server. It then sends another one containing the numbers of three (non-privileged) TCP ports to set up the data, message, and index connections. The amanda server sends a UDP ACK from the privileged port to port 10080 on the client. The amanda server then initiates three TCP connections on the ports indicated in the UDP packet from the client. These are on unprivileged ports on both systems. The dumper on the client then proceeds to start sending date over the TCP connections. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
amrecover and changer with amanda-2.4.4b1
Hi I have seen something very interesting on the changelog of amanda2.4.4b1 it s the ability of amrecover ( and related servers ) to use the changer. i have setup successfully amanda with a tapeless configuration with the chg-multi script. then i m trying to configure the amrecover to use the the changer here s the related portion of file on my configuration amrecover_do_fsf yes amrecover_check_label yes # amrecover will call amrestore with the amrecover_changer changer but when i launch amrecover i got the following error Extracting files using tape drive changer on host backup.int-evry.fr. Load tape DSK05 now Continue [?/Y/n/s/t]? Y EOF, check amidxtaped.debug file on backup.int-evry.fr. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue [?/Y/n/r]? r when i look at amidxtaped.debug i see amidxtaped: time 0.351: HEADER amidxtaped: time 0.351: DEVICE=changer amidxtaped: time 0.351: HOST=^molure$ amidxtaped: time 0.351: DISK=^/var/spool/imap1$ amidxtaped: time 0.351: DATESTAMP=20030223 amidxtaped: time 0.351: END amidxtaped: time 0.351: config 'testdisk' valeur DSK05: label 'changer' not found changer: got exit: 0 str: 5 7 1 changer_query: changer return was 7 1 changer_query: searchable = 0 changer_find: looking for DSK05 changer is searchable = 0 changer: got exit: 0 str: 5 file:/var/lib/backuppc/amanda/t5 amidxtaped: time 0.438: slot 5: date 20030223 label DSK05 (exact label match) amidxtaped: time 0.438: label DSK05 found amidxtaped: time 0.438: amrestore_nargs=0 amidxtaped: time 0.438: Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = amrestore argv[1] = -p argv[2] = -h argv[3] = -l argv[4] = DSK05 argv[5] = -f argv[6] = 16 argv[7] = changer argv[8] = ^molure$ argv[9] = ^/var/spool/imap1$ argv[10] = 20030223 amrestore: could not stat changer: No such file or directory It seems that the changer give the device to use but the daemon amidxtaped didn't used that value. is it supported or should i modify the code to make it work? Thanks in advance. -- Eric Doutreleau I.N.T | Tel : +33 (0) 160764687 9 rue Charles Fourier | Fax : +33 (0) 160764321 91011 Evry France | email : [EMAIL PROTECTED]
Re: your mail
Joshua: You are correct, there is a docs directory in the 2.4.3 tarball and it has the PORTS.USAGE document. Thanks again. And sorry for disseminating missinformation. -- Dr. Karl Hudnut System Administrator UCAR - COSMIC [EMAIL PROTECTED] http://www.cosmic.ucar.edu303 497 8024 On Mon, 24 Feb 2003, Joshua Baker-LePain wrote: CCed back to the list for the archives... On Mon, 24 Feb 2003 at 3:01pm, Karl Hudnut wrote Thanks for your help. I don't seem to have that documentation in any of the rpms I have here. It doesn's seem to be in the tarballs from amanda.org either. Can you help me find it? ?? I just downloaded amanda-2.4.3.tar.gz via the link http://prdownloads.sourceforge.net/amanda/amanda-2.4.3.tar.gz?download on http://www.amanda.org/download.html and there's an entire directory in there called 'docs'. I also wonder if you have any comment on amcheck succeeding and amdump failing. Amcheck just connects to the amandad port (UDP 10080) on the client. It doesn't check that the client can actually open the TCP connections back to the server. Grepping through my own mail archives, here's a summary of port usage I posted back in 2001: The amanda server sends a UDP sendbackup request from a privileged port (not necessarily the same one as above) to port 10080 on the client. The amanda client sends a UDP ACK from port 10080 to the originating privileged port on the server. It then sends another one containing the numbers of three (non-privileged) TCP ports to set up the data, message, and index connections. The amanda server sends a UDP ACK from the privileged port to port 10080 on the client. The amanda server then initiates three TCP connections on the ports indicated in the UDP packet from the client. These are on unprivileged ports on both systems. The dumper on the client then proceeds to start sending date over the TCP connections. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Spam/Bounce-Mail
Hallo, first I say sorry for your trouble with my bounce-mails. This weekend I setup my new Mail-Backupserver. After this work I test a new version of my Spamcheck-script. In this script I call rblcheck. My mistake was the test via list.dsbl.org. The big prob by my was that the powerline from my Primaryserver going offline. So the Backup-Server works with the bad script. Sorry Joerg -- Jörg Frings-Fürst 54526 Landscheid http://www.fixundfoxi.dyndns.info -- Registered Linux User # 280687 ICQ 170365098 GPG Key ID : EB8A FFC8 1314 12E1
RE: tcpserver
Well, I'm using xinetd as a (hopefully) temporary solution. The security issues are my primary concern for not wanting to use it. I prefer to run everything as a standalone daemon if possible (i.e. sshd, httpd, xfs, etc.). xinetd was easy enough to get working though, and I've currently got Amanda working as a client on my server. I knew that Amanda used UDP, so that's why I wasn't sure about the tcpserver (http://cr.yp.to/ucspi-tcp/tcpserver.html) solution... I also remember seeing a udpserver (based on tcpserver I think) months ago somewhere, but I'm not sure of it's maturity, and can't seem to find it now. As mentioned, I've got a working setup now, but would be very interested in hearing any possible alternatives to *inetd. The host system is linux. Thanks! -- Casey Allen Shobe / Software Developer Linux Administrator SecureWorks, Inc. / 404.327.6339 x169 / Fax: 404.728.0144 [EMAIL PROTECTED] / http://www.secureworks.net Mathematics are a medium mankind created when trying to map existance. -- Valdimar Björn Ásgeirsson -Original Message- From: Greg A. Woods [mailto:[EMAIL PROTECTED] Sent: 24. febrúar 2003 22:51 To: Joshua Baker-LePain Cc: Casey Shobe; [EMAIL PROTECTED] Subject: Re: tcpserver [ On Monday, February 24, 2003 at 12:37:47 (-0500), Joshua Baker-LePain wrote: ] Subject: Re: tcpserver On Mon, 24 Feb 2003 at 11:50am, Casey Shobe wrote Is there any way to make amanda work in standalone mode or with tcpserver? I really do not want to have to install inetd... xinetd works quite well Perhaps for some folks, but certianly not for all! Note also that for all intents and proposes xinetd is an inetd. and is much more secure than inetd. I seriously doubt that. In fact I believe there's ample proof to the contrary with several security advisories against xinetd and none that I'm aware of against at least the *BSD inetds. Also note that most (all?) of the *BSD inetds include integrated hooks to TCP Wrappers. Finally note that Amanda doesn't just use TCP -- it also uses UDP and you really can't use libwrap effectively on most UDP services. -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]
Re: Binding amanda to specific interface
BTW, it's not really that hard at all to keep your reverse DNS fully consistent for multi-homed hosts reachable on multiple subnets, though of course it does help to have a well considered naming plan. -- Greg A. Woods The problem is the forward lookup rather than the reverse DNS. If you give 2 different IP addresses to the same hostname BIND will round-robin the 2 addresses - returning the first address on one query and the second on the next. I think the simplest way to solve this is to go ahead and change the IP address of the client to the new IP address since it doesn't appear that Amanda has a switch to force the source address. I have to break down and do it one of these days anyway :-) Mark Radabaugh Amplex (419) 720-3635
Re: Binding amanda to specific interface
BTW, it's not really that hard at all to keep your reverse DNS fully consistent for multi-homed hosts reachable on multiple subnets, though of course it does help to have a well considered naming plan. -- Greg A. Woods The problem is the forward lookup rather than the reverse DNS. If you give 2 different IP addresses to the same hostname BIND will round-robin the 2 addresses - returning the first address on one query and the second on the next. I think the simplest way to solve this is to go ahead and change the IP address of the client to the new IP address since it doesn't appear that Amanda has a switch to force the source address. I have to break down and do it one of these days anyway :-) Mark Radabaugh Amplex (419) 720-3635
release of amanda-2.4.4
Hello, The Amanda core team is pleased to announce the release of Amanda 2.4.4. It is the latest stable release of amanda. It can be dowloaded from http://www.amanda.org/ Here's a list of the changes for release 2.4.4 (from the NEWS file): Look at the ChangeLog file for more details. * New -a option to amcheck to always send an email. * maxpromoteday: New option for a dumptype. * New amtapetype program (replace tapetype) * Client compile on CYGWIN * amrestore -f fileno : amrestore can do fsf before reading the tape * amrestore -l label : amrestore can check the label before restoring. * New config options: amrecover_do_fsf: Amrecover will use the -f flag of amrestore to position the tape. amrecover_check_label: amrecover will pass the -l flag to amrestore. amrecover_changer: amrecover will use your changer. maxdumpsize: The maximum size of the dumps during a run, default to tapesize * runtapes taperalgo: select your algo for the taper, try 'largestfit', it can improve tape usage. * amrecover allow to retry a skip a tape. * New --days option to 'amadmin config balance' command. * New --date option to amstatus * amreport print an usage by tape. * Newer promote algorithm that try to reduce the number of full on a single host in a run. * New changer: chg-juke, chg-null and chg-rait -- 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
linux, lvm, and snapshots
I was thinking about backing up using snapshots. Is there any best-practices way to do this cleanly? I was going to just script the lvcreate/lvremove stuff around the amdump, but figured someone may have a more comprehensive approach. -- -rupa
Re: Binding amanda to specific interface
[ On Monday, February 24, 2003 at 20:09:07 (-0500), Mark Radabaugh wrote: ] Subject: Re: Binding amanda to specific interface The problem is the forward lookup rather than the reverse DNS. If you give 2 different IP addresses to the same hostname BIND will round-robin the 2 addresses - returning the first address on one query and the second on the next. That still shouldn't be a problem. I ran amanda on a network that was multi-homed with two IP subnets on the same ethernet for a very long time and had no problem with it (using ~/.amandahosts). -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]
RE: tcpserver
[ On Monday, February 24, 2003 at 19:36:46 (-0500), Casey Shobe wrote: ] Subject: RE: tcpserver Well, I'm using xinetd as a (hopefully) temporary solution. The security issues are my primary concern for not wanting to use it. I prefer to run everything as a standalone daemon if possible (i.e. sshd, httpd, xfs, etc.). xinetd was easy enough to get working though, and I've currently got Amanda working as a client on my server. I don't know what kind of security you might be talking about, but for most purposes running one master internet daemon to handle all incoming service requests actually has a large number of fairly important security related advantages. I also remember seeing a udpserver (based on tcpserver I think) months ago somewhere, but I'm not sure of it's maturity, and can't seem to find it now. Maturity? What's that got to do with it? There are fundamental conceptual problems with trying to do what TCP Wrappers does with a datagram based server. You have to change your whole way of thinking about these things when you use connection-oriented services or even pseudo-connection style UDP servers. Maturity of fundamentally mis-concieved ideas doesn't help any. :-) If you really want to secure amanda then make sure your border firewalls all block traffic to all the ports where you run Amanda on. You could go one further by building an entirely separate and private subnet with separate physical interfaces to all your important servers and run Amanda only on that private network. That's what I do for my clients. As mentioned, I've got a working setup now, but would be very interested in hearing any possible alternatives to *inetd. The host system is linux. I have a version of *BSD inetd that's been gone over with a fairly fine-toothed comb and which may actually be portable enouch to build and work on linux -- Greg A. Woods +1 416 218-0098;[EMAIL PROTECTED]; [EMAIL PROTECTED] Planix, Inc. [EMAIL PROTECTED]; VE3TCP; Secrets of the Weird [EMAIL PROTECTED]
