Dave - thank you for the response.

The results I posted for sda10 were from the level 0
for that partition which was from a week ago. I ran amdump this past
weekend and sda10 gave me the 'forcing level 0 on next dump message'. All
my other partions showed the current date and time of this weekends dump 
and the amanda tape it went to.  label: daily001

i.e.


Current info for admin1.corp..walidcom sda1:
  Stats: dump rates (kps), Full:  2016.0, 3024.0, 3024.0
                    Incremental:   32.0,  -1.0,  -1.0
          compressed size, Full: -100.0%,-100.0%,-100.0%
                    Incremental: -100.0%,-100.0%,-100.0%
  Dumps: lev datestmp  tape             file   origK   compK secs
          0  20001209  daily001            2    6020    6048    3


Current info for admin1.corp.walid.com sda2:
  Stats: dump rates (kps), Full:  2016.0, 3024.0, 3024.0
                    Incremental:   32.0,  -1.0,  -1.0
          compressed size, Full: -100.0%,-100.0%,-100.0%
                    Incremental: -100.0%,-100.0%,-100.0%
  Dumps: lev datestmp  tape             file   origK   compK secs
          0  20001209  daily001            2    6020    6048    3



Then I got this only for sda10:

>                   
> > Current info for admin1.corp.walid.com sda10:
> >   (Forcing to level 0 dump on next run)
> >   Stats: dump rates (kps), Full:  3106.0, 3364.0, 3100.0
> >                     Incremental:  1735.0, 3089.0, 2364.0
> >           compressed size, Full: -100.0%,-100.0%,-100.0%
> >                     Incremental: -100.0%,-100.0%,-100.0%
> >   Dumps: lev datestmp  tape             file   origK   compK secs
> >           0  20001203  daily119            9 9341985 9341984 3007
> >







On Sun, 10 Dec 2000, David Lloyd wrote:

> 
> Denise!
> 
> > I forced a level 0 to run this afternoon - when it was done no AMANDA MAIL
> > REPORT was generated.
> > 
> > When I looked at the current info via amadmin I noticed that all of my
> > partions were backed up to tape except sda10 which was 'forced to a level
> > 0 dump on next run'.
> 
> Was it, or was it not backed up? The info below suggests that it was...
> 
> > Current info for admin1.corp.walid.com sda10:
> >   (Forcing to level 0 dump on next run)
> >   Stats: dump rates (kps), Full:  3106.0, 3364.0, 3100.0
> >                     Incremental:  1735.0, 3089.0, 2364.0
> >           compressed size, Full: -100.0%,-100.0%,-100.0%
> >                     Incremental: -100.0%,-100.0%,-100.0%
> >   Dumps: lev datestmp  tape             file   origK   compK secs
> >           0  20001203  daily119            9 9341985 9341984 3007
> > 
> > Do you know why this happened and if I  can re-generate the daily AMANDA
> > MAIL REPORT?
> 
> Look in the place that AMANDA logs. You'll see lots of amflush.# and
> amdump.#. Most people also keep their curinfo databases there as well.
> Ours is /usr/adm/amanda/[configuration name]/
> 
> In there run:
> 
> [amanda@localhost MYCONFIG]% amstatus --file amdump.1
> 
> (.1 should be the latest set of dumps). You may want to pipe it to mail
> or use the > operator to save it to file...although this isn't the full
> information it is a start.
> 
> DL
> 

-- 
Denise E. Ives                          [EMAIL PROTECTED]
Systems Engineer                        734.822.2037

Multilingual Internet Domain Name Registrations - http://www.walid.com

Reply via email to