fyi - the graphical client, dsm, is very helpful in debugging include/exclue
problems.  Just remember that you must exit and restart dsm each time you
change the rules.

On Fri, 29 Jan 1999, Rupp Thomas (Illwerke) wrote:

> Hi ADSM-ers,
>
> I have another problem with our AIX client (3.1.0.5). We have a
> filesystem
> /tmp which suddenly gets not backed up any more.
> Here are the relevant ADSM config statements:
>         INCLUDE /.../*
>         Domain all-local
>         subdir yes
>
> $ df -k
> Filesystem    1024-blocks      Free %Used    Iused %Iused Mounted on
> /dev/hd4            40960     30616   26%     1814     9% /
> /dev/hd2          1310720    445268   67%    32082    10% /usr
> /dev/hd9var        131072     98420   25%      525     2% /var
> /dev/hd3            65536     42172   36%      364     3% /tmp
> /dev/hd1             8192      7888    4%       18     1% /homeloc
> /dev/worklv       3072000   2975260    4%       18     1% /work
> rs51:/home       16384000   2034056   88%    31973     1% /home
> rs51:/prog        6144000   3929880   37%    19832     2% /prog
> rs02:/o          10240000   2149388   80%    20646     1% /o
> rs02:/archive     5734400   1802580   69%      801     1% /archive
>
> No messages are seen in DSMSCHED.LOG or DSMERROR.LOG.
> Does anybody know why ADSM wont't backup the /tmp filesystem?
>
> Is my understanding correct that even a filesystem with no files to
> backup should alter
> the date/time in Q FILESPACE of  the Last Backup Start Date/Time and
> Last Backup Completion
> Date/Time?
>
> Kind regards
> Thomas Rupp
> Vorarlberger Illwerke AG
> MAIL:   thomas.rupp AT illwerke.co DOT at
> TEL:    ++43/5574/4991-251
> FAX:    ++43/5574/4991-820-8251
>