Look it the amdump.1 file , the log file or the email report, you should
find why it did a level 1.
Jean-Louis
On 12/13/2011 10:56 AM, Valeriu Mutu wrote:
2 days ago I ran 'amadmin<conf> force' command on a DLE but it appears that it
still did level 1 on next amdump.
Here is what I did before the currently running 'amdump':
# su amanda -c "amadmin Daily1 force cronos.some.domain /pcbi/cbil"
amadmin: cronos.some.domain:/pcbi/cbil is set to a forced level 0 at next run.
The current 'amdump' show level 1 being done:
# amstatus Daily1|grep /pcbi/cbil
cronos.some.domain:/pcbi/cbil 1 469094m dump done (9:53:14), wait
for writing to tape
If I run 'force' and then 'due' I get:
# su amanda -c "amadmin Daily1 force cronos.some.domain /pcbi/cbil"
amadmin: cronos.some.domain:/pcbi/cbil is set to a forced level 0 at next run.
# su amanda -c "amadmin Daily1 due cronos.some.domain /pcbi/cbil"
Due in 3 days: cronos.pcbi.upenn.edu:/pcbi/cbil
Can anyone explain this Amanda behavior? I'm running Amanda 2.6.1p2.
