On Thu, May 12, 2005 at 11:40:21AM +0100, Rodrigo Ventura wrote:
> >>>>> "Jon" == Jon LaBadie <jon AT jgcomp DOT com> writes:
> 
>     Jon> These are level 1 dumps.  Maybe no changes?  Did you get the
>     Jon> same results on the last level 0?  If I recall, these are
>     Jon> mail dirs, is there stuff there?
> 
> Last dump summary:
> 
>                                      DUMPER STATS            TAPER STATS 
> HOSTNAME     DISK        L ORIG-KB OUT-KB COMP% MMM:SS  KB/s MMM:SS  KB/s
> -------------------------- --------------------------------- ------------
> omni         /           0 13315801331580   --    6:163543.9   6:163542.4
> omni         /boot       0    5020   5020   --    0:0011510.0   0:041246.0
> omni         /home/ag    2    7010   7010   --    0:023301.9   0:023041.9
> omni         /home/hm    1  109930 109930   --    0:205490.9   0:382924.1
> omni         /home/nt    2   25960  25960   --    0:045938.1   0:102607.6
> omni         /home/uz    0 25456402545640   --    9:064660.3  14:033019.2
> omni         /root       0  393480 393480   --    1:224826.4   2:132964.4
> omni         /usr        0 35510003551000   --   17:543305.3  13:364353.2
> omni         -ap/user/ag 0      10     10   --    0:00 182.9   0:04   2.7
> omni         -ap/user/hm 0      10     10   --    0:00 184.8   0:03   3.2
> omni         -ap/user/nt 0      10     10   --    0:00 133.9   0:08   1.3
> omni         -ap/user/uz 0 15315201531520   --   13:581828.5   7:523243.4
> 
> Now they are level 0, right? Still no dump. The latest one seems
> dumped ok, but I'm not sure. Check this interaction:
> 
> ----------------------------------------------------------------------
> # cd /
> # amrecover ISR
> AMRECOVER Version 2.4.4p4. Contacting server on omni ...
> 220 omni AMANDA index server (2.4.4p4) ready.
> 200 Access OK
> Setting restore date to today (2005-05-12)
> 200 Working date set to 2005-05-12.
> Scanning /var/amanda/dumps...
> 200 Config set to ISR.
> 200 Dump host set to omni.
> Trying disk / ...
> $CWD '/' is on disk '/' mounted at '/'.
> 200 Disk set to /.
> /
> amrecover> listdisk
> 200- List of disk for host omni
> 201- /
> 201- /boot
> 201- /usr
> 201- /root
> 201- /home/ag
> 201- /home/hm
> 201- /home/nt
> 201- /home/uz
> 201- /var/spool/imap/user/ag
> 201- /var/spool/imap/user/hm
> 201- /var/spool/imap/user/nt
> 201- /var/spool/imap/user/uz
> 200 List of disk for host omni
> amrecover> setdisk /var/spool/imap/user/uz
> 200 Disk set to /var/spool/imap/user/uz.
> amrecover> ls
> 2005-05-12 .
> 2005-05-12 vab/
> 2005-05-12 vale/
> 2005-05-12 vodakura/
> 2005-05-12 vsilva/
> 2005-05-12 vtraver/
> 2005-05-12 yoda/
> 2005-05-12 zlatan/
> amrecover> setdisk /var/spool/imap/user/ag
> 200 Disk set to /var/spool/imap/user/ag.
> No index records for disk for specified date
> If date correct, notify system administrator
> amrecover> ls
> amrecover>
> ----------------------------------------------------------------------


Does 'amadmin <config> disklist omni /var/spool/... ' show indexing
turned on?

Are there index files for those DLE's under your index dir?

Was there ever a successful backup of the DLE's in question?

Does the mailed to you report show anything of interest about
failures or strange results?

I presume the DLE's for /home/{ag|hm|nt} are similar to those for
/var/spool/imap/user/{ag|hm|nt}.  Same similarity for the "uz" entries.
Yet all the /home ones are working, the "include" ones for /var... aren't.

What is different about the /home and /var/spool DLE's?

What is different about /home itself vs /var/spool/imap/user?

-- 
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)