Does this server do an ADSM scheduled backup?  If so, have you checked the
schedule to see if SYS1: is listed as one of the objects to be backed up in
that schedule's definition?




ADSM-L AT VM.MARIST DOT EDU on 08/17/99 06:46:59 PM
Please respond to ADSM-L AT VM.MARIST DOT EDU @ INTERNET
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: ADSM - Netware 'Exclude' Problem

Hi there,
        I hope someone can help me with this query.  We have a number of
Netware servers with ADSM clients, and an ADSM server that runs on an OS/390
MVS Mainframe. Recently we have changed the client DSM.OPT files so that the
value
DOMAIN  =  ALL  LOCAL
is used instead of specifying each individual volume to be handled by using
DOMAIN  DATA:  SYS:  SYS1:

However, recently we removed a volume (SYS1) from a Netware server, and now
the client backup is failing as it can't find the volume.  ADSM doesn't seem
to recognise that the volume involved (SYS1) is no longer a local volume.

Other than deleting the filespace data for this volume, is there some way of
having an exclude in the DSM.OPT file to stop ADSM from attempting to back
up the volume.

Volumes will be moved from server to server and come and go as we move
closer to cluster technology for NetWare.  It's a pain having to
specifically specify volumes to be backed up. I would prefer to be able to
backup everything, and exclude what I don't want.

I would rather not have to go back to specifying the individual volumes to
be handled (eg.  DOMAIN  DATA:  SYS: ), so I hope someone out there can
assist me.

Thanks,
Gary Johnson
Operations Analyst  (Emergency Planning)
IT Operations
CLEAR Communications Ltd
12th floor,  49 Symonds Street, Auckland, 1001, New Zealand
phone:  (64-9)  912-4200
   DDI:  (64-9)  912-4984
    fax:  (64-9)  912-4454
 email:  gjohnso AT clear.co DOT nz