INFO planner sa03 /terrasky/tslibrary_qr 20041206 0 [dumps too big, full dump delayed
Hi I am getting above error message during my Monthly backup. My holding disk is 55 GB - big eneough to accomodate the dump. A level 1 backup is done instead of level 1. Regds M
Re: INFO planner sa03 /terrasky/tslibrary_qr 20041206 0 [dumps too big, full dump delayed
Madhvi Gokool wrote: Hi I am getting above error message during my Monthly backup. My holding disk is 55 GB - big eneough to accomodate the dump. The size of the tape is what matters. Specify "runtapes 2" or "maxdumpsize 55g" (or whatever appropriate value) to let the overflow accumulate on holdingdisk. Also, you need to change the default "reserve 100", to some lower value (even zero) to allow level 0 dumps in degraded mode (= to holdingdisk when tape is full). -- 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 * ***
Exabyte Packetloader and AMANDA ?
Exabyte sells a new and relatively inexpensive auto loader device. Called the "VXA-2 PacketLoader 1x10 1U Autoloader". I have no experience with autoloaders and AMANDA as I have been using AMANDA now for years with manually-loaded tapes. I do know from reading the AMANDA docks that some autoloaders are supported. Does anyone have any experience with this new device and AMANDA ? Will it work OK ? We are getting ready to place the PO.
amanda tape use strategy
Apologies if this has come up before. Couldn't find anything relevant. I'm talking about level 0 dumps (not incrementals). Using ait-3 tapes, GNUTAR (not linux "dump"), a tape library, 104GB holding disk and setting runtapes greater than 1 (I need to dump several tapes-worth of data). NO software or hardware compression. amanda-2.4.4p1-0.3E Amanda works great for me. These are efficiency questions - not critical problems. a) When backing-up multiple disks from a single client, amanda seems to dump and then write them to tape in order of increasing size. This can be inefficient. e.g. if you have filesystems that are 40GB, 40GB, 55GB and 55GB and write to 100GB tapes, amanda will use 3 tapes when the backup would fit on 2 tapes. b) amanda doesn't seem to know that it will run out of space on a tape. E.g. if I have two 65GB filesystems to dump to a 100GB tape, amanda will write the first and then start writing the second one and keep going until it hits the end of tape. It then puts in the next tape and rewrites which is great but a lot of time was wasted writing a file which wasn't going to fit on the first tape. I'm running amtapetype for myself right now but have been using a tape entry from the amanda faq that sets "length 108890 mbytes" (but there are two different ones for the same drive and tape; Sony SDX-700C and AIT-3). So, my questions are 1) is what I've described above true (seems to be for me) and 2) is there anything I can do (easily) to change this behaviour? Thanks, Chris
Re: amanda tape use strategy
Chris Loken wrote: Apologies if this has come up before. Couldn't find anything relevant. I'm talking about level 0 dumps (not incrementals). Using ait-3 tapes, GNUTAR (not linux "dump"), a tape library, 104GB holding disk and setting runtapes greater than 1 (I need to dump several tapes-worth of data). NO software or hardware compression. amanda-2.4.4p1-0.3E Amanda works great for me. These are efficiency questions - not critical problems. a) When backing-up multiple disks from a single client, amanda seems to dump and then write them to tape in order of increasing size. This can be inefficient. e.g. if you have filesystems that are 40GB, 40GB, 55GB and 55GB and write to 100GB tapes, amanda will use 3 tapes when the backup would fit on 2 tapes. b) amanda doesn't seem to know that it will run out of space on a tape. E.g. if I have two 65GB filesystems to dump to a 100GB tape, amanda will write the first and then start writing the second one and keep going until it hits the end of tape. It then puts in the next tape and rewrites which is great but a lot of time was wasted writing a file which wasn't going to fit on the first tape. I'm running amtapetype for myself right now but have been using a tape entry from the amanda faq that sets "length 108890 mbytes" (but there are two different ones for the same drive and tape; Sony SDX-700C and AIT-3). So, my questions are 1) is what I've described above true (seems to be for me) and 2) is there anything I can do (easily) to change this behaviour? Use the parameter "taperalgo largestfit". But beware of some interaction with dumporder, inparallel and the taperalgo: http://marc.theaimsgroup.com/?l=amanda-users&m=106277015010167&w=2 About nr2: you can't change it, but it hurts less when the largestfit algoritm is applied. -- 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 * ***
configuring Amanda with Samba
hi, I am trying to configure Amanda on a Solaris 9 server - I need to backup both Unix computers and Windows computers. I was able to backup the Unix server, BUT I could not backup the Windows machine. I installed SAMBA 3.0.9, HOWEVER when I run amcheck I received the following error message: ...session setup failed: NT_STATUS_LOGON_FAILURE: returned 1 Any thoughts commends? thx, gil
Re: Estimate timeout error
Paul Bijnens wrote: But the reply packet never got acknowledged by the server. Somehow it got lost or corrupted. Default route for reverse path not correct? Wrong subnetmask? Try do get a network trace at the client and server, and inbetween (don't know how to accomplish that on a PIX firewall): Solaris: snoop -x42 host x.x.x.x proto udp port 10080 using open source (linux and others): tcpdump -X host x.x.x.x and udp and port 10080 Or other programs that have the same capabilities (ethereal etc). Before guessing how to fix it, we must know where the problem is. Is the packet lost? or is it broken? Quick recap: Server grolsch tries to back up client dominion. It works for the partitions of /, /usr and /var. As soon as I tell grolsh to back up dominions /u00 partition (a 45G partition, but presently only 177M full w/approx 2000 files) it will fail. I have since removed /u00 from backups to at least keep things working in the meantime but I would like that data backed up :-) I have moved the amanda server to public IP space. It is still behind a PIX firewall, I just got rid of the private IP to public IP mappings. This didnt fix it :-) Not that I thought it would, I just got annoyed at some of the routing. I ran tcpdump on client and server, the dumps are on the following page, lined up as best I could to show the flow. It seems when doing the partition that makes it fail, a bunch of packets do not get from the client to the server. Since I am no expert in TCPdump or interpreting its results, I hope this helps figure out the problem. tcpdump results on http://www.hackermonkey.com/amanda-error.html -Nick
Re: configuring Amanda with Samba
Gil Naveh wrote: I am trying to configure Amanda on a Solaris 9 server - I need to backup both Unix computers and Windows computers. I was able to backup the Unix server, BUT I could not backup the Windows machine. I installed SAMBA 3.0.9, HOWEVER when I run amcheck I received the following error message: ...session setup failed: NT_STATUS_LOGON_FAILURE: returned 1 Any thoughts commends? /etc/amandapass? Username - password - domain correct? Can you log on with smbclient? -- 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: amanda tape use strategy
On Tue, Dec 07, 2004 at 12:35:29PM -0500, Chris Loken wrote: > > Apologies if this has come up before. Couldn't find anything relevant. > I'm talking about level 0 dumps (not incrementals). Using ait-3 tapes, > GNUTAR (not linux "dump"), a tape library, 104GB holding disk and > setting runtapes greater than 1 (I need to dump several tapes-worth of > data). NO software or hardware compression. amanda-2.4.4p1-0.3E > > Amanda works great for me. These are efficiency questions - not critical > problems. > > a) When backing-up multiple disks from a single client, amanda seems to > dump and then write them to tape in order of increasing size. This can > be inefficient. e.g. if you have filesystems that are 40GB, 40GB, 55GB > and 55GB and write to 100GB tapes, amanda will use 3 tapes when the > backup would fit on 2 tapes. > > b) amanda doesn't seem to know that it will run out of space on a tape. > E.g. if I have two 65GB filesystems to dump to a 100GB tape, amanda will > write the first and then start writing the second one and keep going > until it hits the end of tape. It then puts in the next tape and > rewrites which is great but a lot of time was wasted writing a file > which wasn't going to fit on the first tape. I'm running amtapetype for > myself right now but have been using a tape entry from the amanda faq > that sets "length 108890 mbytes" (but there are two different ones for > the same drive and tape; Sony SDX-700C and AIT-3). > > So, my questions are 1) is what I've described above true (seems to be > for me) and 2) is there anything I can do (easily) to change this behaviour? > Checking the setting of your "taperalgo" parameter is in order. A suitable setting for what you want might be "largest dump in the holding disk that should fit the remaining tape space". Probably named something like "largestfit", but DHMTI. :) Note, this does not affect the order of dumping. Other parameters do that. It only affects which, of the already completed dumps, amanda will choose to tape next. It will not wait around for one that fits. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: amanda tape use strategy
--On Tuesday, December 07, 2004 14:13:43 -0500 Jon LaBadie <[EMAIL PROTECTED]> wrote: > > Note, this does not affect the order of dumping. Other parameters > do that. It only affects which, of the already completed dumps, > amanda will choose to tape next. It will not wait around for > one that fits. How difficult would it be to implement a 'best fit' strategy? One that would collect all the dumps to holdingdisk and then fit them onto the tapes, the functional equivalent of running amdump without a tape and then running amflush. I realize that it would require holdingdisk size to be greater than the total size of the backup, but it would allow for the most efficient use of tape. Also, does Amanda always try to write another dump image to tape until it hits EOT, even if the size of the dump is greater than the amount of remaining tape? Frank -- Frank Smith [EMAIL PROTECTED] Sr. Systems Administrator Voice: 512-374-4673 Hoover's Online Fax: 512-374-4501
Re: amanda tape use strategy
On Tue, Dec 07, 2004 at 03:36:56PM -0600, Frank Smith wrote: > --On Tuesday, December 07, 2004 14:13:43 -0500 Jon LaBadie <[EMAIL > PROTECTED]> wrote: > > > > Note, this does not affect the order of dumping. Other parameters > > do that. It only affects which, of the already completed dumps, > > amanda will choose to tape next. It will not wait around for > > one that fits. > > How difficult would it be to implement a 'best fit' strategy? > One that would collect all the dumps to holdingdisk and then > fit them onto the tapes, the functional equivalent of running > amdump without a tape and then running amflush. I realize > that it would require holdingdisk size to be greater than the > total size of the backup, but it would allow for the most > efficient use of tape. I seem to recall that amanda had some way to say "only dump this DLE at such and such a time". If dumper can have delays, maybe taper can too. Then maybe you could say don't start taping until ... That way a number of DLEs would have been completed and the largest fit taperalgo would have several to choose from. -- Jon H. LaBadie [EMAIL PROTECTED] JG Computing 4455 Province Line Road(609) 252-0159 Princeton, NJ 08540-4322 (609) 683-7220 (fax)
Re: Estimate timeout error
Nick Danger wrote: Paul Bijnens wrote: But the reply packet never got acknowledged by the server. Somehow it got lost or corrupted. Default route for reverse path not correct? Wrong subnetmask? Try do get a network trace at the client and server, and inbetween (don't know how to accomplish that on a PIX firewall): Solaris: snoop -x42 host x.x.x.x proto udp port 10080 using open source (linux and others): tcpdump -X host x.x.x.x and udp and port 10080 Or other programs that have the same capabilities (ethereal etc). Before guessing how to fix it, we must know where the problem is. Is the packet lost? or is it broken? Quick recap: Server grolsch tries to back up client dominion. It works for the partitions of /, /usr and /var. As soon as I tell grolsh to back up dominions /u00 partition (a 45G partition, but presently only 177M full w/approx 2000 files) it will fail. I have since removed /u00 from backups to at least keep things working in the meantime but I would like that data backed up :-) I have moved the amanda server to public IP space. It is still behind a PIX firewall, I just got rid of the private IP to public IP mappings. This didnt fix it :-) Not that I thought it would, I just got annoyed at some of the routing. I ran tcpdump on client and server, the dumps are on the following page, lined up as best I could to show the flow. It seems when doing the partition that makes it fail, a bunch of packets do not get from the client to the server. Since I am no expert in TCPdump or interpreting its results, I hope this helps figure out the problem. tcpdump results on http://www.hackermonkey.com/amanda-error.html very good to find that already. You forgot "-s 1500", so that all packets are cut off at 256 bytes... But I believe I have enough information to conclude that the PIX firewall times out too soon for the udp reply. Usually a dialog goes like: server sends some REQuest to client client answers with ACKnowledge to confirm receipt of request client sends REPly to the server server answers with ACKnowledge to confirm receipt of reply The details of the REQ or REP packet are cut off by omitting the -s option to tcdump, but you can see the strings REQ/ACK/REP in each packet. The first exchange is a NOOP request, to which the client answers with his list of capabilities. This takes only a few milliseconds. The second exchange is the request to estimate the list of DLE's. The client sends the REPly when all DLE's are estimated. This takes more time: 09:51:45.208525 til 09:54:25.687229 or about 2 minutes 40 seconds. However the packet is not recieved at the server. The client just sends the packet at an interval of 10 seconds, but never receives the ACK, and gives up. For a TCP connection a firewall has a notion of a connection and keeps a TCP connection open until one of side stops the connections. A UDP connection is stateless, and a firewall has no indication that the third step (REPly) is related to the REQuest/ACK some minutes before. A firewall usually uses a timer to decide when to stop transmitting packets. It seems that the timer for UDP packets in the PIX firewall is less than 2 minutes 40 seconds. I have no experience with a PIX firewall. Any possibility to increase the UDP timeout? Another possibility is to allow UDP packets to port 10080 from client to server without timeouts. (That's what stateless firewalls have to do anyway.) -- 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: amanda tape use strategy
Frank Smith wrote: How difficult would it be to implement a 'best fit' strategy? The number of possibilities is extremely large, and because the tapecapacity is only an approximation, not worth the cost. My AIT-1 tapes hit end of tape between 33 and 34 Gbyte. And rarely there is one which suddenly hits EOT at 31.8 too. One that would collect all the dumps to holdingdisk and then fit them onto the tapes, the functional equivalent of running amdump without a tape and then running amflush. I realize that it would require holdingdisk size to be greater than the total size of the backup, but it would allow for the most efficient use of tape. The "largestfit" performs very well on my setup: 3 of my 4 AIT-1 tapes are filled to nearly 100% on my archive run. Last week one tape had even 100.6%. Also, does Amanda always try to write another dump image to tape until it hits EOT, even if the size of the dump is greater than the amount of remaining tape? For people that use hardware compression, amanda does not know what remains on the tape. And even in my config, I had to specify the tapelength a little pessimistic, because not all tapes have equal capacity. The capacity of a tape is also affected by the status of the write head and tape quality: the drive reads with one head what it just wrote, and, if it concludes that the written part is not good enough, the tapedrive writes the same block again, up to a number of times (much faster than stopping, rewinding and rewriting); this uses tapecapacity too. That's why my tapelengths are less than the real length. An improvement could be that, when nothing fits, amanda chooses the smallest, which has the best chance of fitting on the uncertain remaining inches (which in my case can be 1 Gbyte!). -- 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: amanda tape use strategy
Paul & Jon - thanks for the tip about using taperalgo. I wasn't aware of this parameter. Will try it out but I'm not sure how well it will work for me - I'm only dumping from one client, there are a lot of filesystems that are large compared to the tape size and there isn't enough space to keep all the dumps on the holding disk (HD is size of one tape, total space to be dumped is several tapes worth). I've been using maxdumps=1 so turning that up might help (but I'm afraid of the load it will place on the client) as well as playing with dumporder. Increasing the HD size might also help :-) I was kind of hoping that the dumper would be smart enough to dump in an optimal order (the 40GB space, then one of the 55's, then the other 40GB and then the remaining 55GB in my example from below). Presumably amanda has all the relevant info since it does a planning stage first. But while this may be simple in the case of one client and no compression it could be tricky with multiple clients, differing bandwidths, compression etc. According to Paul, I can't avoid the fact that amanda will attempt to write a file to tape even when it knows there isn't enough space (if compression is off this should be very clear). A closer look at the man page confirms this. Oh well. Thanks for the responses! Chris Paul Bijnens wrote: Chris Loken wrote: Apologies if this has come up before. Couldn't find anything relevant. I'm talking about level 0 dumps (not incrementals). Using ait-3 tapes, GNUTAR (not linux "dump"), a tape library, 104GB holding disk and setting runtapes greater than 1 (I need to dump several tapes-worth of data). NO software or hardware compression. amanda-2.4.4p1-0.3E Amanda works great for me. These are efficiency questions - not critical problems. a) When backing-up multiple disks from a single client, amanda seems to dump and then write them to tape in order of increasing size. This can be inefficient. e.g. if you have filesystems that are 40GB, 40GB, 55GB and 55GB and write to 100GB tapes, amanda will use 3 tapes when the backup would fit on 2 tapes. b) amanda doesn't seem to know that it will run out of space on a tape. E.g. if I have two 65GB filesystems to dump to a 100GB tape, amanda will write the first and then start writing the second one and keep going until it hits the end of tape. It then puts in the next tape and rewrites which is great but a lot of time was wasted writing a file which wasn't going to fit on the first tape. I'm running amtapetype for myself right now but have been using a tape entry from the amanda faq that sets "length 108890 mbytes" (but there are two different ones for the same drive and tape; Sony SDX-700C and AIT-3). So, my questions are 1) is what I've described above true (seems to be for me) and 2) is there anything I can do (easily) to change this behaviour? Use the parameter "taperalgo largestfit". But beware of some interaction with dumporder, inparallel and the taperalgo: http://marc.theaimsgroup.com/?l=amanda-users&m=106277015010167&w=2 About nr2: you can't change it, but it hurts less when the largestfit algoritm is applied.
Question using amflush
Hello Everyone, I've recently deployed amanda. The client forgot tapes on several occasions and I've got 4 backups in my holding area. I initiated the amflush command and followed the instructions. The job kicked off in the background and I've been using: ps -ef |grep amanda to see if the process is still running, which it is. When I do a top command it's using lots of CPU time. It's been runninng for several hours now and my logs haven't been populating since it started. Here's the last few entries: START amflush date 20041207 START driver date 20041207 START taper datestamp 20041207 label Normal18 tape 0 I'm a bit confused because I now see a folder 20041207 in my /var/holding. It's empty, which is good if it's working properly. Why isn't anything being populated too(amflush and log file)? Is there any way to tell if it's running properly? thanks, James
Re: Question using amflush
James Marcinek wrote: I've recently deployed amanda. The client forgot tapes on several occasions and I've got 4 backups in my holding area. I initiated the amflush command and followed the instructions. The job kicked off in the background and I've been using: ps -ef |grep amanda to see if the process is still running, which it is. When I do a top command it's using lots of CPU time. Which process is taking CPU time? planner? driver? taper? It's been runninng for several hours now and my logs haven't been populating since it started. Here's the last few entries: START amflush date 20041207 START driver date 20041207 START taper datestamp 20041207 label Normal18 tape 0 I'm a bit confused because I now see a folder 20041207 in my /var/holding. It's empty, which is good if it's working properly. For flush, that's normal. Why isn't anything being populated too(amflush and log file)? Is there any way to tell if it's running properly? On linux:strace -p The-PID on Solaris: truss -p The-PID "lsof -o the-PID" tells you which files are opened, and sometimes can give a hint what it is doing (e.g. which file it is reading/writing). (hit Ctrl-C to stop it). PS. have also a look at "autoflush on": when forgetting a tape once, the next time, amanda flushes automatically. -- 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: Question using amflush
I initially just straced the parent process (22802 amflush normal) which didn't output anything: Here's the ps -ef again with the trace commands for each PID involved: ps -ef |grep amanda amanda 22803 22802 0 14:01 ?00:00:00 driver normal nodump amanda 22804 22803 0 14:01 ?00:00:00 taper normal amanda 22805 22804 0 14:01 ?00:00:00 taper normal root 27581 27541 0 17:29 pts/000:00:00 su - amanda amanda 27582 27581 0 17:29 pts/000:00:00 -bash amanda 22802 1 98 14:01 ?05:04:39 amflush normal amanda 27972 27582 0 19:10 pts/000:00:00 ps -ef amanda 27973 27582 0 19:10 pts/000:00:00 grep amanda -bash-2.05b$ strace -p 22803 read(0, strace -p 22804 read(0, -bash-2.05b$ strace -p 22805 read(3, -bash-2.05b$ strace -p 22802 No output for this... I'm not sure what to expect for my results to be honest. If this isn't normal then I guess I should kill it. Then I need to know what the Root Cause is so I can fix it. On another matter, could of I just deleted these directories if I didn't want to flush them or would that cause problems? Thanks, James Paul Bijnens <[EMAIL PROTECTED]> wrote: > James Marcinek wrote: > > > amflush itself, the others aren't reporting anything: > > > > ps -ef |grep amanda |grep -v grep > > amanda 22803 22802 0 14:01 ?00:00:00 driver normal nodump > > amanda 22804 22803 0 14:01 ?00:00:00 taper normal > > amanda 22805 22804 0 14:01 ?00:00:00 taper normal > > root 27581 27541 0 17:29 pts/000:00:00 su - amanda > > amanda 27582 27581 0 17:29 pts/000:00:00 -bash > > amanda 22802 1 98 14:01 ?04:26:21 amflush normal > > > That's not normal at all. > You may have to kill it, then run amcleanup, and try again. > > If possible, I'm still interested in the loop it seems to be in > by issuing strace or truss, before killing it. > > > > > > > > > >>>It's been runninng for several hours now and my logs haven't been populating > >>>since it started. Here's the last few entries: > >>> > >>>START amflush date 20041207 > >>>START driver date 20041207 > >>>START taper datestamp 20041207 label Normal18 tape 0 > >>> > >>>I'm a bit confused because I now see a folder 20041207 in my /var/holding. > > > > It's > > > >>>empty, which is good if it's working properly. > >> > >>For flush, that's normal. > >> > >> > >>>Why isn't anything being populated too(amflush and log file)? Is there any > > > > way > > > >>>to tell if it's running properly? > >> > >>On linux:strace -p The-PID > >>on Solaris: truss -p The-PID > >> > >>"lsof -o the-PID" tells you which files are opened, and sometimes can > >>give a hint what it is doing (e.g. which file it is reading/writing). > > > > > > I issued an ls0f -op then-PID and got the following: > > > > lsof -p 22802 > > COMMAND PID USER FD TYPE DEVICESIZE NODE NAME > > amflush 22802 amanda cwdDIR 8,18 1052672 5783888 /tmp/amanda > > amflush 22802 amanda rtdDIR 8,1840962 / > > amflush 22802 amanda txtREG 8,18 14072 10174809 /usr/sbin/amflush > > amflush 22802 amanda memREG 8,18 106400 3784801 /lib/ld-2.3.2.so > > amflush 22802 amanda memREG 8,18 102888 14172763 > > /usr/lib/libamserver-2.4.3.so > > amflush 22802 amanda memREG 8,18 36460 14172762 > > /usr/lib/libamtape-2.4.3.so > > amflush 22802 amanda memREG 8,18 105992 14172761 > > /usr/lib/libamanda-2.4.3.so > > amflush 22802 amanda memREG 8,18 212020 8110087 /lib/tls/libm-2.3.2.so > > amflush 22802 amanda memREG 8,18 173000 14172290 > > /usr/lib/libreadline.so.4.3 > > amflush 22802 amanda memREG 8,18 11784 3784789 > > /lib/libtermcap.so.2.0.8 > > amflush 22802 amanda memREG 8,18 91624 3784813 /lib/libnsl-2.3.2.so > > amflush 22802 amanda memREG 8,18 52492 3784816 > > /lib/libnss_files-2.3.2.so > > amflush 22802 amanda memREG 8,18 1539996 8110085 /lib/tls/libc-2.3.2.so > > amflush 22802 amanda0u CHR1,3 163842 /dev/null > > amflush 22802 amanda1w REG 8,181015 12828895 > > /var/lib/amanda/normal/amflush > > amflush 22802 amanda2w REG 8,181015 12828895 > > /var/lib/amanda/normal/amflush > > amflush 22802 amanda3r FIFO0,5 6348
Re: Question using amflush
I initially just straced the parent process (22802 amflush normal) which didn't output anything: Here's the ps -ef again with the trace commands for each PID involved: ps -ef |grep amanda amanda 22803 22802 0 14:01 ?00:00:00 driver normal nodump amanda 22804 22803 0 14:01 ?00:00:00 taper normal amanda 22805 22804 0 14:01 ?00:00:00 taper normal root 27581 27541 0 17:29 pts/000:00:00 su - amanda amanda 27582 27581 0 17:29 pts/000:00:00 -bash amanda 22802 1 98 14:01 ?05:04:39 amflush normal amanda 27972 27582 0 19:10 pts/000:00:00 ps -ef amanda 27973 27582 0 19:10 pts/000:00:00 grep amanda -bash-2.05b$ strace -p 22803 read(0, strace -p 22804 read(0, -bash-2.05b$ strace -p 22805 read(3, -bash-2.05b$ strace -p 22802 No output for this... I'm not sure what to expect for my results to be honest. If this isn't normal then I guess I should kill it. Then I need to know what the Root Cause is so I can fix it. On another matter, could of I just deleted these directories if I didn't want to flush them or would that cause problems? Thanks, James Paul Bijnens <[EMAIL PROTECTED]> wrote: > James Marcinek wrote: > > > > I've recently deployed amanda. The client forgot tapes on several occasions and > > I've got 4 backups in my holding area. I initiated the amflush command and > > followed the instructions. The job kicked off in the background and I've been > > using: > > > > ps -ef |grep amanda > > > > to see if the process is still running, which it is. When I do a top command > > it's using lots of CPU time. > > Which process is taking CPU time? planner? driver? taper? > > > > > It's been runninng for several hours now and my logs haven't been populating > > since it started. Here's the last few entries: > > > > START amflush date 20041207 > > START driver date 20041207 > > START taper datestamp 20041207 label Normal18 tape 0 > > > > I'm a bit confused because I now see a folder 20041207 in my /var/holding. It's > > empty, which is good if it's working properly. > > For flush, that's normal. > > > > > Why isn't anything being populated too(amflush and log file)? Is there any way > > to tell if it's running properly? > > On linux:strace -p The-PID > on Solaris: truss -p The-PID > > "lsof -o the-PID" tells you which files are opened, and sometimes can > give a hint what it is doing (e.g. which file it is reading/writing). > > (hit Ctrl-C to stop it). > > PS. have also a look at "autoflush on": when forgetting a tape once, > the next time, amanda flushes automatically. >
