Trouble tar'ing large filesystems
Hi I backup onto DDS-2 tapes, so have a limitation of about 3-4GB per tape. The no of tapes is set to 2, so I should be able to backup 6-8GB per run. However, I am unable to tar a single filesystem that is larger than the predicted size of one tape. When I try, I get the error: planner: localhost /home 20030115 0 [dump larger than tape, full dump delayed] The blocksize is set to 499MB, so surely amanda should tar in 499MB blocks until it has done the whole filesystem and then dump it onto 2 tapes. Gareth
Re: Trouble tar'ing large filesystems
amanda cannot backup filesystems that are larger than the size of the tapes, it cannot split backup streams across multiple tapes. Steve Hi I backup onto DDS-2 tapes, so have a limitation of about 3-4GB per tape. The no of tapes is set to 2, so I should be able to backup 6-8GB per run. However, I am unable to tar a single filesystem that is larger than the predicted size of one tape. When I try, I get the error: planner: localhost /home 20030115 0 [dump larger than tape, full dump delayed] The blocksize is set to 499MB, so surely amanda should tar in 499MB blocks until it has done the whole filesystem and then dump it onto 2 tapes. Gareth
Re: Trouble tar'ing large filesystems
Hi, that is one of the limitations at the moment: amanda can not spann a single archiv over multiple tapes. You'll have to use exlucelists to split your big partition into multiple smaler ones, preferably smaler than half of the capacity of a single tape. Christoph [EMAIL PROTECTED] schrieb: Hi I backup onto DDS-2 tapes, so have a limitation of about 3-4GB per tape. The no of tapes is set to 2, so I should be able to backup 6-8GB per run. However, I am unable to tar a single filesystem that is larger than the predicted size of one tape. When I try, I get the error: planner: localhost /home 20030115 0 [dump larger than tape, full dump delayed] The blocksize is set to 499MB, so surely amanda should tar in 499MB blocks until it has done the whole filesystem and then dump it onto 2 tapes. Gareth
amrestore problems after replacing tape drive
Hello! Please CC: any possible replies to me. I sent subscribe request a couple of hours ago, but nothing seems to have happened yet. I'm running Amanda 2.4.3b4 on FreeBSD 4.7. And yes, I understand that 'b' means beta. Yesterday I replaced the tape drive in the backup server. The old drive was HP C1537A (DDS3). The new drive is IBM DDS4, actually a re-badged Seagate 0624 drive. I also started using DDS4 tapes. I made no changes to any configuration files (yet). I'm using dump and restore as the backup software. The drive is set to do hardware compression. The backup ran for the first time tonight. The output that amdump sent me after the backup looked entirely normal, and also I could restore some files from the tape with amrecover. However, amverify is not happy (see output at the end of message). When I tried running amrestore directly from the command line, the following happened: kuller# amrestore /dev/nsa0 kuller.raad.tartu.ee / amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information kuller# The messages are returned immediately, without any kind of delay I imagined would be involved in dealing with the tape drive. I ran 'mt status' and got the following: kuller# mt status Mode Density Blocksize bpi Compression Current: 0x26:DDS-4 1024 bytes 97000DCLZ -available modes- 0:0x26:DDS-4 1024 bytes 97000DCLZ 1:0x26:DDS-4 1024 bytes 97000DCLZ 2:0x26:DDS-4 1024 bytes 97000DCLZ 3:0x26:DDS-4 1024 bytes 97000DCLZ - Current Driver State: at rest. - File Number: 0 Record Number: 64 Residual Count 0 kuller# It seems that my tape drive uses 1k blocks. Assuming that this is the same blocksize which is used by amrestore, I tried telling amrestore to use it, but it refused: kuller# amrestore -b 1k /dev/nsa0 kuller.raad.tartu.ee / amrestore: minimum block size is 32k kuller# Is it possible that amrestore can't read the tape because it has been written with too small blocksize? Or am I barking under completely wrong tree here? It doesn't seem to be hardware problem, because, as I said, I can back up with amdump and restore with amrecover, the only thing that doesn't work is amrestore (and thus, amverify). Unfortunately I don't remember what the blocksize reported by 'mt status' was with the old HP DDS3 drive. Finally, as promised, here's tonight's amverify output. - cut here - Tapes: PAEV11 Errors found: PAEV11 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out PAEV11 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out PAEV11 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out PAEV11 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out PAEV11 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out PAEV11 (): amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out amverify PAEV Tue Jan 14 23:16:55 EET 2003 Loading current slot... Using device /dev/nsa0 Volume PAEV11, Date 20030114 Checked kuller.raad.tartu.ee._var.20030114.0 ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out Checked heerold.raad.tartu.ee._.20030114.0 ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out Checked kuller.raad.tartu.ee._usr.20030114.0 ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out Checked kuller.raad.tartu.ee._.20030114.0 ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out Checked heerold.raad.tartu.ee._var.20030114.0 ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of information ** No header 0+0 in 0+0 out Checked heerold.raad.tartu.ee._usr.20030114.0 ** Error detected () amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: reached end of
Re: amanda 2.4.3 RESULTS MISSING
Tue, 14 Jan 2003 13:09:38 -0500 Gene Heskett [EMAIL PROTECTED]:
Mmm, one question:
Have you more than one installed version of amanda?
The reason I ask is that the normal amanda ./configuration will put
stuff in /usr/local, but the rpm install like from redhat, puts it
in /usr.
No, I configure it with --prefix=/opt/amanda, so there is no posibility of
file shuffling.
Get the latest version of amanda from Jean-Louis's site at
umontreal, link near the bottom of the amanda.org web page, and
check the ChangeLog, you might find something related there.
Since thats the Jan 4th issue when I last looked last night, and
I've been running that one since the 5th with no problems, you
might even build and install it.
I've tried with 2.4.2p2, 2.4.3 stable, 2.4.3-20030104 and 2.5.0-20030104.
All produce the same amreport results.
Searching through the code of reporter.c I don't see any function
more complex than strcmp(), so what is different in my system? (I don't
think strcmp can be somehow corrupt).
And what is funnier: I forgot changing the tape yesterday, so I have had to
run amflush, and the report DID get the results:
---
Subject: AMFLUSH MAIL REPORT FOR January 15, 2003
Date: Wed, 15 Jan 2003 12:04:55 +0100
The dumps were flushed to tape PRMD-002.
The next tape Amanda expects to use is: a new tape.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
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.20.00.2
Tape Used (%) 0.00.00.0 (level:#disks ...)
Filesystems Taped 2 0 2 (1:2)
Avg Tp Write Rate (k/s)22.0--22.0
NOTES:
taper: tape PRMD-002 kb 160 fm 2 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
prmb /etc1 260 96 36.9 N/A N/A0:05 18.3
prmb -ias/enfrio 1 10 64 640.0 N/A N/A0:02 31.2
(brought to you by Amanda version 2.4.3)
---
Why amreport invoked by amdump fails to collect the stats and
invoked by amflush does not?
Sergio
Re: amanda 2.4.3 RESULTS MISSING
On Wednesday 15 January 2003 07:24, Sergio G. Reus wrote:
Tue, 14 Jan 2003 13:09:38 -0500 Gene Heskett
[EMAIL PROTECTED]:
Mmm, one question:
Have you more than one installed version of amanda?
The reason I ask is that the normal amanda ./configuration will
put stuff in /usr/local, but the rpm install like from redhat,
puts it in /usr.
No, I configure it with --prefix=/opt/amanda, so there is no
posibility of file shuffling.
Well, if locate says your system is clean of older stuff, then that
was my best shot at it. You did unpack, configure and make amanda
as the user amanda, and install as root I assume, so there
shouldn't be any permissions problems.
I'll have to leave this one to the real experts, I just play one
occasionally. :-)
Get the latest version of amanda from Jean-Louis's site at
umontreal, link near the bottom of the amanda.org web page, and
check the ChangeLog, you might find something related there.
Since thats the Jan 4th issue when I last looked last night, and
I've been running that one since the 5th with no problems, you
might even build and install it.
I've tried with 2.4.2p2, 2.4.3 stable, 2.4.3-20030104 and
2.5.0-20030104. All produce the same amreport results.
Searching through the code of reporter.c I don't see any function
more complex than strcmp(), so what is different in my system? (I
don't think strcmp can be somehow corrupt).
And what is funnier: I forgot changing the tape yesterday, so I
have had to run amflush, and the report DID get the results:
--
- Subject: AMFLUSH MAIL REPORT FOR January 15, 2003
Date: Wed, 15 Jan 2003 12:04:55 +0100
The dumps were flushed to tape PRMD-002.
The next tape Amanda expects to use is: a new tape.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
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.20.00.2
Tape Used (%) 0.00.00.0
(level:#disks ...) Filesystems Taped 2 0
2 (1:2) Avg Tp Write Rate (k/s)22.0--
22.0
NOTES:
taper: tape PRMD-002 kb 160 fm 2 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER
STATS HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS
KB/s MMM:SS KB/s --
- prmb /etc
1 260 96 36.9 N/A N/A0:05 18.3 prmb
-ias/enfrio 1 10 64 640.0 N/A N/A0:02 31.2
(brought to you by Amanda version 2.4.3)
--
-
Why amreport invoked by amdump fails to collect the stats and
invoked by amflush does not?
Sergio
[This E-mail scanned for viruses by Declude Virus]
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.22% setiathome rank, not too shabby for a WV hillbilly
TSM
Is TSM free? __ E-mail Premium BOL Antivírus, anti-spam e até 100 MB de espaço. Assine já! http://email.bol.com.br/
amrecover tapeless-mode
Hi, I set up amanda in tapeless mode with an external firewire disk on debian woody. Amdump runs fine but most time I try to restore data, I get errors being not at the beginning of the tape. amrestore: WARNING: not at start of tape, file numbers will be offset amrestore: 0: skipping * amrestore: 1: skipping * amrestore: 2: reached end of tape: date 20030115 amidxtaped: amrestore terminated normally with status: 1 amidxtaped: could not stat file:/mnt/firewire/ So, how do I rewind a harddisk? -- Death is nature's way of telling you to slow down.
Re: TSM
On Wed, 15 Jan 2003, Aline wrote: Is TSM free? No. It's an IBM product... -Mitch
Re: chg-zd-mtx doesn't work
Axel, I'd doing this same thing myself. I've on Solaris 8 with a StorEdge 9 jukebox with LTO drive. What I've found is that 1) mtx, mostly it all works, I'm now starting to wonder if I have the correct mtx to go along with chg-zd-mtx vs the version for chg-mtx. 2) chg-zd-mtx, works completely except for the -slot N function. I can reset, eject, load first, last, next, previous, just not load a specific slot number. 3) amlabel and amtape work with the exception of the slot N parameter. amcheck, amdump seem to work just fine. I'm going to test amrestore this morning, we've had no need to test amflush and I'm certain it'll work just fine. What OS, what versions of mtx, OS, etc... --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773 if I run ../chg-zd-mtx info it reports: none no slots available but mtx status finds: Storage Changer /dev/changer:1 Drives, 7 Slots ( 0 Import/Export ) Data Transfer Element 0:Full (Storage Elememt 1 Loaded) Storage Element 1:Empty Storage Element 2:Full etc. so why doesn't mtx doesn't work with ch-zd-mtx? Any Ideas? cheers Axel -- Axel Haenssen Department of Ecology Evolutionary Biology Princeton University Princeton, NJ 08540 USA phone: +1-609-258-6999 email: [EMAIL PROTECTED] find my public key at: www.princeton.edu/~axel
Re: TSM
You mean IBM TSM?? No, definitely not but negotiable with the sales department. Axel On Wed, 2003-01-15 at 09:29, Aline wrote: Is TSM free? __ E-mail Premium BOL Antivírus, anti-spam e até 100 MB de espaço. Assine já! http://email.bol.com.br/ -- Axel Haenssen Department of Ecology Evolutionary Biology Princeton University Princeton, NJ 08540 USA phone: +1-609-258-6999 email: [EMAIL PROTECTED] find my public key at: www.princeton.edu/~axel
Multiple Jukeboxes
Amanda Users, I've gotten (pretty much anyway) amanda working with my jukebox and LTO drive. We are wondering if we could configure amanda to use BOTH jukeboxes, you know, kind of keep 18 tapes on line with Amanda finding the proper available tape according to the tapelist file. I'd thought I'd seen something on using multiple drives as a pretend jukebox but this is really another level of operation. thanks, Brian --- Brian R Cuttler [EMAIL PROTECTED] Computer Systems Support(v) 518 486-1697 Wadsworth Center(f) 518 473-6384 NYS Department of HealthHelp Desk 518 473-0773
amdump not working
I have Redhat 8.0 with Exabyte220 I switched from the chg-multi to chg-zd-mtx. I can load tapes and unload tapes. I can label them and inventory them. But I can write to the tapes. Attached is the amdump debug file. I am not sure what this means /home 0 SIZE -1 /home 1 SIZE -1 -- Raymond Keckler [EMAIL PROTECTED] Homes.com amandad: debug 1 pid 1445 ruid 0 euid 0: start at Wed Jan 15 11:17:05 2003 amandad: version 2.4.3 amandad: build: VERSION=Amanda-2.4.3 amandad:BUILT_DATE=Thu Jan 9 11:25:19 EST 2003 amandad:BUILT_MACH=Linux emailbkup 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux amandad:CC=gcc amandad:CONFIGURE_COMMAND='./configure' '--with-user=root' '--with-group=root' amandad: paths: bindir=/usr/local/bin sbindir=/usr/local/sbin amandad:libexecdir=/usr/local/libexec mandir=/usr/local/man amandad:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda amandad:CONFIG_DIR=/usr/local/etc/amanda DEV_PREFIX=/dev/ amandad:RDEV_PREFIX=/dev/ DUMP=/sbin/dump amandad:RESTORE=/sbin/restore SAMBA_CLIENT=/usr/bin/smbclient amandad:GNUTAR=/bin/gtar COMPRESS_PATH=/bin/gzip amandad:UNCOMPRESS_PATH=/bin/gzip MAILER=/usr/bin/Mail amandad:listed_incr_dir=/usr/local/var/amanda/gnutar-lists amandad: defs: DEFAULT_SERVER=emailbkup DEFAULT_CONFIG=DailySet1 amandad:DEFAULT_TAPE_SERVER=emailbkup amandad:DEFAULT_TAPE_DEVICE=/dev/null HAVE_MMAP HAVE_SYSVSHM amandad:LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE amandad:AMANDA_DEBUG_DAYS=4 BSD_SECURITY USE_AMANDAHOSTS amandad:CLIENT_LOGIN=root FORCE_USERID HAVE_GZIP amandad:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast amandad:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc amandad: time 0.019: got packet: Amanda 2.4 REQ HANDLE 000-B0240808 SEQ 1042647426 SECURITY USER root SERVICE sendsize OPTIONS features=feff9f00;maxdumps=1;hostname=emailbkup; GNUTAR /home 0 1970:1:1:0:0:0 -1 OPTIONS |;auth=bsd;compress-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; GNUTAR /home 1 2003:1:14:23:14:21 -1 OPTIONS |;auth=bsd;compress-fast;index;exclude-list=/usr/local/lib/amanda/exclude.gtar; amandad: time 0.020: sending ack: Amanda 2.4 ACK HANDLE 000-B0240808 SEQ 1042647426 amandad: time 0.021: bsd security: remote host emailbkup user root local user root amandad: time 0.021: amandahosts security check passed amandad: time 0.021: running service /usr/local/libexec/sendsize amandad: time 0.123: sending REP packet: Amanda 2.4 REP HANDLE 000-B0240808 SEQ 1042647426 OPTIONS features=feff9f00; /home 0 SIZE -1 /home 1 SIZE -1 amandad: time 0.123: got packet: Amanda 2.4 ACK HANDLE 000-B0240808 SEQ 1042647426 amandad: time 0.124: pid 1445 finish time Wed Jan 15 11:17:05 2003
Re: amdump not working
On Wed, Jan 15, 2003 at 12:26:21PM -0500, Raymond Keckler wrote: I have Redhat 8.0 with Exabyte220 I switched from the chg-multi to chg-zd-mtx. I can load tapes and unload tapes. I can label them and inventory them. But I can write to the tapes. Attached is the amdump debug file. Good start, what does amcheck give you? I am not sure what this means /home 0 SIZE -1 /home 1 SIZE -1 I believe your server asked the client for the estimated backup size of /home at level 0 and level 1. However the server did not get back valid results. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Multiple Jukeboxes
On Wed, Jan 15, 2003 at 12:36:18PM -0500, Brian Cuttler wrote: Amanda Users, I've gotten (pretty much anyway) amanda working with my jukebox and LTO drive. We are wondering if we could configure amanda to use BOTH jukeboxes, you know, kind of keep 18 tapes on line with Amanda finding the proper available tape according to the tapelist file. That's not possible yet, but you can easily write a changer script that call two changer script. You can look at the chg-rait script that do something similar, it combine many juke-box in a rait device. chg-rait is available in the latest 2.4.3 snapshot. Jean-Louis -- Jean-Louis Martineau email: [EMAIL PROTECTED] Departement IRO, Universite de Montreal C.P. 6128, Succ. CENTRE-VILLETel: (514) 343-6111 ext. 3529 Montreal, Canada, H3C 3J7Fax: (514) 343-5834
Bug? - gzip running on client AND server
Just notice that on at least on of my amanda disk dumps, it is being run
through gzip on client and on the server. The details:
disklist:
lewis /export/lewis3 comp-best-user-tar
amanda.conf:
define dumptype root-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
exclude list /usr/local/lib/amanda/exclude.gtar
priority low
}
define dumptype user-tar {
root-tar
comment user partitions dumped with tar
priority medium
comprate 0.70
}
define dumptype comp-best-user-tar {
user-tar
compress client best
}
on sever:
UIDPID PPID C STIME TTY TIME CMD
amanda6995 6994 0 Jan14 ?00:00:00 /bin/sh /usr/sbin/amdump
Data
amanda7004 6995 0 Jan14 ?00:00:01 /usr/lib/amanda/driver Data
amanda7005 7004 0 Jan14 ?00:03:09 taper Data
amanda7006 7004 2 Jan14 ?00:21:09 dumper0 Data
amanda7010 7005 0 Jan14 ?00:02:48 taper Data
amanda7200 7006 0 02:31 ?00:00:01 /bin/gzip --best
lsof -p 7200:
COMMAND PID USER FD TYPE DEVICESIZE NODE NAME
gzip7200 amanda0u IPv4 89527 TCP
matchbox.colorado-research.com:1187-lewis.colorado-research.com:5603
(ESTABLISHED)
gzip7200 amanda1w REG8,5 49152 50218
/var/lib/amanda/Data/index/lewis/_export_lewis3/20030114_0.gz.tmp
gzip7200 amanda2w REG8,5 21860 40187
/var/lib/amanda/Data/amdump
grep lewis amdump:
DUMP lewis 34cbfe811f01 /export/lewis3 20030114 1 0 1970:1:1:0:0:0
13255125 9312 1 2003:1:8:5:7:24 11532986 51563
driver: send-cmd time 27114.674 to dumper0: FILE-DUMP 00-00011
/var/amanda/Data/20030114/lewis._export_lewis3.0 lewis 34cbfe811f01
/export/lewis3 NODEVICE 0 1970:1:1:0:0:0 1073741824 GNUTAR 13255200
|;bsd-auth;compress-best;index;exclude-list=/usr/local/lib/amanda/exclude.gtar;
On client:
UIDPID PPID CSTIME TTY TIME CMD
amanda 90664 93121 0 02:31:55 ? 5:38
/usr/freeware/libexec/sendbackup
amanda 93116 93121 0 02:31:55 ? 584:12 /usr/sbin/gzip
--best
amanda 93120 90664 0 02:31:55 ? 0:01 sed -e s/^\.//
amanda 93121 1 0 02:31:55 ? 0:00
/usr/freeware/libexec/sendbackup
amanda 93139 93120 0 02:31:55 ? 2:12
/usr/freeware/bin/tar -tf -
Has anyone seen this before?
TIA,
Orion
Re: Bug? - gzip running on client AND server
On Wed, 15 Jan 2003 at 12:31pm, Orion Poplawski wrote Just notice that on at least on of my amanda disk dumps, it is being run through gzip on client and on the server. The details: I'm pretty sure that the gzip on the server is compressing the index file, *not* the dump contents. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Bug? - gzip running on client AND server
Joshua Baker-LePain wrote: On Wed, 15 Jan 2003 at 12:31pm, Orion Poplawski wrote Just notice that on at least on of my amanda disk dumps, it is being run through gzip on client and on the server. The details: I'm pretty sure that the gzip on the server is compressing the index file, *not* the dump contents. Ah, duh! A close look at the lsof output confirms.
Re: amanda 2.4.3 RESULTS MISSING
Oh yes, the refuses to mail report thing. I've had it too.
Have no idea *why* but the only fix I've heard about
works for me, too.
Fix: remove thelbl-temp line from your configuration.
The report should get emailed OK now. Tomorrow you
can probably put the line back in, and it will be okay
for a while.
Maybe this fix can prompt an actual developer to recognize
what it causing this?
Deb Baddorf
And what is funnier: I forgot changing the tape yesterday, so I have had to
run amflush, and the report DID get the results:
---
Subject: AMFLUSH MAIL REPORT FOR January 15, 2003
Date: Wed, 15 Jan 2003 12:04:55 +0100
The dumps were flushed to tape PRMD-002.
The next tape Amanda expects to use is: a new tape.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
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.20.00.2
Tape Used (%) 0.00.00.0 (level:#disks ...)
Filesystems Taped 2 0 2 (1:2)
Avg Tp Write Rate (k/s)22.0--22.0
NOTES:
taper: tape PRMD-002 kb 160 fm 2 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
prmb /etc1 260 96 36.9 N/A N/A0:05 18.3
prmb -ias/enfrio 1 10 64 640.0 N/A N/A0:02 31.2
(brought to you by Amanda version 2.4.3)
---
Why amreport invoked by amdump fails to collect the stats and
invoked by amflush does not?
Sergio
---
Deb Baddorf [EMAIL PROTECTED] 840-2289
You can't help getting older, but you don't have to get old.
- George Burns IXOYE
Re: Bug? - gzip running on client AND server
* Orion Poplawski [EMAIL PROTECTED] (Wed, Jan 15, 2003 at 12:31:44PM -0700) Just notice that on at least on of my amanda disk dumps, it is being run through gzip on client and on the server. The details: lsof -p 7200: COMMAND PID USER FD TYPE DEVICESIZE NODE NAME gzip7200 amanda0u IPv4 89527 TCP matchbox.colorado-research.com:1187-lewis.colorado-research.com:5603 (ESTABLISHED) gzip7200 amanda1w REG8,5 49152 50218 /var/lib/amanda/Data/index/lewis/_export_lewis3/20030114_0.gz.tmp iIt's compressing the index file. Has anyone seen this before? Yup, happens all the time, it's what it's supposed to do if you enable indexing. Currently listening to: Metallica - Nothing Else Matters Gerhard, @jasongeo.com == The Acoustic Motorbiker == -- __O If your watch is wound, wound to run, it will =`\, If your time is due, due to come, it will (=)/(=) Living this life, is like trying to learn latin in a chines firedrill
amandad without xinetd
How to run amandad without usning xinetd? Any pointer will be greatly appeciated. I am running 2.4.2p2 on Mandrake Linux 8.0 James
Re: amdump not working
Ok the gnutar directory was never created. That is why it failed. Is
there documention besides the man pages on Amanda? My backup was success
full but it still had an error on it.
Why does it give me a tape error?
---
*** 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.
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 0:09
Dump Time (hrs:min)0:04 0:00 0:04
Output Size (meg) 422.60.0 422.6
Original Size (meg) 433.20.0 433.2
Avg Compressed Size (%)97.5--97.5 (level:#disks
...)
Filesystems Dumped1 0 1 (1:1)
Avg Dump Rate (k/s) 1632.9-- 1632.9
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) -- -- --
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS
KB/s
-- -
emailbkup/home 1 443630 432760 97.5 4:251632.9 N/A N/A
(brought to you by Amanda version 2.4.3)
-
does anybody now why
On Wed, 2003-01-15 at 14:09, Jon LaBadie wrote:
On Wed, Jan 15, 2003 at 12:26:21PM -0500, Raymond Keckler wrote:
I have Redhat 8.0 with Exabyte220 I switched from the chg-multi to
chg-zd-mtx. I can load tapes and unload tapes. I can label them and
inventory them. But I can write to the tapes. Attached is the amdump
debug file.
Good start, what does amcheck give you?
I am not sure what this means
/home 0 SIZE -1
/home 1 SIZE -1
I believe your server asked the client for the
estimated backup size of /home at level 0 and level 1.
However the server did not get back valid results.
--
Raymond Keckler [EMAIL PROTECTED]
Homes.com
Re: amandad without xinetd
On Wednesday 15 January 2003 16:30, Kang, James wrote: How to run amandad without usning xinetd? Any pointer will be greatly appeciated. I am running 2.4.2p2 on Mandrake Linux 8.0 James Is mandrake 8.0 still using inetd? In which case I think there are instructions in the doc directory of the archive unpack. As a side comment though, xinetd is considered to be more secure, so you might consider updating the distribution to one that does use it. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly
compile error on 2.4.3-20030104
the last bit of the output: Making all in restore-src make[1]: Entering directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' source='amidxtaped.c' object='amidxtaped.o' libtool=no \ depfile='.deps/amidxtaped.Po' tmpdepfile='.deps/amidxtaped.TPo' \ depmode=gcc3 /bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../tape-src -I../server-src -D_FILE_OFFSET_BITS=64 -D_FILE_OFFSET_BITS=64 -O2 -c `test -f 'amidxtaped.c' || echo './'`amidxtaped.c amidxtaped.c: In function `main': amidxtaped.c:478: warning: passing arg 2 of `waitpid' from incompatible pointer type make[1]: *** No rule to make target `../server-src/libamserver.la', needed by `amidxtaped'. Stop. make[1]: Leaving directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' make: *** [all-recursive] Error 1 ## this is with gcc 3.2 20020903 which is the deault gcc on RH 8.0 distribution. ## I will try another source package...
Re: why is tapetype so slow?
[Posted and Cc'ed] On Wed, Jan 15, 2003 at 04:32:23PM -0500, Eric Sproul wrote: After disabling H/W compression, I am getting the same performance from tapetype. It has been running for 15 hours and has only written about 30GB. There is 1 tapetype version around, it's got command-line options, there are ways to go wrong. What are the consequences of having the wrong values in a tapetype definition? If the size value is too large, Amanda will just encounter EOT sooner than expected, right? If it's too low, you waste some tape. I'm thinking I might take what people have already posted for the DLT220 drive and scale it up by 45% (160 is 45% more than 110). Am I crazy? Not crazy at all. I think folks get a little too hung up on tapetype. With your drive, for example, it's hard to see how you would give a darn *what* filemark is, unless your disklist is 1000 entries long... However, you bought yourself a big, fast drive, and what you *should* do is to confirm that it *is* big and fast. Make yourself a representative disk file (15GB of gzipped tar file, 80GB of uncompressed xfsdump file, whatever is apprpropriate for *your* Amanda environment). Run a loop on it like this (pardon the csh, it was a 60-second quickie): #!/bin/tcsh -f set count=1 while (1) echo transfer $count time dd if=/a6/backup/spitfire._a1.20020718.0 of=/dev/rmt/1cn obs=32k || exit @ count++ end Always good to be a little conservative on length, particularly if runtapes=1; you don't want Amanda to estimate a run that doesn't end up fitting. -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
RE: amandad without xinetd
Maybe I wasn't clear enough. I am looking for a way to run amandad by itself without getting started by Mandrake's xinetd. Thanks -Original Message- From: Gene Heskett To: Kang, James; [EMAIL PROTECTED] Sent: 1/15/03 6:10 PM Subject: Re: amandad without xinetd On Wednesday 15 January 2003 16:30, Kang, James wrote: How to run amandad without usning xinetd? Any pointer will be greatly appeciated. I am running 2.4.2p2 on Mandrake Linux 8.0 James Is mandrake 8.0 still using inetd? In which case I think there are instructions in the doc directory of the archive unpack. As a side comment though, xinetd is considered to be more secure, so you might consider updating the distribution to one that does use it.
Universal Programlayýcý
Title: Post Message UNIVERSAL PROGRAMLAYICI Yeteneklerine Þaþacaksýnýz Piyasa Fiyatýnýn Yarýsýna Üstelik 5 Sene Garanti 499USD (Kredi Kartýna 0 Komisyon) Metropol Elektronik Ltd. Þti Tel: 312 425 2200 Fax: 312 425 9983 (Detaylý bilgi için arayýnýz) [EMAIL PROTECTED] (Taleplerinizi bu adrese bildiriniz) ***YENÝ ÜRÜN** Mega Mx Universal Programlayýcý Tek Baþýna veya PC ile kullanýlabilenUniversal ser Programlayýcý. Elle Programlamaya uygundur. -Parelel haberleþme -256 Mbit e geniþleyebilir -5000 den fazla EEPROM,flash Memory, Serial Prog , LOGIC GAL, FPGA, MCU programlayabilirsiniz. -Düþük voltaj (1.8 V dan aþaðý) ) desteði -Performans Karþýlaþtýrmasý(Intel 28F160, 16 Mbit flash Memory,) -Standart 48 pin DIP soket -Ýlave bir modül gerektirmez - Ömür boyu Yazýlým güncelleme desteði -5 sene garanti -%100 amerikan Malý 110-220 V Besleme programlanabilir Üniversal Seri Programlayýcý çok geniþ entegre ailesini desteklemektedir. Top Max iþini iyi bilen profesyonellerin terci ettiði en ekonomik programlayýcýdýr. Tek bir parçadan oluþan Top Max laboratuarlar , mühendislik þirketleri ve kamu kurumlarda kolay ve bütün ihtiyacý görecek þekilde tasarlanmýþtýr. Kullanýcý Dostu ara yüzü ile çok yetenekli fonksiyonlarýný kolayca kullanabilirsiniz. Bütün pin ler adreslenebilir. Yeni entegreler kolayca kütüphaneye eklenebilir veya Ýnternetten yeni entegreleri ücretsiz ve güvenilir olarak güncelleyebilirsiniz Yeni Entegreler programlamak için ilave bir donanýma ihtiyacýnýz olmaz.. Opsiyonel olarak 4Mbit lik ROM emulator alabilirsiniz. 48 pin Üniversal ve TTL pin driver cihazýn üzerindedir . Program ile pinleri kontrol ederek her pini V Vcc, Vpp ,GND ile besleyebilirsniz.Pinlerin high/low seviyeleri ayarlanabilir(pull-high/pull-low, tri-state ve yüksek hýz) Bu geliþmiþ pin dizayný ile herhangi bir adaptör kullanmadan her türlü kompanet rahatlýkla programlanabilir. Mega Max la sadece programlanabilir entegreleri deðil programlamakla kalmaz TTL ve CMOS entegreleri test edebilirsiniz.Dinamik ve Statik hafýzalarýn çalýþýp çalýþmadýðýný kontrol edebilirsiniz. Mega Max bütün IBM PC, XT, PS/2,AT,286,386,486,Pentium, Pentium II, Pentium III, Celeron ,PIV, AMD, Cyrix, Kiþisel Laptop larla kullanýlabilir. Standart olarak herhangi bir kiþisel PC nin Paralel Portundan baðlantý kurabilirsiniz. Herhangi bir Adapter ve özel karta ihtiyaç duymaz. Mega Max ýn en büyük avantajlarýndan bir çok üstün hazýrlanmýþ yazýlýmýdýr. Top Max herhangi baðlý bir PC ile kontrol edilebilir.Operasyon Yazýlýmý kullanýcý dostu, Windows altýnda pencerelerle çalýþma imkaný, makro hazýrlama, batch dosyalarýný yürütebilme,yüksek boyutlu sanal hafýza yönetimi saðlar. Mega Max Operasyonel Yazýlýmý bir çok derleyicinin çýktýsýný kullanabilir( POF, JDEC, CUPL, PALASM,OPEL,ABEL Program vector capability, multi-array fuse map editor, ve Dos shell handling utility, file fromat handler ) Bütün kompanentlerde yüksek performans alýrsýnýz. Kontrol programý her zaman kendini performans teste tabi tutacak þekilde donatýlmýþtýr.Her zaman 48 pin i test eder. TopMax¡¯s Mühendislik uygulamarýnda en esnek cihazlardan biridir · Desteklenen Ürünler · EPROM 27xxx ve 27Cxxx serisi, 16 Kbit den 32Mbit e kadar 8-bit/16-bit · EEPROM 27Exxx, 28xxx , ve 28Cxxx serisi · Flash EPROM 256 Kbit 32 Mbit 28Fxxx, 29Fxxx 29Cxxx, 29BVxxx, 29LVxxx, 29Wxxx 49Fxxx serisi(2.7, 3.3, 5.0, veya 12 Volt) · Serial E(E)PROM 24Cxx, 24Fxx, 25Cxx, 59Cxx, EPC1/1213/1648, ve 93Cxx · Bipolar PROM 27Sxx, 7Cxxx, 71xx, 74Sxx, 87Sxx, 82Sxx, · PALs, PALCEs, GAL 16V8, 20V8, 22V10, 20RA10, 26V12 serisi · Dallas NV RAM DS12xx, DS13xx, DS15xx, DS16xx serisi · PEELs 153, 173, 253, 273, 18CV8, 20CG10 serisi · EPLD PLCxxx, PLSxxx, PLUSxxx, Epxxx, EPCxxx, EPMxxx, PLDxxx, 5Cxxx, 85Cxxx serisi · SPLDs, CPLD ATF16/20/22Vxx, ATV750/1500/2500 · MACH serisi MACH1xx/2xx/4xx, ve xxx-SP serisi · MAX serisi MAX5000, MAX7000 serisi · 8748 Microcontrollers 8741, 8742, 8748, 8749 serisi · 8751 Microcontrollers 87C51/52, -FA, -FB, -FC, ¡®528, ¡®652, ¡®654, ¡¯54 89Cxx, 89Sxx, 89LVxx, 89C serisi 87C751/752 · SGS-Thomson Microcontrollers ST62xx serisi · Xilinx EPLD XC72xx, XC73xx serisi · WSI¡¯s PSD PSD3xx, PSD4xx, PSD5xx serisi · MCHP¡¯s PIC PIC12Cxxx, PIC16xxx, 17xxx serisi · Motorola Microcontrollers MC68705, MC68HC705, MC68HC711 serisi · Zilog Microcontrollers Z86Cxx, Z86Exx serisi · I.C.s Tested · TTL type 54, 74(S, LS, L, H, HC) serisi · CMOS type 40, 45 serisi · Dynamic Memory 4164 - 1MBit · Static Memory 6116 - 6256 · Kullanýcý tanýmlý test iþareti üretme Listeden Çýkmak Ýçin [EMAIL PROTECTED] e bir mesaj atýn
Re: compile error on 2.4.3-20030104
On Wednesday 15 January 2003 18:07, DK Smith wrote: the last bit of the output: Making all in restore-src make[1]: Entering directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' source='amidxtaped.c' object='amidxtaped.o' libtool=no \ depfile='.deps/amidxtaped.Po' tmpdepfile='.deps/amidxtaped.TPo' \ depmode=gcc3 /bin/sh ../config/depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../config -I../common-src -I../tape-src -I../server-src -D_FILE_OFFSET_BITS=64 -D_FILE_OFFSET_BITS=64 -O2 -c `test -f 'amidxtaped.c' || echo './'`amidxtaped.c amidxtaped.c: In function `main': amidxtaped.c:478: warning: passing arg 2 of `waitpid' from incompatible pointer type make[1]: *** No rule to make target `../server-src/libamserver.la', needed by `amidxtaped'. Stop. make[1]: Leaving directory `/Admin/Build/amanda-2.4.3-20030104/restore-src' make: *** [all-recursive] Error 1 ## this is with gcc 3.2 20020903 which is the deault gcc on RH 8.0 distribution. ## I will try another source package... Yes, so would I, I've had no problem building the snapshots with 3.2 as supplied with rh8.0. But I have had kernel downloads go south, and only going after it again will fix the problem for me in that case. I'm out in the boonies on a 56k line thats often 28k or less. -- Cheers, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.22% setiathome rank, not too shabby for a WV hillbilly
³o¬O§Anªº!!
Title: ±z¬O¤U±¨º¤@¨º¤@ºØ¨¥÷
¡@
°Ý°Ý¦Û¤v...¿ú¬°¤°»òÁ`¬O¤£ª¾¤£Ä±´Nªá§¹¤F...
±z¬O¤U±¨º¤@¨º¤@ºØ¨¥÷
:
¡@¡@¢°.¬O¤@¦ì·QÁÈ¿úªº¾Ç¥Í¡A«o¥u¯àÁȨì¨C¤p®É70¡ã100ªº®ÉÁ~¡A²Ö¿n¤£¤F°]´I¡C
¡@¡@¢±.¬O¤@¦ì¤W¯Z±Ú¡A¨C¤Ñ¥´¥d¡¨¤W¡¨¡¨¤U¡¨¯Z¡Aè¦n¥d¦b¨º¸Ì¡A¤S¾á¤ß³Qµôû¡C
¡@¡@¢².¬O¤@¦ì·QÀ°®a®x¦hÁȨǿú¡A¨Ó¬°®a®xºÉ¤ßºÉ¤Oªº®a®x¥D°ü¡C
¡@¡@¡@ ¦pªG§A¯uªº·Q¼W¥[¦¬¤J¡A¤S¨ã³Æ¤F¤@¨Ç¹q¸£ªº°ò¦¡I
¨º»ò®¥³ß±z¡I³o±N·|¬O±z³Ì¦nªº¾÷·|¡I
±zª¾¹D¶Ü¡H
¡@¡@ì¨Ó¶R¤ú»I¡A¥Î½Ã¥Í¯È¡A¤]¯à²Ö¿n°]´I¡I¦A°t¤W±M·~ªººô¸ô¦æ¾P¤è¦¡¡Iµ´¹ï¤ÞÃz¥«³õ¡I
¡@
§Ú·Q¬Ý¶R¤ú»I¤Î¥Î½Ã¥Í¯ÈÁÈ¿úªº¼v¤ù
§Ún¶i¤@¨B¤F¸Ñ
§ÚnÁÈ¿ú¡A½Ð±zÁpµ¸§Ú¡I
¡@
¤F¸Ñ¬O¤£¥Îªá¿úªº!!¾÷·|¬O´x´¤¦b¥ýª¾¥ýıªº¤H¤â¤W,´x´¤¥ý¾÷¡A´N¬OĹ®a¡I
·í¾÷·|¥X²{¡@±z¬O¬Ý¨ì¥¦½§²Lªº§Î»ª¡@ÁÙ¬O¤w¬Ý¨ì¨ä¤º²[ªº²`«× ¥¿©Ò¿×¼z²´ÃÑ^¶¯
¡@¡@¡@¡@³o¤Ç¤d¨½°¨ ¥u¦³¿W¨ã¼z²´ªº§B¼Ö ¥i¥H¬Ý¨ì¥Lªº¼ç¤O»P»ùÈ
Y¦]¤H¼Æ¤Ó¦h,¼v¤ùµLªk¥¿±`Æ[¬Ý,½Ð±zª½±µ¯d¤U±zªº¸ê®Æ,§Ú±N·|ºÉ³t»P±z³sµ¸!
³o¤£¬O¤@Ó¤£³Ò¦ÓÀò©Î§ë¾÷¨ú¥©ªº¥Í·N¡A¦Ó¬OÅý¨S¦³°]¤OI´º«oÄ@·N§V¤O¥I¥X¡A§ïÅܦۤv«D¤Z¦¨¥\ªº¦a¤è¡A§Ú̦b³o¸Ì§ïÅܦۤv¨Ã¾Ç²ß¦¨¥\ªº²ßºD¡A¥Î¹ïªº¤èªk§@¹ïªº¨Æ¡A¤£®ö¶OºN¯Áªº®É¶¡¸òµÛ¨t²Î±Ð¨|§Ö³t¦¨ªø¡A¦pªG§A¬O·Qn¤£³Ò¦ÓÀò©Î°½Ãi¨ú¥©¥ç©Î¬O¤£¯à±µ¨ü¬°¤F¦¨¥\¦Ó§ïÅܦۤvªºÃa²ßºDªº¤H¡A½Ð¤£n¯d¤U¸ê®Æ¥H§K®ö¶O©¼¦¹ªº®É¶¡¡C
