Amanda does not determine what backup level it's going to use until it's
finished estimating during the amdump process, which is handled by
amanda's magic balancing algorithms. Then, the way to see the current
level is by using amstatus. The balance shown here is indicative of a
nine-day old configuration that's never successfully been dumped :)
-Troy
On Thu, 2 Nov 2000, Denise Ives wrote:
> Is there a command line utlity that can verify the current back up
> level (0,1,2,3,4,5) or the
> next level amdump will run?
>
>
>
>
> thanks.
>
>
>
>
>
> amanda@sundev1 [daily] % amadmin daily balance
>
> due-date #fs orig KB out KB balance
> -------------------------------------------
> 11/01 Wed 9 14186107 14186304 +1900.0%
> 11/02 Thu 0 0 0 ---
> 11/03 Fri 0 0 0 ---
> 11/04 Sat 0 0 0 ---
> 11/05 Sun 0 0 0 ---
> 11/06 Mon 0 0 0 ---
> 11/07 Tue 0 0 0 ---
> 11/08 Wed 0 0 0 ---
> 11/09 Thu 0 0 0 ---
> 11/10 Fri 0 0 0 ---
> 11/11 Sat 0 0 0 ---
> 11/12 Sun 0 0 0 ---
> 11/13 Mon 0 0 0 ---
> 11/14 Tue 0 0 0 ---
> 11/15 Wed 0 0 0 ---
> 11/16 Thu 0 0 0 ---
> 11/17 Fri 0 0 0 ---
> 11/18 Sat 0 0 0 ---
> 11/19 Sun 0 0 0 ---
> 11/20 Mon 0 0 0 ---
> 11/21 Tue 0 0 0 ---
> 11/22 Wed 0 0 0 ---
> 11/23 Thu 0 0 0 ---
> 11/24 Fri 0 0 0 ---
> 11/25 Sat 0 0 0 ---
> 11/26 Sun 0 0 0 ---
> 11/27 Mon 0 0 0 ---
> 11/28 Tue 0 0 0 ---
> -------------------------------------------
> TOTAL 9 14186107 14186304 709315 (estimated 20 runs per
> dumpcycle)
> (9 filesystems overdue, the most being overdue 9 days)
> amanda@sundev1 [daily] %
>
>
>
>
>
>
>
>
>
>
>
