Re: different backup for sub directory
Leonid Mamchenkov wrote:
JBL Just add:
JBL
JBL exclude ./local
JBL
JBL to your dumptype for /usr. See the example disklist and/or amanda.conf
JBL for examples.
And you don't even need to modify the full dumptype, if you have
a recent amanda version (at least 2.4.3). You now can define a
dumptype inline in your disklist:
your.client /usr/local incremental
your.client /usr {
full
exclude ./local
} 1
--
Paul Bijnens, XplanationTel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512
http://www.xplanation.com/ email: [EMAIL PROTECTED]
***
* I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, *
* quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, *
* stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, *
* PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, *
* kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...*
* ... Are you sure? ... YES ... Phew ... I'm out *
***
Re: Redhat 9?
Les Mikesell [EMAIL PROTECTED] writes: I posted a couple of messages about amflush hanging after installing the libc/kernel updates to RedHat 9. By hang, do you mean consume 100% of CPU for days on end? Yes, I am seeing that on RH9. Nice to know I am not alone. Thanks for the tip about installing 2.4.4; I will give that a try. - Pat
Re: add new clients, lost order scheduleing, tape isn't streaming
On Friday 30 May 2003 05:27, Paul Bijnens wrote: Gene Heskett wrote: Now the client is a bit slow, a 500mhz K6-III, so I expected the level 0's this would cause would take a while. This also brought my disklist entries up to 44. The string that controls the dumporder in amanda.conf: dumporder *should* cause the largest first, then descending order, and there are enough S's to cover all DLE's such that once the first dump is ready, the drive streams till its done. They all start together, but which dump will be ready first you think? It's probably one of the smaller dumps! I guess not all 44 dumpers will be active, because you probably have other constraints (maxdumpers per host, per disk, bandwith etc,). Miss-conception I think, 44 DLE's, but its the default 4 dumpers in the amanda.conf (on the server). Taper starts taping as soon it receives the first file to tape, and that's probably a smaller one. So basicly it had the 1 dumper running on the client, and 3 running on itself, and they went thru the biggest 33 files on the server while the 1st one on the client completed. Mmm, the counts are correct, but they didn't 100% start with the biggest ones on the server since it had taped 650 megabytes of server stuff by then, but the server still had at least 2 to do yet that were more than the 650 megs the first 33 had totalled, each. Thats what got my attention. Using less dumpers should work better. Less than 4? --from amanda.conf- inparallel 4# maximum dumpers that will run in parallel (max 63) # this maximum can be increased at compile-time, # modifying MAX_DUMPERS in server-src/driverio.h [...] dumporder # specify the priority order of each dumper # s - smallest size # S - biggest size # t - smallest time # T - biggest time # b - smallest bandwitdh # B - biggest bandwitdh # try BTBTBTBTBTBT if you are not holding # disk constrained # BUT, if you want streaming, start with the big ones and work down --- Maybe I should change the first 5 or 6 to T's? OTOH, if it starts taping when the first one is done, Theres not a heck of a lot I can do, that machine is overclocked as far as it will without effecting the uptimes now. If it held them in the holding disk to achieve the specified order, it would have waited over 2:20 for the first, actually the biggest, after compress client best compression. According to amplot, the tape was running from about :45 to about 1:15, then was resting for about another 50 minutes before fireing up and finishing the job at the 3:55 mark, certainly not as tape wastefull as running without a holding disk would be. And either way the total runtime would be pretty much the same for the same set of conditions. Thanks Paul. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Dump too big for tape
Title: Dump too big for tape
Hi all -
Well, here I am againsame server different issue. My backups are still failing on that client with a timeout and I'm still searching to figure out why. But that's not why I'm here today. Running amanda 2.4.2p2 on a RH8 box with a seagate stand alone with 125m DDS3 12/24GB DAT tapes and hardware compression is turned off.
Report says:
These dumps were to tape isymmdaily01.
The next tape Amanda expects to use is: isymmdaily06.
FAILURE AND STRANGE DUMP SUMMARY:
www.iclear / lev 0 FAILED [mesg read: Connection timed out]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min) 0:02
Run Time (hrs:min) 3:57
Dump Time (hrs:min) 0:58 0:58 0:00
Output Size (meg) 5798.6 5787.0 11.7
Original Size (meg) 5798.6 5787.0 11.7
Avg Compressed Size (%) -- -- -- (level:#disks ...)
Filesystems Dumped 10 9 1 (1:1)
Avg Dump Rate (k/s) 1717.8 1716.1 3433.8
Tape Time (hrs:min) 1:32 1:32 0:00
Tape Size (meg) 5798.9 5787.2 11.7
Tape Used (%) 50.1 50.0 0.1 (level:#disks ...)
Filesystems Taped 10 9 1 (1:1)
Avg Tp Write Rate (k/s) 1072.5 1072.4 1102.8
FAILED AND STRANGE DUMP DETAILS:
/-- www.iclear / lev 0 FAILED [mesg read: Connection timed out]
sendbackup: start [www.iclear.com:/ level 0]
sendbackup: info BACKUP=/usr/local/bin/tar
sendbackup: info RECOVER_CMD=/usr/local/bin/tar -f... -
sendbackup: info end
\
NOTES:
planner: Dump too big for tape: full dump of isymmdb:/var delayed.
taper: tape isymmdaily01 kb 5938112 fm 10 [OK]
DUMP SUMMARY:
DUMPER STATS TAPER STATS
HOSTNAME DISK L ORIG-KB OUT-KB COMP% MMM:SS KB/s MMM:SS KB/s
--- --
isymmdb /etc 0 2336 2336 -- 0:04 618.6 0:01 1739.3
isymmdb /export 0 78560 78560 -- 0:21 3803.3 1:25 922.7
isymmdb /opt 0 371488 371488 -- 2:08 2911.2 5:51 1058.6
isymmdb -oracle/admin 0 2897184 2897184 -- 9:27 5107.0 44:45 1079.1
isymmdb /usr 0 695872 695872 -- 5:30 2106.8 10:45 1079.1
isymmdb /var 1 11936 11936 -- 0:03 3432.9 0:11 1102.8
web.isym /etc 0 2688 2688 -- 0:01 2700.6 0:03 809.1
web.isym /home 0 64576 64576 -- 0:03 20024.3 1:01 1055.0
web.isym /var 0 229344 229344 -- 0:17 13575.1 3:33 1078.4
www.icle / 0 FAILED ---
xfer.icl / 0 1583808 1583808 -- 39:42 664.8 24:42 1069.0
(brought to you by Amanda version 2.4.2p2)
The interesting part is that for tape size it says: 5798.9 while my estimate says 5798.6and my entry in amanda.conf for this tape says:
define tapetype Verbatim-125m {
comment Verbatim 4mm-125m DAT
length 11576 mbytes
filemark 0 kbytes
speed 1077 kbytes
}
As I look back through my reports (2 days earlier my backup was 5950.2 and it says my tape size was 5950.5) I see that my tape size is always reading .3 over my estimated dump size.
First, is this normal that my tape size never displays what it actually is.
Should I chalk this up to a media problem? When my failing client was working, I was successfully backing up 10229.2.
Any input appreciated. THANKS.
rapc
Rebecca A. Crum
Systems Administrator
Unterberg Associates, P.C.
(219) 736-5579 ext. 184
Re: add new clients, lost order scheduleing, tape isn't streaming
Resent on the list Jon, I'm bouncing again On Friday 30 May 2003 04:07, Jon LaBadie wrote: On Fri, May 30, 2003 at 03:15:54AM -0400, Gene Heskett wrote: Hi everybody; Now the client is a bit slow, a 500mhz K6-III, so I expected the level 0's this would cause would take a while. This also brought my disklist entries up to 44. The string that controls the dumporder in amanda.conf: dumporder *should* cause the largest first, then descending order, and there are enough S's to cover all DLE's such that once the first dump is ready, the drive streams till its done. I think you have the wrong idea of dumporder. My understanding is this: One parameter in amanda.conf is dumpers, default I think to 4. This is how many DLE's can be simultaneously dumping. Your dumporder needs be no longer than this number. Because they are simultaneous, you might start DLE's hypothetically of 20GB, 18GB, and 15GB. The the 4th dumper doing the 4th largest might get one of 0.5GB. This could finish rapidly and keep getting assigned the next largest DLE which should be smaller than 0.5GB and also finish fast. So lots of DLE's could finish before your large one even if the large ones started first. However, I have no idea why your large one started later rather than according to the scheme above. Oh it started first alright according to amstatus, its just that it took it about 2:20 to complete that one dump on the old workhorse. According to amplot, it fired up the tape and wrote for about 20 minutes, then rested the tape for another 50 minutes before it started writing that first dump. And it did the first 33 DLE's on the server in that first 20 minute write, not all of which were the largest. The only way it could have done that would be for the last 2 dumpers to always draw an uncompressed DLE that was only an incremental. And the next largest dump was on the server was set for 'compress client best'. One thing I think I'll do is write another dump spec, the same as comp-root-tar but it says 'compress server best' for those DLE's on the server proper. Or is that just robbing peter to pay george? There should be less data to shuffle thru the le0 connection if its 'client' I'd think. I think I need my first tea of the day, this isn't jelling too well... -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: Dump too big for tape
On Fri, 30 May 2003 at 9:30am, Rebecca Pakish Crum wrote
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 3:57
Dump Time (hrs:min)0:58 0:58 0:00
Output Size (meg)5798.6 5787.0 11.7
Original Size (meg) 5798.6 5787.0 11.7
Avg Compressed Size (%) -- -- --(level:#disks
..)
Filesystems Dumped 10 9 1 (1:1)
Avg Dump Rate (k/s) 1717.8 1716.1 3433.8
Tape Time (hrs:min)1:32 1:32 0:00
Tape Size (meg) 5798.9 5787.2 11.7
Tape Used (%) 50.1 50.00.1 (level:#disks
..)
Filesystems Taped10 9 1 (1:1)
Avg Tp Write Rate (k/s) 1072.5 1072.4 1102.8
NOTES:
planner: Dump too big for tape: full dump of isymmdb:/var delayed.
taper: tape isymmdaily01 kb 5938112 fm 10 [OK]
As I look back through my reports (2 days earlier my backup was 5950.2
and it says my tape size was 5950.5) I see that my tape size is always
reading .3 over my estimated dump size.
First, is this normal that my tape size never displays what it actually
is.
Nope, that's normal. Output Size is the size of all the dump images.
Remember that amanda puts a 32KB header on each of those before they go to
tape. 10 filesystems * 32KB is 320KB, or about .3 MB. QED.
--
Joshua Baker-LePain
Department of Biomedical Engineering
Duke University
RE: Dump too big for tape
Nope, that's normal. Output Size is the size of all the dump images. Remember that amanda puts a 32KB header on each of those before they go to tape. 10 filesystems * 32KB is 320KB, or about .3 MB. QED. Yeah, output size should be fine...not even 6 gigs on a 12 gig tape that used to be backing up almost 11 successfully. That's my concern. Even with the .3 megs amanda is throwing on there, I'm not even coming close to tape end. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Dump too big for tape
On Fri, 30 May 2003 at 9:47am, Rebecca Pakish Crum wrote Well, how big is that /var? From yesterday's report: isymmdb /var 0176096 176096 --0:59 2985.8 2:43 1079.7 Yes, but how big is it today? :) Check in last night's amdump.N file (should be amdump.1) to see how big the estimate was. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
RE: Configuring RH7.2 Amanda out of the box - error accessing Amanda hosts file.
Ok my amandahosts file looks like this. dilmom.as400resource.com amanda I have run the following chown amanda.amanda /home/amanda/.amandahosts and chmod 600 /home/amanda/.amandahosts and this is what I get from amcheck Amanda Tape Server Host Check - Holding disk /usr/amanda/dumps: 16945236 KB disk space available, that's plenty NOTE: skipping tape-writable test Tape kdpdfri label ok NOTE: info dir /var/lib/amanda/kdp/curinfo: does not exist NOTE: it will be created on the next run Server check took 0.020 seconds Amanda Backup Client Hosts Check ERROR: dilmom: [access as amanda not allowed from [EMAIL PROTECTED] open of /home/amanda/.amandahosts failed Client check: 1 host checked in 0.008 seconds, 1 problem found (brought to you by Amanda 2.4.2p2) This is all from my disk crash - I decided for the sake of my sanity to change everything back to use the amanda profile. I can sort out the windows shares by creating another user on each PC. What I am trying to acheive is to configure up the RH7.2 out of the box amanda software. I've managed to get all my config files back from the tapes. Thanks for your help. Regards Kevin -Original Message- From: Jon LaBadie [mailto:[EMAIL PROTECTED] Sent: 29 May 2003 17:42 To: Amanda (E-mail) Subject: Re: Configuring RH7.2 Amanda out of the box - error accessing amandah osts file. On Thu, May 29, 2003 at 05:17:01PM +0100, Kevin Passey wrote: Can anybody help me here. I am trying to configure Amanda that is shipped with RH7.2 and it is giving me one error when I run AMCHECK. Which basically says my amanda user cannot access the amandahosts file in /home/Administrator Is Administrator the amanda user? Is there a file, .amandahosts in ~Administrator? What are its contents? What are its permissions? What additional information can you glean from the amcheck debug log in /tmp/amanda? -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Questions about AMANDA
Hi, I have a backup policy and I would like to convert it to Amanda. The backup policy is: One full backup - One time per month (without following incremental backups) One full backup - One time per week and incrementals backups until the next week. For example, if I make a full backup on monday, the incrementals backups should be from tuesday until sunday. My problem is, how can I set up Amanda to do this ? Another questions: How can I restore a backup using Amanda ? If one of the clients that have been backuped is down (lose all data), How can I restore a backup on that client ? How can I change the label of a tape ? Sorry for this questions. I'm a newbie Amanda user. Thanks, Roberto Samarone Araujo
RE: Dump too big for tape
Well, how big is that /var? From yesterday's report: isymmdb /var 0176096 176096 --0:59 2985.8 2:43 1079.7 -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Disaster recovery dump cycles
Hi, I'm just starting to figure out Amanda and I have a few questions, hopefully not too stupid. My main goal is disaster recovery for a few servers, which to me means having the most recent complete set of backups off-site. I'm curious how that would work with Amanda dump cycles. If, for instance, I have a dump cycle of 7 days, would I be guaranteed that I have a full set of data if I have the 7 most recent tapes off-site? Assuming all my backups worked properly, of course. And since things don't always work properly, would it make sense to have 3 dump cycles in my tape cycle (I hope I'm getting the terminology correct) and keep the most recent 2 dump cycles off-site? Now lets say I wanted to be able to restore users' mistakenly deleted files as well. Would it be possible to keep a copy of the most recent dump cycle on-line using the file: driver without having the backup data collected twice? I.e. grab /usr, spool it to tape, and save it on disk. I hope I'm asking reasonable questions. I'm just trying to be really clear on how this stuff works before I buy all my equipment. Thanks for your time, - Bruce
Re: Dump too big for tape
Rebecca Pakish Crum wrote: FAILURE AND STRANGE DUMP SUMMARY: _www.iclear_ file://www.iclear / lev 0 FAILED [mesg read: Connection timed out] But from the previous mails we found out, ananda did send the estimate before timing out. So planner set all up to include 5.6 GByte from this host too. And that seems to be too much for 11976 Mbyte tape capacity. So planner degraded one of the backups, and planned an incremental one instead. Completely aside: I would have expected a message named hostname diskname lev 0 FAILED [blabla] Any idea why the hostname is _www.iclear_ file://www.iclear in the message amanda sends you? -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
RE: Dump too big for tape
Yes, but how big is it today? :) Check in last night's amdump.N file (should be amdump.1) to see how big the estimate was. got result for host isymmdb disk /var: 0 - 176050K, 1 - 11830K, -1 - -1K
RE: Dump too big for tape
But from the previous mails we found out, ananda did send the estimate before timing out. So planner set all up to include 5.6 GByte from this host too. And that seems to be too much for 11976 Mbyte tape capacity. So planner degraded one of the backups, and planned an incremental one instead. I'm not even addressing the timeout issue...that just will not resolve... I'm more concerned with why my 12GB tape will not backup ~5.8GB today, when it backed up ~5.9GB last night and every night since April, when it was backing up well over 10GB. This very tape, isymmdaily01, in its last rotation, backed up 5923MB. What I'm trying to find out is why 5.6 GB 'seems to be too much for the 11976 Mbyte tape capacity'. If it's a media error, I'll pull the tape...I'm asking if this could be indicative of something else. Completely aside: I would have expected a message named hostname diskname lev 0 FAILED [blabla] Any idea why the hostname is _www.iclear_ file://www.iclear in the message amanda sends you? I guess I always assumed that it was cutting the .com off of the www.iclear.com due to some reporting constraint. My disklist entry says: www.iclear.com / user-tar for that client. Sendbackup is looking for the right client: /-- www.iclear / lev 0 FAILED [mesg read: Connection timed out] sendbackup: start [www.iclear.com:/ level 0] And all of the information I sent you in those reports last week has the server going to the client and getting estimates...it's timing out after that, so it appears to know where it's going, it just can't complete it's mission (even though it chose to accept it), and it's self-destructing.
Re: Questions about AMANDA
On Fri, May 30, 2003 at 11:58:28AM -0300, Roberto Samarone Araujo (RSA) wrote: Hi, I have a backup policy and I would like to convert it to Amanda. The backup policy is: One full backup - One time per month (without following incremental backups) Fine. Separate amanda config with: dumpcycle 0 # full only runspercycle 1 # full only tapecycle 1 # full only strategy noinc # full only index yes# you don't have to, but it's nice record no# so you don't confuse the other config One full backup - One time per week and incrementals backups until the next week. For example, if I make a full backup on monday, the incrementals backups should be from tuesday until sunday. You don't do this. You do: dumpcycle 1 week # At least one full per week runspercycle 7 # Run 7X/week tapecycle 14 # At least two weeks, more is better index yes record yes So you don't know if the full will be on Monday or not, but you know you will get at least one full/week. You don't know that all the other runs will be incremental, though they probably will be unless amanda decides to move the full day to balance tape usage. Another questions: How can I restore a backup using Amanda ? Usually, amrecover, sometimes amrestore. If one of the clients that have been backuped is down (lose all data), How can I restore a backup on that client ? Read docs/RESTORE. :-) How can I change the label of a tape ? amlabel -f -- Jay Lessert [EMAIL PROTECTED] Accelerant Networks Inc. (voice)1.503.439.3461 Beaverton OR, USA(fax)1.503.466.9472
RE: Dump too big for tape
On Fri, 30 May 2003 at 10:38am, Rebecca Pakish Crum wrote But from the previous mails we found out, ananda did send the estimate before timing out. So planner set all up to include 5.6 GByte from this host too. And that seems to be too much for 11976 Mbyte tape capacity. So planner degraded one of the backups, and planned an incremental one instead. I'm not even addressing the timeout issue...that just will not resolve... I'm more concerned with why my 12GB tape will not backup ~5.8GB today, when it backed up ~5.9GB last night and every night since April, when it was backing up well over 10GB. This very tape, isymmdaily01, in its last rotation, backed up 5923MB. What I'm trying to find out is why 5.6 GB 'seems to be too much for the 11976 Mbyte tape capacity'. If it's a media error, I'll pull the tape...I'm asking if this could be indicative of something else. Ah, but what Pual is saying is that they're related. If you add up what did get backed up plus the disk that failed with the data timeout (but got an estimate), you're at capacity. So the full of that /var wouldn't fit, so amanda degraded it. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Re: Dump too big for tape
Rebecca Pakish Crum wrote: But from the previous mails we found out, ananda did send the estimate before timing out. So planner set all up to include 5.6 GByte from this host too. And that seems to be too much for 11976 Mbyte tape capacity. So planner degraded one of the backups, and planned an incremental one instead. I'm not even addressing the timeout issue...that just will not resolve... But before timing out, planner got already an estimate. Look in the amdump file. It took 5.6+ Gbyte in its estimate from www.iclear.com plus the 5.9 Gbyte from the others plus 150 Mbyte from /var. And that total amount is over your estimated tapecapacity. So planner decided to switch one filesystem to an incremental one before even starting the backups themselves. It does not know that www.iclear.com will time out. When the backup was started, www.iclear.com timed out, just as always, but planner had already given instructions to the driver. Driver does not come back on the schedule delivered by planner to notice that suddenly, because some other dump failed, it has enough room on the tape to do a full instead of an incremental. Look (or post) the amdump file from that run, and notice the schedule planner generated. -- Paul Bijnens, XplanationTel +32 16 397.511 Technologielaan 21 bus 2, B-3001 Leuven, BELGIUMFax +32 16 397.512 http://www.xplanation.com/ email: [EMAIL PROTECTED] *** * I think I've got the hang of it now: exit, ^D, ^C, ^\, ^Z, ^Q, F6, * * quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout, close, bye, /bye, * * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt, abort, hangup, * * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill -1 $$, shutdown, * * kill -9 1, Alt-F4, Ctrl-Alt-Del, AltGr-NumLock, Stop-A, ...* * ... Are you sure? ... YES ... Phew ... I'm out * ***
RE: Dump too big for tape
Ah, but what Pual is saying is that they're related. If you add up what did get backed up plus the disk that failed with the data timeout (but got an estimate), you're at capacity. So the full of that /var wouldn't fit, so amanda degraded it. Athe light is getting brighter, I'm walking towards it. This whole disk failing thing is causing more and more nonsense. I moved it back to it's old backup method for now, removing it from my amanda disklist, so I can get a solid level 0 of everything and sleep well. I just keep praying these boxes will go away soon. I don't have the resources or approval to test if that client is failing due to hardware issues. We dumped this company a year ago and I still can't shake them. It's my own little version of SARS.
RE: Dump too big for tape
But before timing out, planner got already an estimate. Look in the amdump file. It took 5.6+ Gbyte in its estimate from www.iclear.com plus the 5.9 Gbyte from the others plus 150 Mbyte from /var. And that total amount is over your estimated tapecapacity. So planner decided to switch one filesystem to an incremental one before even starting the backups themselves. It does not know that www.iclear.com will time out. When the backup was started, www.iclear.com timed out, just as always, but planner had already given instructions to the driver. Driver does not come back on the schedule delivered by planner to notice that suddenly, because some other dump failed, it has enough room on the tape to do a full instead of an incremental. Look (or post) the amdump file from that run, and notice the schedule planner generated. I get it now...it makes sense now that I see it on paper...but I wasn't thinking about it that way. (argh) Tunnel vision - sorry...
Excludes?
Does Amanda 2.4.1p1 support excludes? Can I use excludes with dump, or only gnutar? -- David Olbersen iGuard Engineer 11415 West Bernardo Court San Diego, CA 92127 1-858-676-2277 x2152
Re: Configuring RH7.2 Amanda out of the box - error accessing Ama nda hosts file.
On Fri, May 30, 2003 at 03:47:17PM +0100, Kevin Passey enlightened us: Ok my amandahosts file looks like this. dilmom.as400resource.com amanda *snip* Amanda Backup Client Hosts Check ERROR: dilmom: [access as amanda not allowed from [EMAIL PROTECTED] open of /home/amanda/.amandahosts failed ^ Notice that does not say dilmom.as400resource.com. You'll want an entry like dilmom amanda in your amandahosts file. Matt -- Matt Hyclak Department of Mathematics Ohio University (740) 593-1263 pgp0.pgp Description: PGP signature
Large drives
Hello Amanda users, I have an IRIX system (Origin 300, 4 500Mhz processors) with a few disks on it. One of these disks is relatively large, a RAID array configured as a single partition of 0.866 TBytes. The owner is looking into methods of backup and since we use amanda almost universally... but I need a sanity check. The system owner is thinking of purchasing a jukebox with 8 or 16 bays and an SDLT 320 drive, native 160 GByte capacity. I don't believe I've ever heard of anything that will backup such a large partition. Well, let me put it another way. I am not aware of any media (other than a duplicate RAID-array) that would backup up this large a partition. Also the partition is likely to grow as the array is not fully populated. I'm thinking Amanda using DLE's specifying TAR (some version of tar) backing up perhaps by user directory (which are at the top level of the partition). Tar backups would allow for full vs incremental ? And relatively easy restores ? I know I could probably xfsdump to multiple tapes but the restore process would be a real nightmare. We are already using amanda 2.4.4 with a jukebox on a Solaris system so we have some experience with configuration (that is a whole other thread...). We are open to suggestions, hardware, software or otherwise. Please tell me we aren't breaking new ground. 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
Re: Large drives
On Fri, 30 May 2003 at 1:47pm, Brian Cuttler wrote I have an IRIX system (Origin 300, 4 500Mhz processors) with a few disks on it. One of these disks is relatively large, a RAID array configured as a single partition of 0.866 TBytes. Pah. I've got a 2TB partition, a 1TB, and a .5TB, with another 2TB on the way. I win. ;) The system owner is thinking of purchasing a jukebox with 8 or 16 bays and an SDLT 320 drive, native 160 GByte capacity. I've got a 19 slot Overland with AIT3 (100GB native). I'm thinking Amanda using DLE's specifying TAR (some version of tar) backing up perhaps by user directory (which are at the top level of the partition). Until a user gets too big, at which point you need to start playing with exclude and include. Tar backups would allow for full vs incremental ? And relatively easy restores ? I know I could probably xfsdump to multiple tapes but the restore process would be a real nightmare. Yep -- works just fine here. If you use amrecover, you won't even be able to tell if you're using dump or tar. Using amrestore, just remember to do 'tar x' rather than xfsrestore. We are open to suggestions, hardware, software or otherwise. I use software compression so I can turn it on or off as befits each user's data. Some stuff compresses *very* well (one user has 360GB on disk, which compresses down to 60GB using gzip --fast), and other stuff is incompressible, even in software. I don't do too much Irix, so I don't know how you'd control the changer. I use mtx on Linux, with the chg-zd-mtx changer. My library (Overland Library Pro) is solid, and was a very good deal compared with other AIT changers. Good luck. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
client was working, now suddenly is getting self check host down? errors
Hi, This is confusing me a bit, I hope someone hear has an idea of what might be happening. I have been running an amanda server, backing itself up + one other amanda client (jayhawker), for about a week now. It works great every night when I have the amdump run. Yesterday I added a third amanda client, bcc1. bcc1 and jayhawker are both fresh RedHat 9 installs. I configured bcc1 exactly the same was as jayhawker, with the same entries in hosts.allow / hosts.deny / xinetd.conf / /home/amanda/.amandahosts etc. Both mybox (by name and by ip just in case) and localhost (by localhost / localhost.localdomain / 127.0.0.1) are allowed in hosts.allow for the user amanda... I know a lot of that is redundant but I wanted to be 100% sure I allowed the right things, since at least the .amandahosts file has been a bit picky. Also of course my amanda server mybox is set up ok in /etc/hosts. At first mybox could back up bcc1 just fine. I ran amcheck and there were 0 problems in 3 clients found. The first amdump worked yesterday afternoon. Then overnight amdump ran from cron and was unable to connect to bcc1. Actually 95% of the DLEs were backed up ok but /usr on bcc1 failed: 192.168.2. /usr lev 0 FAILED 20030530[could not connect to 192.168.2.200] This morning after reading that in the amanda report, I ran amcheck and it said selfcheck host down when trying bcc1 . Just to see if I could get to it, I tried ping bcc1 which started pinging the right IP immediately, no problems at all. I ran amcheck again without changing anything else and it found 0 problems. Then I ran amdump and somehow by the time it had finished, the problem came back, because *all* of the DLEs had FAILED messages saying could not connect. I had to leave the building for a bit, and when I came back, amcheck repeatedly says host down, even after I ping bcc1 (which still works great). I checked the /var/log/secure and /var/log/messages but I don't see anything strange at all, as far as I can tell. the amanda service is still running on the client and nothing has changed in the firewalls etc. I double checked all the things mentioned in the FAQ but everything seems to still be set up just fine. My disklist file on the server uses bcc1 for the client name, but just for kicks I tried changing it to the client's IP, and now it's saying that ip won't do a selfcheck either. Also my timeouts were set to at least 30 seconds in amanda.conf, amcheck was waiting a good long while before giving up, plus the boxes are all on a LAN so when amcheck works it usually only takes it less than a second to finish. Any ideas of why a client would work for a while then randomly not be able to do a selfchecK? The other amanda client is still working great... Thanks! ___ Jeremy Martin Network Technician http://www.gsi-kc.com mailto:[EMAIL PROTECTED]
Re: 2.4.4 build/make problem - resolved
John, Jon, Gene, Ivan, Just a quick Thank You. I've successfully run the new amanda build, 2.4.4 on my firewall using the resticted ports to backup the 2nd client. Client and server are both Solaris, drive is SDLT. The problems I encounted where 1) the error in the changer-src/Makefile (next time I'll use the snapshots rather than the current release version) 2) inability to find the run-time libraries I needed (it should have been a LD_LIBRARY_PATH issue, it wasn't, the libraries where in /usr/local/lib and I needed to copy them to the server and client from the build system). 3) I had a syntax error when overwriding the CC choices. We lack GNU CC on many of our systems and wanted to use the Solaris CC compiler. # setenv CC cc # setenv CFLAGS -fast -xarch=v8plusa 4) lack of /sh/bash on client system, # make wouldn't run without having some shell it could use. Fix I used was # ln -s /bin/sh /bin/bash Not counting whatever my firewall expert did. thanks all, 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
RE: client was working, now suddenly is getting self check host down? errors
I have a random problem like this as well running RH Linux. The client occasionally fails amcheck in the afternoon. (Backups run at nite.) When I look at portland, the client, I find the selfcheck task stuck and I am unable to kill it, even with kill -9. See if you have the same problem. On the client, try ps -ef | grep amand or grep with whatever your amanda user account is. If you see selfcheck running, you'll be unable to get amcheck on the server to finish until it's gone. Just something to check. Ron Bauman Hatteras Networks, Inc. -Original Message- From: Martin, Jeremy [mailto:[EMAIL PROTECTED] Sent: Friday, May 30, 2003 2:14 PM To: [EMAIL PROTECTED] Subject: client was working, now suddenly is getting self check host down? errors Hi, This is confusing me a bit, I hope someone hear has an idea of what might be happening. I have been running an amanda server, backing itself up + one other amanda client (jayhawker), for about a week now. It works great every night when I have the amdump run. Yesterday I added a third amanda client, bcc1. bcc1 and jayhawker are both fresh RedHat 9 installs. I configured bcc1 exactly the same was as jayhawker, with the same entries in hosts.allow / hosts.deny / xinetd.conf / /home/amanda/.amandahosts etc. Both mybox (by name and by ip just in case) and localhost (by localhost / localhost.localdomain / 127.0.0.1) are allowed in hosts.allow for the user amanda... I know a lot of that is redundant but I wanted to be 100% sure I allowed the right things, since at least the .amandahosts file has been a bit picky. Also of course my amanda server mybox is set up ok in /etc/hosts. At first mybox could back up bcc1 just fine. I ran amcheck and there were 0 problems in 3 clients found. The first amdump worked yesterday afternoon. Then overnight amdump ran from cron and was unable to connect to bcc1. Actually 95% of the DLEs were backed up ok but /usr on bcc1 failed: 192.168.2. /usr lev 0 FAILED 20030530[could not connect to 192.168.2.200] This morning after reading that in the amanda report, I ran amcheck and it said selfcheck host down when trying bcc1 . Just to see if I could get to it, I tried ping bcc1 which started pinging the right IP immediately, no problems at all. I ran amcheck again without changing anything else and it found 0 problems. Then I ran amdump and somehow by the time it had finished, the problem came back, because *all* of the DLEs had FAILED messages saying could not connect. I had to leave the building for a bit, and when I came back, amcheck repeatedly says host down, even after I ping bcc1 (which still works great). I checked the /var/log/secure and /var/log/messages but I don't see anything strange at all, as far as I can tell. the amanda service is still running on the client and nothing has changed in the firewalls etc. I double checked all the things mentioned in the FAQ but everything seems to still be set up just fine. My disklist file on the server uses bcc1 for the client name, but just for kicks I tried changing it to the client's IP, and now it's saying that ip won't do a selfcheck either. Also my timeouts were set to at least 30 seconds in amanda.conf, amcheck was waiting a good long while before giving up, plus the boxes are all on a LAN so when amcheck works it usually only takes it less than a second to finish. Any ideas of why a client would work for a while then randomly not be able to do a selfchecK? The other amanda client is still working great... Thanks! ___ Jeremy Martin Network Technician http://www.gsi-kc.com mailto:[EMAIL PROTECTED]
Problems to run 'amrecover' - Again
Hi, After use the suggestion, it worked but, there are still some problems: I used the line: amrecover Daily1 -s localhost But, some erros occured: 501 No index record for host: server1.mydomain. Invalid? Trying Server1.mydomain ... 501 No index record for host: Server1.mydomain. Invalid? After that, the prompt appeared, I did 'ls' and the 'amrecover' returned me 'Must select a disk before listing file'. After sethost (sethost client1) and setdisk (setdisk hdb1 /usr), I could see the directory tree from the backup. I add a file and tried to extract it but, some errors appeared: Load tape XYZ01 now Continue? [Y/n] EOF, check amdxtaped.debug file on localhost. amrecover: short block 0 bytes UNKNOWN file amrecover: Can't read file header extract_list - child returned non-zero status: 1 Continue?[Y/n] I Can't recovery the file :///. What's hapenned ? Thanks, Roberto Samarone Araúo On Fri, 30 May 2003 at 2:41pm, Roberto Samarone Araujo (RSA) wrote I've done a backup perfectly but, when I tried to run 'amrecover' from the server or from the clients, I received the messages: Contacting server on localhost ... 200 server1 AMANDA index server (2.4.2p2) ready. 500 Access not allowed: [access as backup not allowed from [EMAIL PROTECTED] amandahostsauth failed. I put on the /root/.amandahosts - localhost root - on the server. And - server1.mydomain backup - on the clients. I started amrecover on the server using: amrecover Daily1. On the clients I started using: amrecover Daily1 -t server1.mydomain, but the same error occured. What's the problem ? You need 'localhost root' in the .amandahosts in ~backup. -- Joshua Baker-LePain Department of Biomedical Engineering Duke University
Lick to me / Sevis Benimle
Title: Super PornolaR MutHis ResimLer ve VideoLar Lick To me Inanilmaz Porno Filmler
KALiTE HiCBiR ZAMAN TESADÜF DEGiLDiR..!
Title: Untitled TR.Rehber 11 - 199$ 6.850.000 Trk E-mail adresi ( llere, ya gruplarna, cinsiyetlere ve meslek gruplarna gre byk bir titizlik ile kategori edilip hazirlandi.) World.Rehber 4.0-199$ Dnya Genelinde 350 Milyon e-mail adresi lkelere ve ktalara gre byk bir titizlik ile kategori edilip hazirlandi. Firma.Rehberi 2 - 55$ Trkiye genelinde 500bin firmanin adi, adresi, faliyet alani, telefon, fax, e-mail,web adresi gibi bilgilerinin bulunduu muhteem bir kaynaktir. TR.Rehber 11 ve World.Rehber 4.0 birlikte alndnda sadece 299$ Dnya'da ve paralel olarak Trkiye'de internet her geen gn gibi bymekte. Bu yeni oluum iinde yer almak ve faaliyette bulunmak kanlmaz. u anda, Trkiye'de 7 milyon internet kullancs olduu tahmin ediliyor ve bu rakkam her geen gn hzla artyor. nternet'te firmanzn WEB sitesini oluturma zorunluluu her geen gn artyor. Bu kadar kolay ulam imkanlar olan bir teknikten firmanz niin yararlanmasn. Firmanzn WEB sitesini amanz yeterli mi? Sitenizin aldn nasl ve kime duyuracaksnz ? Sitenize nasl ok ziyareti ekebileceksiniz ? Internet'te, ayn ii yapan veya sizin ulamak istediiniz firmalar nasl bulacaksnz? CD'lerimiz bunlar rahat yapabilmenizi salayacak. ! .:: deme ve Ulam Seeneklerimiz::. Seenek 1 - deme banka havalesi, ulam kargo ile salanacakdr. (24 saat ierisinde adresinize teslim edilir.) Seenek 2 - demeli APS. deme CD'lerin teslimatn gerekletiren kuryeye yaplacaktr. (24-72 saat arasnda adresinize teslim edilir.) Seenek 3 - Banka demesi ile direk download imkan. Rehberlere annda ulamak isteyen mterilerimiz iin hzl bir zmdr. LETM BLGLER 0535 482 97 19 GKHAN ATASOY !! Tm rnlerimiz 687.245 adet arama motoruna kayt hediyelidir !! Herseye ragmen bizden e-mail almak istemiyor ve satisa sundugumuz listelerden cikmak istiyorsaniz [EMAIL PROTECTED] adresine bos bir mail gondermeniz yeterli olacakdir.
Failed Backups
I've been running amanda for several months with
backups to disk
(amanda version 2.4.3). Recently I've had backups
failing and can't
figure out what the problem may be.
Some details:
- Clients and backup server are Linux (RedHat 8)
- backup disk has plenty of free space (80 GB drive
with only 35% in
use)
Below is an example report from one of the failed
dumps. Nothing has
recently changed that should affect backups. I
haven't found
anything to help point me in the right direction and
would appreciate
any points.
Thanks,
Chris
-- AMANDA MAIL REPORT --
These dumps were to tape standard14.
The next 7 tapes Amanda expects to used are:
standard16, standard17,
standard18,
+standard19, standard20, standard21, standard22.
FAILURE AND STRANGE DUMP SUMMARY:
gilgamesh. / lev 1 FAILED [unknown response: 0;]
gilgamesh. / lev 1 FAILED [dump to tape failed]
goblin.the /var lev 1 FAILED [can't dump no-hold
disk in degraded
mode]
gilgamesh. /home lev 1 FAILED [can't dump no-hold
disk in degraded
mode]
gilgamesh. /usr lev 1 FAILED [can't dump no-hold
disk in degraded
mode]
hades.theo /var lev 1 FAILED [can't dump no-hold
disk in degraded
mode]
psyche.the /usr lev 1 FAILED [can't dump no-hold
disk in degraded
mode]
psyche.the /var lev 3 FAILED [can't dump no-hold
disk in degraded
mode]
hades.theo / lev 1 FAILED [can't dump no-hold disk
in degraded mode]
goblin.the /usr lev 2 FAILED [can't dump no-hold
disk in degraded
mode]
STATISTICS:
Total Full Daily
Estimate Time (hrs:min)0:02
Run Time (hrs:min) 0:02
Dump Time (hrs:min)0:00 0:00 0:00
Output Size (meg) 3.00.03.0
Original Size (meg) 9.40.09.4
Avg Compressed Size (%)31.5--31.5
(level:#disks
...)
Filesystems Dumped9 0 9
(1:9)
Avg Dump Rate (k/s) 298.7-- 298.7
Tape Time (hrs:min)0:00 0:00 0:00
Tape Size (meg) 3.50.03.5
Tape Used (%) 0.30.00.3
(level:#disks
...)
Filesystems Taped10 0 10
(1:10)
Avg Tp Write Rate (k/s) 300.0-- 300.0
^L
FAILED AND STRANGE DUMP DETAILS:
/-- gilgamesh. / lev 1 FAILED [unknown response: 0;]
\
^L
NOTES:
planner: Incremental of psyche.theory14.net:/var
bumped to level 3.
planner: Full dump of psyche.theory14.net:/var
promoted from 2 days
ahead.
taper: tape standard14 kb 3552 fm 10 [OK]
DUMP SUMMARY:
DUMPER STATS
TAPER
STATS
HOSTNAME DISKL ORIG-KB OUT-KB COMP% MMM:SS
KB/s MMM:SS
KB/s
--
-
gilgamesh.th / 1 FAILED
---
gilgamesh.th /boot 1 10 64 640.0 0:00
0.0 0:00
218.8
gilgamesh.th /home 1 FAILED
---
gilgamesh.th /usr1 FAILED
---
gilgamesh.th /var12370448 18.9 0:02
180.5 0:03
131.1
goblin.theor / 11320160 12.1 0:01
76.9 0:01
121.3
goblin.theor /boot 1 10 64 640.0 0:00
0.0
0:001008.4
goblin.theor /home 14710 2496 53.0 0:03
963.0 0:03
974.2
goblin.theor /usr2 FAILED
---
goblin.theor /var1 FAILED
---
hades.theory / 1 FAILED
---
hades.theory /boot 1 10 64 640.0 0:00
0.0 0:00
171.2
hades.theory /var1 FAILED
---
psyche.theor / 11080128 11.9 0:03
26.7 0:03
37.6
psyche.theor /boot 1 10 64 640.0 0:00
0.0 0:00
603.0
psyche.theor /home 1 90 64 71.1 0:00
15.5 0:00
243.9
psyche.theor /usr1 FAILED
---
psyche.theor /var3 FAILED
---
(brought to you by Amanda version 2.4.3)
Re: Failed Backups
On Fri, May 30, 2003 at 11:32:54PM -0400, Chris Gordon wrote: I've been running amanda for several months with backups to disk (amanda version 2.4.3). Recently I've had backups failing and can't figure out what the problem may be. Some details: - Clients and backup server are Linux (RedHat 8) - backup disk has plenty of free space (80 GB drive with only 35% in use) Below is an example report from one of the failed dumps. Nothing has recently changed that should affect backups. I haven't found anything to help point me in the right direction and would appreciate any points. -- AMANDA MAIL REPORT -- These dumps were to tape standard14. The next 7 tapes Amanda expects to used are: standard16, standard17, standard18, +standard19, standard20, standard21, standard22. Interesting that standard15 is not mentioned. It may have bearing on my guesses. FAILURE AND STRANGE DUMP SUMMARY: gilgamesh. / lev 1 FAILED [unknown response: 0;] gilgamesh. / lev 1 FAILED [dump to tape failed] goblin.the /var lev 1 FAILED [can't dump no-hold disk in degraded mode] A scan of the source shows that message only coming in one place. At that time the backup has entered degraded mode. Further, the message is only printed if the backup is not using a holding disk. So first I presume you are not using a holding disk. Second, looking at the source (quickly, so I might have missed something) degraded mode is only entered after a dump starts if a tape error occurs. So I'm guessing you have a size limit on your disk tapes and standard14 reached that limit. When the changer script went to switch to standard15, an error occured. That put you into degraded mode, and without a holding disk, backups of all subsequent DLE's failed. A place to start looking at least. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
RE: Configuring RH7.2 Amanda out of the box - error accessing Ama nda hosts file.
I thought that once I sent the mail so I added both it now looks like dilmom.as400resource.com amanda dilmom amanda Still no Joy !! Thanks for your reply anyway. Regards Kevin -Original Message- From: Matt Hyclak [mailto:[EMAIL PROTECTED] Sent: 30 May 2003 17:09 To: Amanda (E-mail) Subject: Re: Configuring RH7.2 Amanda out of the box - error accessing Ama nda hosts file. On Fri, May 30, 2003 at 03:47:17PM +0100, Kevin Passey enlightened us: Ok my amandahosts file looks like this. dilmom.as400resource.com amanda *snip* Amanda Backup Client Hosts Check ERROR: dilmom: [access as amanda not allowed from [EMAIL PROTECTED] open of /home/amanda/.amandahosts failed ^ Notice that does not say dilmom.as400resource.com. You'll want an entry like dilmom amanda in your amandahosts file. Matt -- Matt Hyclak Department of Mathematics Ohio University (740) 593-1263
Re: Configuring RH7.2 Amanda out of the box - error accessing Ama nda hosts file.
On Saturday 31 May 2003 04:12, Kevin Passey wrote: I thought that once I sent the mail so I added both it now looks like dilmom.as400resource.com amanda dilmom amanda Still no Joy !! Are the perms 0600, and its owned by amanda? -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
Re: Configuring RH7.2 Amanda out of the box - error accessing Ama nda hosts file.
Hi, I thought that once I sent the mail so I added both it now looks like dilmom.as400resource.com amanda dilmom amanda Still no Joy !! Thanks for your reply anyway. Regards Kevin -Original Message- *snip* Amanda Backup Client Hosts Check ERROR: dilmom: [access as amanda not allowed from [EMAIL PROTECTED] open of /home/amanda/.amandahosts failed ^ Check the owner and permisions of '/home/amanda/.amandahosts' - should be amanda.disk and 660. WJ
Re: Configuring RH7.2 Amanda out of the box - error accessing Ama nda hosts file.
On Saturday 31 May 2003 04:40, Wojciech Jedliczka wrote: Hi, I thought that once I sent the mail so I added both it now looks like dilmom.as400resource.com amanda dilmom amanda Still no Joy !! Thanks for your reply anyway. Regards Kevin -Original Message- *snip* Amanda Backup Client Hosts Check ERROR: dilmom: [access as amanda not allowed from [EMAIL PROTECTED] open of /home/amanda/.amandahosts failed ^ Check the owner and permisions of '/home/amanda/.amandahosts' - should be amanda.disk and 660. WJ Nope, 0600. RTM please. -- Cheers, Gene AMD [EMAIL PROTECTED] 320M [EMAIL PROTECTED] 512M 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attornies please note, additions to this message by Gene Heskett are: Copyright 2003 by Maurice Eugene Heskett, all rights reserved.
