Estimate
Hello, I am running debian on kernel 2.4.18 and amanda 2.4.2p2 for both server and client. Upto yesterday it worked fine but when today I run amdump it stuck on getting estimate on clients and when I check the process on clients killpgrp become zombie and it is run by backup. So can anybody can help me out of this. Arunav Mandal.
Re: amanda and dump-gnuitar
* Robert Kearey [EMAIL PROTECTED] (Thu, Mar 14, 2002 at 05:03:09PM +1000)
I'm sure this is an obvious FAQ, but anyway ...
The time has come when I need greater granularity for our backups, so I
want to switch from dump to gnutar. I gather this isn't a simple
proccess - is there a Canonical Way of doing so?
Yes,
edit your disklist, and change the dumptype from a dumptype that uses
DUMP into one that uses TAR.
e.g.
define dumptype high-tar {
global
program GNUTAR
comment root partitions dumped with tar
compress none
index
comment partitions dumped with tar
exclude list /usr/local/lib/amanda/exclude.gtar
priority high
maxdumps 4
}
Mixing dump and gnutar backups in the same tape cycle sounds scary :)
It's not.
I've been doing it for years (well, maybe not years, but at least a year
now)
--
Rob KeareyWebsite: http://apac.redhat.com
Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer
+61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Currently listening to: Led Zeppelin - Stairway To Heaven
Gerhard, (@jasongeo.com) == The Acoustic Motorbiker ==
--
__O One day a king will rise with the sun, the moon and the stars
=`\, And you are he and you must die,
(=)/(=) To be born again, come again, live again,
once more be again the king
Relabel whitout dataloss ?
Is it possible to relabel a tape, but preserve the existing data on the tape ? Reason Im asking is that we are now using 2 tapedrives, and Id like to relabel half od the tapes so that they can only be sued in the 2nd drive, but I'd rather not loose any data on the second batch. Of course, if all else fails, I can label each tape before I start the backup, but I'd rather label them all in one go Kind regards, -- Gerhard den Hollander Phone :+31-10.280.1515 Global IT Support manager Direct:+31-10.280.1539 Jason Geosystems BV Fax :+31-10.280.1511 (When calling please note: we are in GMT+1) [EMAIL PROTECTED] POBox 1573 visit us at http://www.jasongeo.com 3000 BN Rotterdam JASON...#1 in Reservoir CharacterizationThe Netherlands This e-mail and any attachment is/are intended solely for the named addressee(s) and may contain information that is confidential and privileged. If you are not the intended recipient, we request that you do not disseminate, forward, distribute or copy this e-mail message. If you have received this e-mail message in error, please notify us immediately by telephone and destroy the original message.
dump larger than tape, skipping incremental
Hello amanda-gurus, I backup big files from a client over ethernet (100 MBit) to amanda server. the client is very weak (~ 200 MhZ) and it is no good idea to compress the files because the client could crash I think. The files get stored on a holding disk on the amanda server. I use DDS3-tapes and there is not enough free space to store the files on the tape. the following error occurs (amreport): FAILURE AND STRANGE DUMP SUMMARY: localhost /backup lev 6 FAILED [dump larger than tape, skipping incremental] planner: FATAL cannot fit anything on tape, bailing out is there any possibility to compress the files AFTER they got transmitted to the server? Thank you very much! Greetings, Leonie Nuenighoff __ r-tec IT Systeme GmbH Engelsfeld 9 45549 Sprockhövel - Germany Tel. +49 (0) 23 39 - 91 82-698 Fax +49 (0) 23 39 - 91 82-99 http://www.r-tec.net
amlabel crushing the tapelist file
Hello all, I'm using amanda-2.4.2p2 and recently had to add a few tapes with the amlabel program. To my surprise that operation obliterated tapelist file, instead of appending the new tapes (as described on the man page), and now Amanda is asking for new tapes. It seems to have no memory of the old tapes. Is this the normal behavior? Can/should I manually add the old tapelist file? Thank you, Joao PS: Since Amanda is mostly asking for new tapes, I'm choosing them carefully from the old tapelist file, and those used tapes make eventually their way to the new tapelist file. - Email Enviado utilizando o serviço MegaMail
amtape and tape changer problem
Hi, Thank you very much for your suggestion. Meanwhile, I got another problem...when I enter the command amtape daily show I got the following message: scanning all 7 slots in tape-changer rack: slot1: date X Label DailySet11 amtape: could not load slot DeviceCapabilitiesPage: == Null. I am wondering something is wrong about my changer device...but I am not sure what is exactly wrong with it. So, any information or references? pls help!!! Zhen Liu --- It means that it is a unused tape ...if it had been previously used (meaning tape is referred to in the tapelist file) then there will be a reference to the tape. Look in your tapelist file and see if there is any reference to DailySet16 Don Zhen Liu wrote: Hi, I am working on amanda with the Adic Fastor autoloader...Dlt7000... on RH linux 7.1 os... When I run amcheck i got the following message: amcheck-server: slot0: date X label DailySet16 (first labelstr match) So, anyone knows anything wrong with this? why the date shows X instead of the actual date? pls help!!! Thanks, Zhen Liu Via Webmail [EMAIL PROTECTED] Zhen Liu Via Webmail [EMAIL PROTECTED]
amandad failure on Sun box
I was getting a selfcheck error on one of my sun boxes I just built amanda on and this is what I found in /var/adm/messages: jupiter inetd[179]: amanda/udp server failing (looping), service terminated Any ideas on what I need to fix here? Also on my MP-RAS box I'm getting this error running selfcheck: ERROR: edaf6.irs.sat NAK: amandad busy Brian Davidson 11710 Plaza America Drive Reston, Virginia 20190 703.261.4694 703.261.5086 Fax
more dumpers please...
I have a client with 4 fast processors and would like to use at least 2 or 3 of them if possible for dumps. Is it possible to get amanda to dump more than 1 partition on the same client at a time to the backup server? I want to do compress client best which will really slow things down so to counteract that I'd like amanda to run multiple dumpers on the same client but not necessarily the same partition. Thanks! Trevor.
Backups take to long
I've asked this question before but I have a litle more information now. My backups
kick off at 10pm but they are not finishing till 8pm and by that time there is no
one in the office to change the tape for the next backups starting two hours later.
This only seems to have taken this long since I upgraded to amanda 2.4.2p2 to avoid
timeout problems I was having with 2.4.1p1.
Also along with this problem and maybe part of the cause is the fact that
/export/home/student, staff, grad, msc(the biggest and most important parts of the
backup - especially staff and student) are not being dumped until afternoon when
there is a lot of users on the system. Is there a way of forcing amanda to dump and
tape these during the night when there is no(very little) users on the system? It
should be noted that /export/blah/blah is contained on the localhost.
I'm using dump and the tapeserver is running Solaris 5.7, I have a tapelist
containing 20 tapes with a seperate config for monthlys which are run every 4 weeks.
The tapeserver has 4 network cards qfe0-3, One way of speeding things up was in the
disklist forcing each host to use the network card for the network it's on, saving
it from going through the router but I don't know if this is done automatically(my
networking is not as it should be).
Besides the forcing of amanda to do those dumps during the night is there any tips
for configuring amanda to do the backups faster? Is there any difference between
amanda 2.4.2p2 and 2.4.1p1 that would cause this massive backup time difference?
Below I have included a copy of the email sent at the end of the last backup (by the
way what is that code 3 that ufsdump returned on /export/home/staff). I've also
attached my amanda.conf which has an include for amanda.conf.dumptypes,
amanda.conf.net, amanda.conf.tape (Simply to make amanda.conf less cluttered)which
I've also included below.
Email Report:
These dumps were to tape SCMS19.
The next tape Amanda expects to use is: SCMS00.
FAILURE AND STRANGE DUMP SUMMARY:
vindaloo /export/home lev 0 FAILED [Request to vindaloo timed out.]
bicycle/export/home lev 0 FAILED [Request to bicycle timed out.]
toast /export/home lev 0 FAILED [Request to toast timed out.]
mrwhippy /usr/people lev 0 FAILED [Request to mrwhippy timed out.]
localhost /export/home/staff lev 1 FAILED [/usr/sbin/ufsdump returned 3]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)9:23
Run Time (hrs:min)21:57
Dump Time (hrs:min) 16:40 10:36 6:04
Output Size (meg) 20635.412104.2 8531.2
Original Size (meg) 44814.625340.419474.2
Avg Compressed Size (%)44.4 46.4 41.8 (level:#disks ...)
Filesystems Dumped 48 14 34 (1:28 2:3 3:3)
Avg Dump Rate (k/s) 352.2 324.9 399.8
Tape Time (hrs:min)1:26 0:50 0:36
Tape Size (meg) 20636.912104.6 8532.3
Tape Used (%) 59.0 34.6 24.4 (level:#disks ...)
Filesystems Taped48 14 34 (1:28 2:3 3:3)
Avg Tp Write Rate (k/s) 4104.2 4162.9 4023.6
FAILED AND STRANGE DUMP DETAILS:
/-- localhost /export/home/staff lev 1 FAILED [/usr/sbin/ufsdump returned 3]
sendbackup: start [localhost:/export/home/staff level 1]
sendbackup: info BACKUP=/usr/sbin/ufsdump
sendbackup: info RECOVER_CMD=/usr/local/bin/gzip -dc |/usr/sbin/ufsrestore -f... -
sendbackup: info COMPRESS_SUFFIX=.gz
sendbackup: info end
| DUMP: Writing 32 Kilobyte records
| DUMP: Date of this level 0 dump: Wed Mar 13 17:01:36 2002
| DUMP: Date of last level 0 dump: the epoch
| DUMP: Dumping /dev/md/rdsk/d5 (arthur:/export) to standard output.
| DUMP: Mapping (Pass I) [regular files]
? DUMP: Error in ftw (No such file or directory)
| DUMP: The ENTIRE dump is aborted.
sendbackup: error [/usr/sbin/ufsdump returned 3]
\
NOTES:
planner: Incremental of master:/export/home/mail bumped to level 3.
planner: Incremental of roadkill:/export/archive bumped to level 3.
planner: Incremental of roadkill:/export/local bumped to level 2.
planner: Incremental of localhost:/var bumped to level 2.
taper: tape SCMS19 kb 21132160 fm 48 [OK]
DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
-- -
air -xport/home 1 63 32 50.8 0:02 15.1 0:02 27.0
asterix -xport/home 15983 1760 29.4 0:17 101.2 0:03 711.6
besson -xport/home 1 63 32 50.8 0:02 15.6 0:02 26.9
bicycle -xport/home 0 FAILED ---
catullus -tullus/ir1 1 127 32
Re: amanda and dump-gnuitar
Hi Robert, I by no means an Amanda expert, however I am pretty sure you can mix dump and gnutar in your backups. I think it is simply a matter of adjusting the entries in your disklist. I have been able to use both dump and gnutar without problems. You may need to make sure that your clients have access to the desired program (ie. install gnutar if you don't have it on the client). Jeff On Thu, 2002-03-14 at 02:03, Robert Kearey wrote: I'm sure this is an obvious FAQ, but anyway ... The time has come when I need greater granularity for our backups, so I want to switch from dump to gnutar. I gather this isn't a simple proccess - is there a Canonical Way of doing so? Mixing dump and gnutar backups in the same tape cycle sounds scary :) -- Rob KeareyWebsite: http://apac.redhat.com Red Hat Asia-Pacific Legal: http://apac.redhat.com/disclaimer +61 7 3872 4803 Stuff: http://people.redhat.com/rkearey
Problem with throughput
We have a strange problem with throughput to the backup server. The
backup-server is foo1 and the fileserver is foo3. Both servers have a 100Mb
NIC and connected to the same switch.
I can copy a 25Mb file from the /usr/share/admin/felles/infoavd share in 3
seconds to my computer, so the throughput from the fileserver should be ok.
But as you can see amanda finished that copy (4Gb) 17 hours after the
backup started.
Both servers run amanda 2.4.2p2-1.
Some parameters from amanda.conf:
netusage 10 Kbps
# Disk is 40Gb
holdingdisk hd1 {
directory /u05/amanda/dumps
comment main holding disk
use -10 Mb
chunksize 2000 Mb
}
define tapetype SLR100 {
comment Tandberg SLR100 tape drives
length 5 mbytes
filemark 8 kbytes
speed 1650 kps
}
define dumptype user-tar {
root-tar
comment user partitions dumped with tar
priority medium
}
define interface local {
comment a local disk
use 10 kbps
}
define interface eth0 {
comment 100 Mbps ethernet
use 4 kbps
}
Here is a output of the backup running now: (Ignore the problem with
/usr/share/admin/data)
foo1:/ 11088k finished (22:32:22)
foo1:/boot 1 32k finished (22:31:31)
foo1:/home 1 11264k finished (22:31:55)
foo1:/u01 0 1012672k finished (23:12:57)
foo1:/u02 1 32k finished (22:31:19)
foo1:/u03 1 446624k finished (22:48:12)
foo1:/u04 0 1478240k finished (23:25:29)
foo1:/usr 13328k finished (22:32:36)
foo1:/var 14128k finished (22:32:04)
foo2:/11280k finished (22:31:43)
foo2:/boot1 32k finished (22:31:21)
foo2:/home17968k finished (22:33:39)
foo2:/usr 13360k finished (22:32:17)
foo2:/var 1 41920k finished (22:48:57)
foo3:/0 1018976k finished (2:58:04)
foo3:/boot1 32k finished (22:31:23)
foo3:/home4 1410816k finished (6:08:59)
foo3:/usr/share/admin 0 6924700k dumping 408896k ( 5.90%)
(15:02:
52)
foo3:/usr/share/admin/data2 [mesg read: Connection reset by peer]
(0:35:
46)
foo3:/usr/share/admin/felles/infoavd 0 4237920k finished (15:44:45)
foo3:/var 1 29632k finished (22:36:18)
SUMMARY part real estimated
size size
partition : 21
estimated : 21 16506208k
failed : 1 71160k ( 0.43%)
wait for dumping: 0 0k ( 0.00%)
dumping to tape : 0 0k ( 0.00%)
dumping : 1 408896k 6924700k ( 5.90%) ( 2.48%)
dumped : 19 9709344k 9510348k (102.09%) ( 58.82%)
wait for writing: 00k0k ( 0.00%) ( 0.00%)
writing to tape : 00k0k ( 0.00%) ( 0.00%)
failed to tape : 00k0k ( 0.00%) ( 0.00%)
taped : 19 9709344k 9510348k (102.09%) ( 58.82%)
5 dumpers idle : not-idle
taper idle
network free kps: 239878
holding space : 28343992k ( 80.37%)
dumper0 busy : 15:37:02 ( 90.65%)
dumper1 busy : 0:19:20 ( 1.87%)
dumper2 busy : 2:04:15 ( 12.02%)
taper busy : 1:51:04 ( 10.75%)
0 dumpers busy : 0:00:13 ( 0.02%) start-wait: 0:00:13 (100.00%)
1 dumper busy : 16:32:22 ( 96.01%) client-constrained: 15:49:30 ( 95.68%)
not-idle: 0:42:03 ( 4.24%)
start-wait: 0:00:49 ( 0.08%)
2 dumpers busy : 0:34:31 ( 3.34%) client-constrained: 0:34:19 ( 99.44%)
start-wait: 0:00:11 ( 0.56%)
3 dumpers busy : 0:06:30 ( 0.63%) client-constrained: 0:06:30 (
99.90%)
Vegard
Re: dump larger than tape, skipping incremental
On Thu, 14 Mar 2002 at 10:55am, Nünighoff, Leonie, NUE wrote is there any possibility to compress the files AFTER they got transmitted to the server? In your dumptype: compress server fast (or best). -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Bad file descriptor
On Wed, Mar 13, 2002 at 07:59:02PM -0500, John R. Jackson wrote: Every day now (for the past 3 days) I have been getting the same errors: Bad file descriptor Sigh. Amanda is not telling you the whole story there (can't remember if this is fixed in the current source or not). It's not, this patch should fix it. Or maybe just set degraded_mode to 1. 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 --- server-src/driver.c.1 Wed Mar 13 18:34:12 2002 +++ server-src/driver.c Thu Mar 14 09:57:30 2002 @@ -2189,6 +2189,7 @@ update_failed_dump_to_tape(dp); free_serial(result_argv[2]); failed = 2; /* fatal problem */ + start_degraded_mode(runq); } /* reset statistics return */
amrecover is kicking my butt......
Okay, this makes no sense whatsoever. This is only occuring on one
filesystem, and it is sporadic in occurances there. When ever I
attempt to do a amrecover of the directory on /var/mail I get the
following:
But I can dd the file from tape and extract it doing a straight
ufsrestore from that archived file, so it is on the volume. At first I
thought that index file was corrupted (since that is was amrecover
refers off of initially). And the files (or directories) are there in
my dd'd version. Amverify shows no issues whatsoever with the
filesystem in question:
Checked chg._var.20020313.0
And the sendbackup doesn't have any complaints either:
sendbackup: debug 1 pid 11165 ruid 9732 euid 9732 start time Wed Mar 13
22:10:45
2002
/var/adm/amanda/libexec/sendbackup: version 2.4.2p2
sendbackup: got input request: DUMP /var 0 1970:1:1:0:0:0 OPTIONS
|;bsd-auth;ind
ex;
parsed request as: program `DUMP'
disk `/var'
lev 0
since 1970:1:1:0:0:0
opt `|;bsd-auth;index;'
sendbackup: try_socksize: send buffer size is 65536
sendbackup: stream_server: waiting for connection: 0.0.0.0.48393
sendbackup: stream_server: waiting for connection: 0.0.0.0.48394
sendbackup: stream_server: waiting for connection: 0.0.0.0.48395
waiting for connect on 48393, then 48394, then 48395
sendbackup: stream_accept: connection from 152.3.165.105.47225
sendbackup: stream_accept: connection from 152.3.165.105.47226
sendbackup: stream_accept: connection from 152.3.165.105.47227
got all connections
sendbackup: started index creator: /usr/sbin/ufsrestore -tvf - 21 |
sed -e '
s/^leaf[]*[0-9]*[ ]*\.//
t
/^dir[ ]/ {
s/^dir[ ]*[0-9]*[ ]*\.//
s%$%/%
t
}
d
'
sendbackup: spawning /usr/sbin/ufsdump in pipeline
sendbackup: argument list: dump 0usf 1048576 - /dev/rdsk/c0t0d0s3
sendbackup: index created successfully
sendbackup: pid 11165 finish time Wed Mar 13 23:04:32 2002
What is leading amrecover to believe that the file inquestion isn't on
the volume? I am out of ideas.
Don
Re: amlabel crushing the tapelist file
On Thu, Mar 14, 2002 at 10:36:44AM +, jpsp wrote: Hello all, I'm using amanda-2.4.2p2 and recently had to add a few tapes with the amlabel program. To my surprise that operation obliterated tapelist file, instead of appending the new tapes (as described on the man page), and now Amanda is asking for new tapes. It seems to have no memory of the old tapes. Is this the normal behavior? No, Do you know what caused this?, disk full? you killed amlabel? Can/should I manually add the old tapelist file? Yes, if you ran amdump, it has probably erased some log and index files needed to use amrecover. 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
Re: Backups take to long
Hi David,
I don't think I have all the answers to all of your questions, but I did
see a few things that you may want to check into further.
First, I would take a closer look at the chunksize entry in the
Amanda.conf. I think this refers to the size of the files used to hold
your backups. I use a chunk size of 1GB as some filesystems have
difficulty dealing with very large files. This will not reduce the
amount of data per client you can backup. It will simply break the
backup for each entry in the disk list into nice neat chuncks.
Next, please take a look in the /tmp/amanda directory on each troubled
client. In that directory you should have a series of files ending in
.debug. These are log files that will usually contain some hints of
problems. This may help you locate the trouble spot for each client
more efficiently.
If it is at all possible, you may want to consider moving your backup
start time to earlier in the evening. I start my backups at 7:30pm and
they usually finish in the small hours of the morning, depending on how
many level 0's ended up in there.
This may be unrelated to your problem, however I have many solaris
clients on my network I backup as well. I noticed that the TAR and
GZIP/GUNZIP programs that were part of the default install (including
fully patched Solaris 8 systems) were not able to handle files larger
than 2GB. I updated these programs using packages from
www.sunfreeware.com and those problems were fixed.
I know this isn't much information, but hopefully it will help you out
until someone with more experience is able to answer.
Jeff
On Thu, 2002-03-14 at 09:29, David Flood wrote:
I've asked this question before but I have a litle more information now. My backups
kick off at 10pm but they are not finishing till 8pm and by that time there is no
one in the office to change the tape for the next backups starting two hours later.
This only seems to have taken this long since I upgraded to amanda 2.4.2p2 to avoid
timeout problems I was having with 2.4.1p1.
Also along with this problem and maybe part of the cause is the fact that
/export/home/student, staff, grad, msc(the biggest and most important parts of the
backup - especially staff and student) are not being dumped until afternoon when
there is a lot of users on the system. Is there a way of forcing amanda to dump and
tape these during the night when there is no(very little) users on the system? It
should be noted that /export/blah/blah is contained on the localhost.
I'm using dump and the tapeserver is running Solaris 5.7, I have a tapelist
containing 20 tapes with a seperate config for monthlys which are run every 4 weeks.
The tapeserver has 4 network cards qfe0-3, One way of speeding things up was in the
disklist forcing each host to use the network card for the network it's on, saving
it from going through the router but I don't know if this is done automatically(my
networking is not as it should be).
Besides the forcing of amanda to do those dumps during the night is there any tips
for configuring amanda to do the backups faster? Is there any difference between
amanda 2.4.2p2 and 2.4.1p1 that would cause this massive backup time difference?
Below I have included a copy of the email sent at the end of the last backup (by the
way what is that code 3 that ufsdump returned on /export/home/staff). I've also
attached my amanda.conf which has an include for amanda.conf.dumptypes,
amanda.conf.net, amanda.conf.tape (Simply to make amanda.conf less cluttered)which
I've also included below.
Email Report:
These dumps were to tape SCMS19.
The next tape Amanda expects to use is: SCMS00.
FAILURE AND STRANGE DUMP SUMMARY:
vindaloo /export/home lev 0 FAILED [Request to vindaloo timed out.]
bicycle/export/home lev 0 FAILED [Request to bicycle timed out.]
toast /export/home lev 0 FAILED [Request to toast timed out.]
mrwhippy /usr/people lev 0 FAILED [Request to mrwhippy timed out.]
localhost /export/home/staff lev 1 FAILED [/usr/sbin/ufsdump returned 3]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)9:23
Run Time (hrs:min)21:57
Dump Time (hrs:min) 16:40 10:36 6:04
Output Size (meg) 20635.412104.2 8531.2
Original Size (meg) 44814.625340.419474.2
Avg Compressed Size (%)44.4 46.4 41.8 (level:#disks ...)
Filesystems Dumped 48 14 34 (1:28 2:3 3:3)
Avg Dump Rate (k/s) 352.2 324.9 399.8
Tape Time (hrs:min)1:26 0:50 0:36
Tape Size (meg) 20636.912104.6 8532.3
Tape Used (%) 59.0 34.6 24.4 (level:#disks ...)
Filesystems Taped48 14 34 (1:28 2:3 3:3)
Avg Tp Write Rate (k/s) 4104.2
Exclude list
I have my exclude lists on the client systems but I am not sure that they are being used. The total space that gets backed up is about 80MB or so. According to amstatus it is trying to dump 633MB which is roughly half the amount of space on the file system. I'm pretty sure that my exclude lists are correctly working. How can I tell if gtar is using the exclude list? If I do a ps -auxww | grep gtar on the client after I run amdump from the server, I get this: root74765 5.6 0.4 48444592?? D 11:55am 0:39:54 /usr/localbin/gtar --create -file /dev/null --directory /usr --one-file-system --listed-incremental /usr/local/var/amanda/gnutar-lists/smtp0da0s1e_0.new --sparse --ignore-failed-read --totals . Notice there is not --exclude. What did I do wrong? jeff
Re: amlabel crushing the tapelist file
Cópia Jean-Louis Martineau [EMAIL PROTECTED]: On Thu, Mar 14, 2002 at 10:36:44AM +, jpsp wrote: Hello all, I'm using amanda-2.4.2p2 and recently had to add a few tapes with the amlabel program. To my surprise that operation obliterated tapelist file, instead of appending the new tapes (as described on the man page), and now Amanda is asking for new tapes. It seems to have no memory of the old tapes. Is this the normal behavior? No, Do you know what caused this?, disk full? you killed amlabel? Maybe I killed amlabel... That's a real possibility, now that I think about it, since I was testing a new script to format several tapes at once. Anyway I've added the old tapelist and Amanda seems to be normal again. Thanks, Joao Can/should I manually add the old tapelist file? Yes, if you ran amdump, it has probably erased some log and index files needed to use amrecover. 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 - Email Enviado utilizando o serviço MegaMail
Re: Documentation
I'll send you a copy once it's complete. I wouldn't want to send it the whole list. Apparently, only a handful are interested in it. On Wed, 2002-03-13 at 21:09, Robert SHEN wrote: Will it be possible to post it here? - Original Message - From: Brad Tilley [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, March 14, 2002 1:29 AM Subject: Documentation Hello, I am preparing amanda documentation for our office. The documents are specific to us, but general enough to probably be of use to others who have similar amanda implementations (50+ Windows end users and about six departmental Linux servers and workstations). Is there a place where I could publish the documentation (once it is finished) so others could benefit? Thanks, -- Brad Tilley, OUB Sys. Admin. http://bursar.vt.edu/rtilley/pgpkey -- Brad Tilley, OUB Sys. Admin. http://bursar.vt.edu/rtilley/pgpkey
Re: amanda debugging
On Thu, 14 Mar 2002, Chris Freeman wrote: Hi all, I have been using amanda on other servers, and so far have been very impressed with its capabilites. However on one particular box I get a strange problem. amdump and amcheck run with no complaints or problems, but when I go to run amrecover I get the error must set config host, before setting disk and it does not let me continue. There is no option to set confighost, and besides I thought this was set when amrecover is executed. amrecover -C Daily. Is there anything I am missing? I have looked through the archives, but it seems like this isn't a common problem. Also the logs do not seem to suggest anything. Does anyone have any suggestions as to what is going on here? Thanks in advance for any help offered. Chris Freeman. lgsa:/etc/amanda/Daily# amrecover -C Daily AMRECOVER Version 2.4.2p2. Contacting server on localhost ... 220 lgsa AMANDA index server (2.4.2p2) ready. 200 Access OK Setting restore date to today (2002-03-11) 200 Working date set to 2002-03-11. 200 Config set to Daily. 501 No index records for host: lgsa. Invalid? Trying lgsa ... 501 No index records for host: lgsa. Invalid? Trying localhost ... 501 No index records for host: localhost. Invalid? amrecover setdisk /home 501 Must set config,host before setting disk. amrecover # uname -a Linux lgsa 2.4.17 #3 Thu Jan 3 00:14:54 EST 2002 i686 unknown Actually, that's what happens on my server and I just enter the following commands: sethost host_to_restore (from disklist entry) setdisk partition here's an output that I save to remind myself of just that: AMRECOVER Version 2.4.1p1. Contacting server on fred.quantified.net ... 220 fred AMANDA index server (2.4.1p1) ready. 200 Access OK Setting restore date to today (2001-01-31) 200 Working date set to 2001-01-31. 200 Config set to daily. 501 No index records for host: fred.quantified.net. Invalid? Trying fred.quantified.net ... 501 No index records for host: fred.quantified.net. Invalid? amrecover sethost ftp 501 No index records for host: ftp. Invalid? Trying ftp.quantified.net ... 200 Dump host set to ftp.quantified.net. amrecover setdisk /dev/sd0g 200 Disk set to /dev/sd0g. -- ~ Doug Silver Network Manager Quantified Systems, Inc ~
Re: Documentation
On 14 Mar 2002, Brad Tilley wrote: I'll send you a copy once it's complete. I wouldn't want to send it the whole list. Apparently, only a handful are interested in it. On Wed, 2002-03-13 at 21:09, Robert SHEN wrote: Will it be possible to post it here? - Original Message - From: Brad Tilley [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, March 14, 2002 1:29 AM Subject: Documentation Hello, I am preparing amanda documentation for our office. The documents are specific to us, but general enough to probably be of use to others who have similar amanda implementations (50+ Windows end users and about six departmental Linux servers and workstations). Is there a place where I could publish the documentation (once it is finished) so others could benefit? Thanks, -- Brad Tilley, OUB Sys. Admin. http://bursar.vt.edu/rtilley/pgpkey I disagree -- one of the things that I (and others I've talked to) have noticed is that while Amanda is feature rich, it's documentation is lacking. Why not post it somewhere so other's can read through it and potentially add to it. Even if it's just from the client/end-user perspective, I think it's better than nothing. just my $.02 ;) -- ~ Doug Silver Network Manager Quantified Systems, Inc ~
Re: Exclude list
On Thu, 14 Mar 2002, Jeffrey Auerbach wrote:
I have my exclude lists on the client systems but I am not sure that they are
being used. The total space that gets backed up is about 80MB or so.
According to amstatus it is trying to dump 633MB which is roughly half the
amount of space on the file system. I'm pretty sure that my exclude lists
are correctly working.
How can I tell if gtar is using the exclude list? If I do a ps -auxww | grep
gtar on the client after I run amdump from the server, I get this:
root 74765 5.6 0.4 48444592?? D 11:55am
0:39:54 /usr/localbin/gtar
--create -file /dev/null --directory /usr --one-file-system
--listed-incremental /usr/local/var/amanda/gnutar-lists/smtp0da0s1e_0.new
--sparse --ignore-failed-read --totals .
Notice there is not --exclude.
What did I do wrong?
jeff
first, check in /tmp/amanda for easier debugging. The runtar.*.debug
should have something like this:
runtar: debug 1 pid 29180 ruid 0 euid 0 start time Thu Mar 14 02:25:05
2002
gtar: version 2.4.2p2
running: /usr/local/bin/gtar: gtar --create --file - --directory
/export/home --one-file-system --listed-incremental
/usr/local/var/amanda/gnutar-lists/fred.quantified.net_export_home_0.new
--sparse --ignore-failed-read --totals --exclude-from
/var/amanda/exclude-list .
Also make sure in your amanda.conf file your exclude list is defined and
exists on the client:
define dumptype gtar {
comment Default Gnutar backup
index yes
program GNUTAR
compress client fast
exclude list /var/amanda/exclude-list
}
--
~
Doug Silver
Network Manager
Quantified Systems, Inc
~
Re: Exclude list
It was a spelling error in my amanda.conf file of the exclude list.
I will now accept a slap.
jeff
On Thursday 14 March 2002 01:31 pm, Doug Silver wrote:
On Thu, 14 Mar 2002, Jeffrey Auerbach wrote:
I have my exclude lists on the client systems but I am not sure that they
are being used. The total space that gets backed up is about 80MB or so.
According to amstatus it is trying to dump 633MB which is roughly half
the amount of space on the file system. I'm pretty sure that my exclude
lists are correctly working.
How can I tell if gtar is using the exclude list? If I do a ps -auxww |
grep gtar on the client after I run amdump from the server, I get this:
root74765 5.6 0.4 48444592?? D 11:55am
0:39:54 /usr/localbin/gtar
--create -file /dev/null --directory /usr --one-file-system
--listed-incremental /usr/local/var/amanda/gnutar-lists/smtp0da0s1e_0.new
--sparse --ignore-failed-read --totals .
Notice there is not --exclude.
What did I do wrong?
jeff
first, check in /tmp/amanda for easier debugging. The runtar.*.debug
should have something like this:
runtar: debug 1 pid 29180 ruid 0 euid 0 start time Thu Mar 14 02:25:05
2002
gtar: version 2.4.2p2
running: /usr/local/bin/gtar: gtar --create --file - --directory
/export/home --one-file-system --listed-incremental
/usr/local/var/amanda/gnutar-lists/fred.quantified.net_export_home_0.new
--sparse --ignore-failed-read --totals --exclude-from
/var/amanda/exclude-list .
Also make sure in your amanda.conf file your exclude list is defined and
exists on the client:
define dumptype gtar {
comment Default Gnutar backup
index yes
program GNUTAR
compress client fast
exclude list /var/amanda/exclude-list
}
RE: amandad failure on Sun box
Brian, What does your amanda /etc/inetd.conf entries look like? should look like... amanda dgram udp waitamanda /usr/local/libexec/amandad amandad ./Ben I was getting a selfcheck error on one of my sun boxes I just built amanda on and this is what I found in /var/adm/messages: jupiter inetd[179]: amanda/udp server failing (looping), service terminated Any ideas on what I need to fix here? Also on my MP-RAS box I'm getting this error running selfcheck: ERROR: edaf6.irs.sat NAK: amandad busy Brian Davidson 11710 Plaza America Drive Reston, Virginia 20190 703.261.4694 703.261.5086 Fax
Re: Documentation (Yes, post it!)
On Thu, 14 Mar 2002, Eric Trager wrote: On Thu, 14 Mar 2002, Doug Silver wrote: On 14 Mar 2002, Brad Tilley wrote: I'll send you a copy once it's complete. I wouldn't want to send it the whole list. Apparently, only a handful are interested in it. I disagree -- one of the things that I (and others I've talked to) have noticed is that while Amanda is feature rich, it's documentation is lacking. Why not post it somewhere so other's can read through it and potentially add to it. Even if it's just from the client/end-user perspective, I think it's better than nothing. Well put. Anything documenting successes and failures along the way that ends up searchable in the archives is a Good Thing. I've searched for issues with all kinds of programs on deja.com for years and sometimes it's a lone reply in a single thread that gives me a solution. If you don't have the web space for it, I'd be willing to put it up. Or maybe amanda.org would like it. I've been having massive problems with using amanda with kerberos, in large part due to lack of documentation. You'd better believe that when I finally get all done, I am going to put up a document telling how to do it. --Ruth Anne
Re: Documentation
I have written two docuements. One on excluding data with amanda, and one on how to setup amanda to use gpg. The exclude doc is now available in the DOCS subdir, but it was about six months between when I finished it and a new version of amanda was released. Is there another location that docs are archived and viewable? Do the members of the list really want docs flying around the list. If so I would like to post my new gpg doc. Thanks. Andrew
amrecover not working
I'm getting an error when running amrecover which is coming from my configuration I suppose. It's trying to use 0 as the device, when it should look in the chg-scsi.conf for configuration 0 and see the device name, right? And if I change my tapedev to /dev/nst0 it screws everything else up. Here is the amidxtaped.debug: [amanda@backup amanda]$ cat /tmp/amanda/amidxtaped.20020314124953.debug amidxtaped: debug 1 pid 3048 ruid 504 euid 504 start time Thu Mar 14 12:49:53 2002 amidxtaped: version 2.4.2p2 SECURITY USER root bsd security: remote host backup user root local user amanda amandahosts security check passed 6 amrestore_nargs=6 -h -p 0 aeoluspn ^sd2a$ 20020302 Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = amrestore argv[1] = -h argv[2] = -p argv[3] = 0 argv[4] = aeoluspn argv[5] = ^sd2a$ argv[6] = 20020302 amrestore: could not open tape 0: No such file or directory amidxtaped: amrestore terminated normally with status: 2 amidxtaped: could not stat 0 could not stat 0 amidxtaped: pid 3048 finish time Thu Mar 14 12:49:53 2002 and here are the pertinent lines of my conf files: amanda.conf: runtapes 2 # number of tapes to be used in a single run of amdump tpchanger chg-scsi # the tape-changer glue script tapedev 0 # the no-rewind tape device to be used rawtapedev /dev/null # the raw device to be used (ftape only) changerfile /usr/local/etc/amanda/DailySet1/chg-scsi.conf changerdev /dev/sch0 chg-scsi.conf: number_configs 1 eject 1 # Tapedrives need an eject command sleep 30 # Seconds to wait until the tape gets ready cleanmax100 # How many times could a cleaning tape get used changerdev /dev/sch0 # # Next comes the data for drive 0 # config 0 drivenum0 dev /dev/nst0 startuse0 # The slots associated with the drive 0 enduse 23 # statfile/usr/local/etc/amanda/DailySet1/tape0-slot # The file where the actual slot is stored cleanfile /usr/local/etc/amanda/DailySet1/tape0-clean # The file where the cleanings are recorded usagecount /usr/local/etc/amanda/DailySet1/totaltime
Re: amtape and tape changer problem
Hi, On Thu, Mar 14, 2002 at 09:00:06AM -0500, Zhen Liu wrote: Hi, Thank you very much for your suggestion. Meanwhile, I got another problem...when I enter the command amtape daily show I got the following message: scanning all 7 slots in tape-changer rack: slot1: date X Label DailySet11 amtape: could not load slot DeviceCapabilitiesPage: == Null. Hmm, that is an indicator that the device for the robot is wrong. Can you send the debug output (/tmp/amanda) Thomas -- --- | Thomas Hepper[EMAIL PROTECTED] | | ( If the above address fail try ) | | ( [EMAIL PROTECTED])| ---
Re: Tapeless operation
On Wednesday, March 13, 2002, at 01:34 PM, Joshua Baker-LePain wrote: On Wed, 13 Mar 2002 at 1:21pm, Eric Zylstra wrote I've been looking, but don't know where to find info about tapeless use. The FAQ has an entry on this, but no answer. Any pointers? Do you mean degraded mode (i.e. you usually use a tape, but one wasn't in) or the file: driver? If the latter, you need 2.4.3b3 (or whatever the latest is), and info you need is in amanda(8). If the latter, just set reserve to something greater than 0 and have at it. I have terrabytes of storage available via NFS. I want to backup to that NFS mount. No tape will ever be involved. I'm using 2.4.p2. I've seen discussion before about doing such a thing with older versions. Thanks, EZ
Re: Tapeless operation
On Thu, 14 Mar 2002 at 12:38pm, Eric Zylstra wrote I have terrabytes of storage available via NFS. I want to backup to that NFS mount. No tape will ever be involved. I'm using 2.4.p2. I've seen discussion before about doing such a thing with older versions. Using files on disk like tapes has only ever been supported in the 2.4.2-tapeio branch of CVS, which (as I understand it) became 2.4.3b3. So you'll need to go that route. As I mentioned, details are in amanda(8) in that distrib. Also, look through the recent mailing list archives -- this has been discussed a fair bit recently. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: amtape and tape changer problem
Hi, Thanks for your prompt response...below are the debug of output (/tmp/amanda)...pls check them...I really appreciate your help!!! [root@apple amanda]# more amtape.20020314082946.debug amtape: debug 1 pid 20641 ruid 33 euid 33 start time Thu Mar 14 08:29:46 2002 changer: got exit: 0 str: 1 7 1 0 changer: got exit: 0 str: 1 /dev/nst0 changer: got exit: 2 str: DeviceCapabilitiesPage == NULL could not load slot DeviceCapabilitiesPage: == NULL amtape: pid 20641 finish time Thu Mar 14 08:31:24 2002 [root@apple amanda]# more chg-scsi.20020314083102.debug chg-scsi: debug 1 pid 20651 ruid 33 euid 33 start time Thu Mar 14 08:31:02 2002 ARG [0] : /usr/lib/amanda/chg-scsi ARG [1] : -slot ARG [2] : next Number of configurations: 1 Tapes need eject: Yes barcode reader : No Tapes need sleep: 70 seconds Cleancycles : 20 Changerdevice : /dev/sgb Tapeconfig Nr: 0 Drivenumber : 0 Startslot : 0 Endslot : 6 Cleanslot : -1 Devicename: /dev/nst0 changerident : none SCSITapedev : none tapeident : none statfile : none Slotfile : /etc/amanda/DailySet1/tape5-slot Cleanfile : /etc/amanda/DailySet1/tape0-clean Usagecount: /etc/amanda/DailySet1/totaltime # START OpenDevice OpenDevice : /dev/sgb SCSI_OpenDevice : use SG interface SCSI_OpenDevice : current timeout 6000 SCSI_OpenDevice : timeout set to 6 # START SCSI_Inquiry SCSI_Inquiry start length = 56: # START DecodeSCSI SCSI_ExecuteCommand : INQUIRY 12 00 00 00 38 00 # STOP DecodeSCSI 08 80 02 02 33 00 00 00 41 44 49 43 20 20 20 203...ADIC 46 61 73 74 53 74 6F 72 20 44 4C 54 20 20 20 20FastStor.DLT 30 31 31 38 00 00 00 00 00 00 00 00 00 00 00 000118 00 00 00 00 00 00 00 00 SCSI_Inquiry : end 0 # START PrintInquiry qualifier 0 type8 data_format 2 ansi_version2 ecma_version0 iso_version 0 type_modifier 0 removable 1 vendor_info ADIC prod_ident FastStor DLT prod_version0118 vendor_specific using ident = generic, type = Generic driver tape/robot [generic] # START OpenDevice OpenDevice : /dev/nst0 SCSI_OpenDevice : checking if /dev/nst0 is a sg device No link /dev/nst0 using ident = generic, type = Generic driver tape/robot [generic] need_eject set to 2 ## START get_drive_count get_drive_count : fd 3 # START GenericElementStatus # START SCSI_ModeSense SCSI_ModeSense start length = 255: # START DecodeSCSI SCSI_ExecuteCommand : MODE SENSE 1A 08 3F 00 FF 00 # STOP DecodeSCSI [root@apple amanda]# clear [root@apple amanda]# more chg-scsi.20020314083102.debug chg-scsi: debug 1 pid 20651 ruid 33 euid 33 start time Thu Mar 14 08:31:02 2002 ARG [0] : /usr/lib/amanda/chg-scsi ARG [1] : -slot ARG [2] : next Number of configurations: 1 Tapes need eject: Yes barcode reader : No Tapes need sleep: 70 seconds Cleancycles : 20 Changerdevice : /dev/sgb Tapeconfig Nr: 0 Drivenumber : 0 Startslot : 0 Endslot : 6 Cleanslot : -1 Devicename: /dev/nst0 changerident : none SCSITapedev : none tapeident : none statfile : none Slotfile : /etc/amanda/DailySet1/tape5-slot Cleanfile : /etc/amanda/DailySet1/tape0-clean Usagecount: /etc/amanda/DailySet1/totaltime # START OpenDevice OpenDevice : /dev/sgb SCSI_OpenDevice : use SG interface SCSI_OpenDevice : current timeout 6000 SCSI_OpenDevice : timeout set to 6 # START SCSI_Inquiry SCSI_Inquiry start length = 56: # START DecodeSCSI SCSI_ExecuteCommand : INQUIRY 12 00 00 00 38 00 # STOP DecodeSCSI 08 80 02 02 33 00 00 00 41 44 49 43 20 20 20 203...ADIC 46 61 73 74 53 74 6F 72 20 44 4C 54 20 20 20 20FastStor.DLT 30 31 31 38 00 00 00 00 00 00 00 00 00 00 00 000118 00 00 00 00 00 00 00 00 SCSI_Inquiry : end 0 # START PrintInquiry qualifier 0 type8 data_format 2 ansi_version2 ecma_version0 iso_version 0 type_modifier 0 removable 1 vendor_info ADIC prod_ident FastStor DLT prod_version0118 vendor_specific using ident = generic, type = Generic driver tape/robot [generic] # START OpenDevice OpenDevice : /dev/nst0 SCSI_OpenDevice : checking if /dev/nst0 is a sg device No link /dev/nst0 using ident = generic, type = Generic driver tape/robot [generic] need_eject set to 2 ## START get_drive_count get_drive_count : fd 3 # START GenericElementStatus # START SCSI_ModeSense SCSI_ModeSense start length = 255: # START DecodeSCSI SCSI_ExecuteCommand : MODE SENSE 1A 08 3F 00 FF 00 # STOP DecodeSCSI SCSI_ModeSense end: 0 # START DecodeModeSense 65 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00e... 1D 12 00 56 00 01 00 01 00 07 00 00 00 00 00 52...V...R 00 01 00 00 1E 02 00 00 1F 0E 0A 00 0A 0B 00 03 00 00 00 00 00 00 00 00 00 2C 43 6F 70 79 72 69..Copyri 67 68 74
Taper process hang with D state
Hi, I have problem with Amanda recently. The tape rate was a little bit slow from the very beginning but it wouldn't hang until recently. The following is a process list and one of the taper process is hang with state D. Does anyone have the same problem? How could it be solved? backup 16978 0.0 0.4 2180 1068 ?S00:45 0:00 /bin/sh /usr/sbin/amdump DailySet1 backup 16986 0.0 0.4 2244 1104 ?S00:45 0:00 /usr/lib/amanda/driver DailySet1 backup 16988 0.1 0.6 2828 1620 ?S00:45 0:42 taper DailySet1 backup 16989 0.2 0.4 2536 1248 ?S00:45 1:00 dumper DailySet1 backup 16990 0.0 0.4 2444 1172 ?S00:45 0:00 dumper DailySet1 backup 16991 0.0 0.6 2844 1560 ?D00:45 0:28 taper DailySet1 backup 16992 0.0 0.4 2528 1240 ?S00:45 0:00 dumper DailySet1 backup 16994 0.0 0.3 2324 984 ?S00:45 0:00 dumper DailySet1 backup 17021 0.0 0.2 2116 748 ?S00:52 0:00 /usr/lib/amanda/sendbackup backup 17022 0.0 0.2 1628 652 ?S00:52 0:00 /bin/gzip --best backup 17023 0.1 0.3 2104 840 ?S00:52 0:47 /usr/lib/amanda/sendbackup backup 17025 0.0 0.5 3180 1340 ?S00:52 0:00 sh -c /bin/tar -tf - 2/dev/null | sed -e 's/^\.//' backup 17026 0.0 0.2 1568 632 ?S00:52 0:14 /bin/tar -tf - backup 17027 0.0 0.1 1312 448 ?S00:52 0:00 sed -e s/^\.// Besides that, the dumper rate is quite slow as well. It only has 193KB/s sometimes to dump from a local harddrive. Any help would be appreciated. Thanks in advance, Ben
Re: Restoring w/o amanda
This works, but it doesn't work the way I thought it might. I didn't understand IRG (Inter Record Gaps) but now, I think I have a better grasp of it. ... You've got the right idea, but they are not called inter record gaps. Those are the spaces (if the technology uses them) between records on the tape, i.e. between the 32 KByte blocks. What you're seeing are called tape marks, and they indicate end of file. Amanda writes one between each image (client/disk) and dd stops reading when it sees one (because the Unix read() returns zero, indicating end of file). It isn't as convenient as I thought it would be, but it does the job. Remember that most people have lots of clients and disks scattered thoughout a given tape. So restoring the whole tape at once would probably be a really bad thing. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Problem with building amanda...
Hi! I'm trying to build amanda on a Solaris 2.6 box (I don't know if there are other things that would describe it better -- if you can think of anything, please let me know...). I ran configure with the following line (running as root): # ./configure --with-user=amanda --with-group=root --prefix=/usr/amanda --without-server --with-index-server=einstein.mgh.harvard.edu The only odd output from configure that I noticed was: checking whether posix fcntl locking works... no checking whether flock locking works... no checking whether lockf locking works... no checking whether lnlock locking works... no configure: warning: *** No working file locking capability found! configure: warning: *** Be VERY VERY careful. I then tried to do a 'make'. The output is below. What do I need to do to get DATAMODEL_NATIVE specified? Thanks, Ricky Making all in config Making all in common-src /usr/bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c alloc.c gcc -DHAVE_CONFIG_H -I. -I. -I../config -I./../regex-src -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -g -O2 -c alloc.c -o alloc.o In file included from /usr/include/sys/turnstile.h:12, from /usr/include/sys/t_lock.h:20, from /usr/include/sys/vnode.h:37, from /usr/include/sys/stream.h:21, from /usr/include/netinet/in.h:38, from amanda.h:218, from alloc.c:33: /opt/Summertime_97.sparc/lib/gcc-lib/sparc-sun-solaris2.5/2.7.2.2/ \ include/sys/param.h:187: warning: `NBBY' redefined /usr/include/sys/select.h:45: warning: this is the location of the previous definition In file included from /usr/include/sys/stream.h:26, from /usr/include/netinet/in.h:38, from amanda.h:218, from alloc.c:33: /usr/include/sys/model.h:32: #error No DATAMODEL_NATIVE specified *** Error code 1 make: Fatal error: Command failed for target `alloc.lo' Current working directory /usr/amanda/src/amanda-2.4.2p2/common-src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' - Richard MorseSystem Administrator MGH Biostatistics Center 50 Staniford St. Rm 560 [EMAIL PROTECTED] 617/724-9830
Backing up index files
Hello everybody. Each day that Amanda runs, I get a message similar to the following: /-- sbs/usr lev 1 STRANGE sendbackup: start [sbs:/usr level 1] sendbackup: info BACKUP=/usr/linux/bin/gtar sendbackup: info RECOVER_CMD=/usr/linux/bin/gtar -f... - sendbackup: info end ? gtar: ./local/etc/amanda/Gemini/index/sbsdp/_gemini_disk3_archive/20020313_1.gz.tm p: Warning: Cannot stat: No such file or directory | Total bytes written: 37652480 (36MB, 836kB/s) sendbackup: size 36770 sendbackup: end \ This looks to me to be a temporary index file that has been removed after tar started. Is this a problem? I wouldn't think so, but I'd like to make sure. If it isn't a problem, is there a way to prevent it? Should I not be backing up my indexes? If I should, am I doing it wrong? Thanks for you help! Anthony Valentine
verification of tape
Is it possible to have a tape verified by xfsdump or xfsrestore if those utilities are combined with Amanda under SGI IRIX? I am evaluating Amanda for backups but verification seems to be a problem with xfsdump and xfsrestore utilities. Can Amanda overcome this somehow? I have XFS filesystems on all the SGIs I manage. Thanks, Dow
amrecover not working
I'm getting an error when running amrecover which is coming from my configuration I suppose. It's trying to use 0 as the device, when it should look in the chg-scsi.conf for configuration 0 and see the device name, right? And if I change my tapedev to /dev/nst0 it screws everything else up. Here is the amidxtaped.debug: [amanda@backup amanda]$ cat /tmp/amanda/amidxtaped.20020314124953.debug amidxtaped: debug 1 pid 3048 ruid 504 euid 504 start time Thu Mar 14 12:49:53 2002 amidxtaped: version 2.4.2p2 SECURITY USER root bsd security: remote host backup user root local user amanda amandahosts security check passed 6 amrestore_nargs=6 -h -p 0 aeoluspn ^sd2a$ 20020302 Ready to execv amrestore with: path = /usr/local/sbin/amrestore argv[0] = amrestore argv[1] = -h argv[2] = -p argv[3] = 0 argv[4] = aeoluspn argv[5] = ^sd2a$ argv[6] = 20020302 amrestore: could not open tape 0: No such file or directory amidxtaped: amrestore terminated normally with status: 2 amidxtaped: could not stat 0 could not stat 0 amidxtaped: pid 3048 finish time Thu Mar 14 12:49:53 2002 and here are the pertinent lines of my conf files: amanda.conf: runtapes 2 # number of tapes to be used in a single run of amdump tpchanger chg-scsi # the tape-changer glue script tapedev 0 # the no-rewind tape device to be used rawtapedev /dev/null # the raw device to be used (ftape only) changerfile /usr/local/etc/amanda/DailySet1/chg-scsi.conf changerdev /dev/sch0 chg-scsi.conf: number_configs 1 eject 1 # Tapedrives need an eject command sleep 30 # Seconds to wait until the tape gets ready cleanmax100 # How many times could a cleaning tape get used changerdev /dev/sch0 # # Next comes the data for drive 0 # config 0 drivenum0 dev /dev/nst0 startuse0 # The slots associated with the drive 0 enduse 23 # statfile/usr/local/etc/amanda/DailySet1/tape0-slot # The file where the actual slot is stored cleanfile /usr/local/etc/amanda/DailySet1/tape0-clean # The file where the cleanings are recorded usagecount /usr/local/etc/amanda/DailySet1/totaltime
Two Drives
Dear Amanda Users, I have two tape drives and would like to split my backups between them. I understand that amanda does not presently have an automatic way to do this. To do it manually, do I simply create two schedules (say Daily-A and Daily-B) and run them both independently? One of my drives is an Onstream ADR50. I understand there is a problem with this drive and amanda. Does it mean that the drive is completely useless with amanda? Thanks, Dick
Bad file descriptor
Dear Amanda Users,
I continue to have the problems listed below in the log. I have
specified a tapetype length of 4 meg (while the tape is advertised
at 66000 meg) but I still get out of tape in addition to Bad file
descriptor which I was tole in a previous reply is related to hitting
EOT.
I also assume the data write: Broken pipe is due to the out of tape
error.
What do I need to do to keep amanda from trying to put more on a tape
than will fit.
Thanks,
Dick
These dumps were to tape Daily4.
*** A TAPE ERROR OCCURRED: [[writing file: Bad file descriptor]].
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: Daily5.
FAILURE AND STRANGE DUMP SUMMARY:
vulcan.int /usr lev 0 FAILED [out of tape]
vulcan.int /usr lev 0 FAILED [data write: Broken pipe]
vulcan.int /usr lev 0 FAILED [dump to tape failed]
gorn.ameri / lev 0 FAILED [out of tape]
gorn.ameri / lev 0 FAILED [data write: Broken pipe]
gorn.ameri / lev 0 FAILED [dump to tape failed]
andorian.a / lev 0 FAILED [out of tape]
andorian.a / lev 0 FAILED [data write: Broken pipe]
andorian.a / lev 0 FAILED [dump to tape failed]
solo.ameri /idebigger lev 0 FAILED [out of tape]
solo.ameri /idebigger lev 0 FAILED [data write: Broken pipe]
solo.ameri /idebigger lev 0 FAILED [dump to tape failed]
maul.ameri / lev 0 FAILED [out of tape]
maul.ameri / lev 0 FAILED [data write: Broken pipe]
maul.ameri / lev 0 FAILED [dump to tape failed]
gorn.ameri /ideroot2 lev 0 FAILED [out of tape]
gorn.ameri /ideroot2 lev 0 FAILED [data write: Broken pipe]
gorn.ameri /ideroot2 lev 0 FAILED [dump to tape failed]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:04
Run Time (hrs:min) 6:34
Dump Time (hrs:min)0:18 0:00 0:18
Output Size (meg)2164.60.0 2164.6
Original Size (meg) 2164.60.0 2164.6
Avg Compressed Size (%) -- -- --(level:#disks ...)
Filesystems Dumped 19 0 19 (1:19)
Avg Dump Rate (k/s) 2063.4-- 2063.4
Tape Time (hrs:min)0:16 0:00 0:16
Tape Size (meg) 2165.20.0 2165.2
Tape Used (%) 5.50.05.5 (level:#disks ...)
Filesystems Taped19 0 19 (1:19)
Avg Tp Write Rate (k/s) 2298.3-- 2298.3
FAILED AND STRANGE DUMP DETAILS:
/-- vulcan.int /usr lev 0 FAILED [data write: Broken pipe]
sendbackup: start [vulcan.internal.americom.com:/usr level 0]
sendbackup: info BACKUP=/sbin/dump
sendbackup: info RECOVER_CMD=/sbin/restore -f... -
sendbackup: info end
| DUMP: Date of this level 0 dump: Thu Mar 14 06:21:39 2002
| DUMP: Dumping /dev/hda2 (/usr) to standard output
| DUMP: Exclude ext3 journal inode 8
| DUMP: Label: /usr
| DUMP: mapping (Pass I) [regular files]
| DUMP: mapping (Pass II) [directories]
| DUMP: estimated 3236344 tape blocks.
| DUMP: Volume 1 started with block 1 at: Thu Mar 14 06:22:06 2002
| DUMP: dumping (Pass III) [directories]
| DUMP: dumping (Pass IV) [regular files]
| DUMP: 32.56% done at 3512 kB/s, finished in 0:10
| DUMP: 78.77% done at 4249 kB/s, finished in 0:02
| DUMP: 100.00% done at 4494 kB/s, finished in 0:00
| DUMP: 100.00% done at 4617 kB/s, finished in 0:00
| DUMP: 100.00% done at 4691 kB/s, finished in 0:00
| DUMP: 100.00% done at 4740 kB/s, finished in 0:00
| DUMP: 100.00% done at 4774 kB/s, finished in 0:00
| DUMP: 100.00% done at 4801 kB/s, finished in 0:00
| DUMP: 100.00% done at 4821 kB/s, finished in 0:00
| DUMP: 100.00% done at 4837 kB/s, finished in 0:00
| DUMP: 100.00% done at 4851 kB/s, finished in 0:00
| DUMP: 100.00% done at 4854 kB/s, finished in 0:00
| DUMP: 100.00% done at 4859 kB/s, finished in 0:00
| DUMP: 100.00% done at 4868 kB/s, finished in 0:00
| DUMP: 100.00% done at 4876 kB/s, finished in 0:00
| DUMP: 100.00% done at 4883 kB/s, finished in 0:00
| DUMP: 100.00% done at 4889 kB/s, finished in 0:00
| DUMP: 100.00% done at 4894 kB/s, finished in 0:00
| DUMP: 100.00% done at 4899 kB/s, finished in 0:00
| DUMP: 100.00% done at 4904 kB/s, finished in 0:00
| DUMP: 100.00% done at 4908 kB/s, finished in 0:00
| DUMP: 100.00% done at 4912 kB/s, finished in 0:00
| DUMP: 100.00% done at 4915 kB/s, finished in 0:00
| DUMP: 100.00% done at 4914 kB/s, finished in 0:00
| DUMP: 100.00% done at 4917 kB/s, finished in 0:00
| DUMP: 100.00% done at 4920 kB/s, finished in 0:00
| DUMP: 100.00% done at 4923 kB/s, finished in 0:00
| DUMP: 100.00% done at 4926 kB/s, finished in 0:00
| DUMP: 100.00% done at 4928 kB/s, finished in 0:00
| DUMP: 100.00% done at 4930 kB/s, finished in 0:00
| DUMP: 100.00% done at 4932 kB/s, finished in 0:00
| DUMP: 100.00% done at 4934 kB/s, finished in 0:00
| DUMP: 100.00% done at
libtool problem with amanda-2.4.3b3 build
I recently posted some build data about versions 2p2 and 3b3 with regard to the results of various configure options related to libtool as well as changing the version of libtool... The 2p2 builds performed without a problem when --disable-libtool was set or unset. The 3b3 build dies with libtool errors REGARDLESS of whether --disable-libtool is set or not. Would this not indicate a problem with the build? Regardless of whether or not there is a problem with libtool on the Alpha/Tru64 box?... If one says --disable-libtool what should one expect? A broken build with libtoool errors as the cuplrit? Maybe my problem is not libtool when the --disable-libtool option is specified... thx dk
Re: Relabel whitout dataloss ?
Is it possible to relabel a tape, but preserve the existing data on the tape ? No. It's a fundamental aspect of tapes that any write operation sets end of device (i.e. there ain't nothing after that). Some devices support partitioning, but that's a completely different animal and not relevant to Amanda. Of course, if all else fails, I can label each tape before I start the backup, but I'd rather label them all in one go Better safe than sorry. Relabel a few just before you need them. Gerhard den Hollander John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: more dumpers please...
I have a client with 4 fast processors and would like to use at least 2 or 3 of them if possible for dumps. ... Dumps can be very I/O bound. Make sure you have enough bandwidth as well. Is it possible to get amanda to dump more than 1 partition on the same client at a time to the backup server? ... Set maxdumps in either the global area of amanda.conf or in the specific dumptypes (see amanda(8)). Trevor. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amandad failure on Sun box
I was getting a selfcheck error on one of my sun boxes I just built amanda on and this is what I found in /var/adm/messages: jupiter inetd[179]: amanda/udp server failing (looping), service terminated Any ideas on what I need to fix here? Have you gone through the FAQ checklists: http://amanda.sourceforge.net/fom-serve/cache/16.html http://amanda.sourceforge.net/fom-serve/cache/140.html Also on my MP-RAS box I'm getting this error running selfcheck: ERROR: edaf6.irs.sat NAK: amandad busy What version of Amanda? What's in the corresponding /tmp/amanda/amandad*debug file? Brian Davidson John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrecover is kicking my butt......
... When ever I attempt to do a amrecover of the directory on /var/mail I get the following: Ummm, you didn't post what amrecover was saying. That might help :-). But I'll save you one round trip. What's in the corresponding /tmp/amanda/amrecover*debug file. Should be something like this: Started amidxtaped with arguments 6 -h -p ... Exec'ing /usr/sbin/ufsrestore with arguments: restore xbf 2 - /conte/WWW/Fall01/Sorted/alllabs And what's in the corresponding /tmp/amanda/amidxtaped*debug file back on the server? Don John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
unsub
unsubscribe amanda-users
Re: verification of tape
Is it possible to have a tape verified by xfsdump or xfsrestore if those utilities are combined with Amanda under SGI IRIX? ... The current sources should do that just fine. What version of Amanda are you using? Amanda for backups but verification seems to be a problem with xfsdump and xfsrestore utilities. ... What does seems to be a problem mean? Are you getting error messages? What are they? Dow John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Taper process hang with D state
... The following is a process list and one of the taper process is hang with state D. ... The 'D' state means the process is stuck in the kernel doing I/O. That is either a hardware or an OS (kernel) problem. You'll have to start looking there. Nothing Amanda does should be able to cause this. Ben John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amrecover not working
I'm getting an error when running amrecover ... Then why didn't you post the error message??? :-) In any case, I can guess what's wrong ... ... It's trying to use 0 as the device, when it should look in the chg-scsi.conf for configuration 0 and see the device name, right? ... No. Amrecover does not support the use of changers (yet). You need to tell it (via the -d option or the settape command) the actual tape device name to use, and you'll have to load the tape yourself. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Backing up index files
This looks to me to be a temporary index file that has been removed after tar started. Yup. Is this a problem? ... Nope. If it isn't a problem, is there a way to prevent it? ... You should be able to give GNU tar an exclusion pattern. I **think** the following would do it: exclude ./local/etc/amanda/Gemini/index/*.tmp but GNU tar exclusion patterns give me a headache and you should test this thoroughly. Should I not be backing up my indexes? ... I certainly do (but I use dump and don't see the problem you do). Anthony Valentine John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: amlabel problem
This is what I'm getting when I try to do an amlabel to a new tape. Is this an amlabel problem or a tape drive problem? What version of Amanda? What OS? rewinding, reading label, reading label: Value too large for defined data type I *think* what this says is that amlabel was built for 32 bit file systems but the kernel (or libc?) is using 64 bit structures (but that's kind of a wild guess). Did you build Amanda yourself or use some evil, you get what you deserve, pre-packaged thing :-)? Trevor. John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Problem with building amanda...
The only odd output from configure that I noticed was: checking whether posix fcntl locking works... no checking whether flock locking works... no checking whether lockf locking works... no checking whether lnlock locking works... no configure: warning: *** No working file locking capability found! configure: warning: *** Be VERY VERY careful. That's bad. It usually means your compiler is broken. And sure enough, you've fallen for the classic forgot to update gcc when the OS was updated problem: /opt/Summertime_97.sparc/lib/gcc-lib/sparc-sun-solaris2.5/2.7.2.2/ \ Notice the solaris2.5 in the name? That means gcc was built for Solaris 2.5. Prior to recent versions, gcc was *extremely* sensitive to having to be built specifically for the OS you were running. FYI, I use gcc 2.95.3 on my Solaris 2.6 boxes and it works fine (of course, I built it on 2.6 as well). Ricky John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Re: Backing up index files
* John R. Jackson ([EMAIL PROTECTED]) [20020314 23:15] thus spake: This looks to me to be a temporary index file that has been removed after tar started. Yup. Is this a problem? ... Nope. If it isn't a problem, is there a way to prevent it? ... You should be able to give GNU tar an exclusion pattern. I **think** the following would do it: exclude ./local/etc/amanda/Gemini/index/*.tmp I'd use something like (actually I think you gave me the hint on this one a while ago!): exclude ./local/etc/amanda/Gemini/index/*/*/*.tmp ^ ^ | | | disk/device hostname but you're right, gnutar exclude lists are a pain in the butt! but GNU tar exclusion patterns give me a headache and you should test this thoroughly. Should I not be backing up my indexes? ... I certainly do (but I use dump and don't see the problem you do). Anthony Valentine John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED] jf -- Dreams and belief have gone Time, life itself goes on
does amlabel format a tape?
as title
admanda problem
hello all, 1) i have both windows and os/2 clients down here. now with amanda installed on my linux box can i take back-up's of both those os's i.e os/2 and win. 2) how can i take back-up's on os/2 operating system. should i include any script in my os/2 clients. 3) what all should i include in my crontab file? 4) i have already enabled samba on my linux box and able to browse win files, is there any other tool even to view os/2 files on my linux box? __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ ---BeginMessage--- We are unable to deliver the message from [EMAIL PROTECTED] to [EMAIL PROTECTED]. The amanda-users group is for archival use only and does not accept direct postings. If you want to post to the actual email list, please send your message to [EMAIL PROTECTED] For further assistance, please email [EMAIL PROTECTED] or visit http://help.yahoo.com/help/us/groups/ ---BeginMessage--- hello all, 1) i don't have tape drive down here. can i use one of my disk partition as back-up device and can i take back-up's on my linux-box. 2) i have both window's os/2 operating system clients down here, can i even take back-up's frpm os/2 clients on my linux box. 3) if and if there is a chance of backing-up the os/2 clients , should i include any script in my client's end. 4) wha sort of script should i include in my window's client. __ Do You Yahoo!? Try FREE Yahoo! Mail - the world's greatest free email! http://mail.yahoo.com/ ---End Message--- ---End Message---
