On Thu, Sep 05, 2019 at 14:12:29 -0400, Chris Hoogendyk wrote:
> Although my email said that the report was from the September 4th
> run, amstatus said it was giving me information about the September
> 4th run. What about the others?
[...]
> As a followup question, How do I get amstatus to tell me about
> multiple parallel runs and then deal with those individually?
> 

Short answer: use the --file option on "amstatus", after looking in
/var/log/amanda/<CONFIG> (or whatever your "logdir" is pointed to) to
find the specific amdump.<DATETIME> (or amflush.*) file you want to look
at.

I don't have a lot of experience with parallel runs, but off hand I
don't believe there is a way to get amstatus to do "show me the amdump
sessions that are currently running" -- you have to figure that out some
other way, or run amstatus on each file and look through the output to
see which ones are still underway (e.g. the "taped" DLE counts are less
than the total number of DLEs or whatever).

                                                Nathan
----------------------------------------------------------------------------
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region Ray
Ontko & Co.  - Software consulting services - http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239

Reply via email to