ADSM-L

Problem with error message from include/excluded files

1999-06-23 11:45:06
Subject: Problem with error message from include/excluded files
From: John Schneider <jdschn AT IBM DOT NET>
Date: Wed, 23 Jun 1999 10:45:06 -0500
Greetings,
    I think I have a good handle on include/exclude lists, but this one
has me stumped.
I am running the ADSM 3.1.2.20 server under AIX, and the latest AIX ADSM
client
fresh off the Web.

In my scheduler logs I keep receiving the messages:

Incremental backup of volume '/'
ANS1228E Sending of object '/info/notes/.lost' failed
ANS1105E The management class for this file does not have a valid backup
copy group.
This file will not be backed up.

ANS1228E Sending of object '/info/notes' failed
ANS1105E The management class for this file does not have a valid backup
copy group.
This file will not be backed up.

ANS1228E Sending of object '/info/tmp' failed
ANS1105E The management class for this file does not have a valid backup
copy group.
This file will not be backed up.

The files seem to be always directories, but only about 20 directories
out of the
many thousands on this system.  It is true that my default management
class does
not have a valid backup copy group, but the default management class
should not
be invoked.  My include/exclude list contains:

INCLUDE *    BACKUP-OS
INCLUDE /.../*    BACKUP-OS
INCLUDE /.../*    BACKUP-OS
INCLUDE /etc/.../*   BACKUP-OS
INCLUDE /usr/.../*   BACKUP-OS
INCLUDE /var/.../*   BACKUP-OS
INCLUDE /menu/.../*            BACKUP-OS
INCLUDE /mother/.../*            BACKUP-OS
INCLUDE /home/.../*            BACKUP-GENERIC
INCLUDE /vertex/.../*            BACKUP-GENERIC
EXCLUDE /tmp/.../*
INCLUDE /tmp/sap/*        BACKUP-GENERIC
INCLUDE /oracle/.../*            BACKUP-GENERIC
EXCLUDE /oracle/PRD/sapdata9[0-9]/.../*
EXCLUDE /oracle/PRD/sapdata8[0-9]/.../*
EXCLUDE /oracle/PRD/sapdata7[0-9]/.../*
EXCLUDE /oracle/PRD/sapdata6[0-9]/.../*
EXCLUDE /oracle/PRD/sapdata5[0-9]/.../*
EXCLUDE /oracle/PRD/sapdata4[0-9]/.../*
EXCLUDE /oracle/PRD/sapdata3[0-9]/.../*
EXCLUDE /oracle/PRD/sapdata2[0-9]/.../*
EXCLUDE /oracle/PRD/sapdata1[0-9]/.../*
EXCLUDE /oracle/PRD/sapdata[0-9]/.../*
EXCLUDE /oracle/PRD/saparch/.../*
EXCLUDE /oracle/PRD/saparch[0-9]/.../*
EXCLUDE /oracle/PRD/origlog[A-Z]/.../*
EXCLUDE /oracle/PRD/mirrlog[A-Z]/.../*
EXCLUDE /oracle/stage/.../*
EXCLUDE /oracle/stage/*
EXCLUDE /adsm/.../*
EXCLUDE /.../core

so that all files not otherwise specified should go the BACKUP-OS
management class. (Also, shouldn't the first and second line shown
above mean the same thing?  It seems like it should, but I have seen
examples on this list that have both.)

Both of the management classes shown above contain valid backup
copy groups.

I know that directories are handled differently than regular files, but
according to the manual, they should be directed to the management
class with the longest retention, in my case, BACKUP-GENERIC,
not the default management class.  Is there a special reason why the
default management class is being invoked here?

Just for grins, I also put a DIRMC BACKUP-GENERIC line
in the client's dsm.sys file, but the symptom didn't change.  That
should have forced all directories to that management class,
right?

Can anyone spot what obvious thing I must be overlooking?

TIA,

John Schneider

***********************************************************************
* John D. Schneider       Email: jdschn AT ibm DOT net * Phone: 314-349-4556
* Lowery Systems, Inc.
* 1329 Horan                  Disclaimer: Opinions expressed here are
* Fenton, MO 63026                   mine and mine alone.
***********************************************************************
<Prev in Thread] Current Thread [Next in Thread>