On Mon, Jul 31, 2006 at 03:24:28PM -0400, Mitch Collinsworth wrote:
> 
> On Mon, 31 Jul 2006, Alan Pearson wrote:
> 
> >I've tried to force a L0 backup of it, like :
> >
> >amadmin DailySet1 force qtvpdc.lab:/Shares
> >amadmin: qtvpdc.lab:/Shares is set to a forced level 0 at next run.
> >
> >
> >But when amdump runs, it just schedules a L1 or L2 backup.
> 
> Syntax:
> 
> % amadmin help
> 
> Usage: amadmin <conf> <command> {<args>} ...
>     Valid <command>s are:
>         version                         # Show version info.
>         force [<hostname> [<disks>]* ]+ # Force level 0 at next run.
...
>         info [<hostname> [<disks>]* ]*  # Show current info records.
...
> 
> 
> So your "amadmin DailySet1 force qtvpdc.lab:/Shares"
> should be "amadmin DailySet1 force qtvpdc.lab /Shares"
> 

Nice catch.  I'm surprised at the resulting message.
When I tried a similar bad syntax I got "amadmin: no disk matched"

The amadmin info command shows when a DLE is set to forced.
Here is one I forced for demo.


Current info for bigcow OPT:
  (Forcing to level 0 dump at next run)                 <<====
  Stats: dump rates (kps), Full:   64.0,  64.0,  -1.0
                    Incremental:   64.0,  64.0,  64.0
          compressed size, Full: 640.0%,640.0%,640.0%
                    Incremental: 640.0%,640.0%,640.0%
  Dumps: lev datestmp  tape             file   origK   compK secs
          0  20060727  vtape14            95      10      64    1
          1  20060731  vtape18           121      10      64    1


-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)