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, Xplanation Tel +32 16 397.511
Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM Fax +32 16 397.512
http://www.xplanation.com/ email: Paul.Bijnens AT xplanation DOT com
***********************************************************************
* 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 *
***********************************************************************
|
