ADSM-L

Re: client option sets and exclude lists

1998-08-12 09:36:19
Subject: Re: client option sets and exclude lists
From: "Mapes, Mark" <MWM4 AT PGE DOT COM>
Date: Wed, 12 Aug 1998 06:36:19 -0700
Try using as the option value INCLEXCL, then in the value put an INCLUDE or
EXCLUDE and the directories, files, wild cards, etc. (I got this from the
README of the latest PTF).

Mark Mapes
PG&E

> ----------
> From:         Karen Krowzack[SMTP:Karen.M.Krowzack AT UCM DOT COM]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Wednesday, August 12, 1998 5:52AM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      client option sets and exclude lists
>
> I hate to ask a dumb and simple question, but has anyone used a client
> option set to use include/exclude options?  I am trying to set this up on
> my
> ADSM AIX server for the UNIX clients it is backing up.  I cannot seem to
> do
> this from the command line "define clientopt unixoptionset exclude /tmp"
> (doesn't work - syntax error) The GUI in the WEB browser or win95 admin
> client won't let me point to an include/exclude list or cite individual
> excluded files.  What am I doing wrong?  Neither the admin guide or the
> admin reference talk about this in any detail.
>
> Besides wishing to setup a generic include/exclude list, I am also seeking
> to 'test' that my client option set really is in effect.  Since so many of
> the parameters that one puts in this file are performance related, does
> anyone have an idea of how to really test if a newly defined client option
> set really "works".  Thanks.
>
> Karen Krowzack
> IBM Global Services
> Tieline 461, x7309
> Outside phone - 312-394-7309
> Pager:  800-759-8888, PIN 1967096
> email:  Karen.M.Krowzack AT ucm DOT com
> PROFS:  krowzack(isscvm)
>
<Prev in Thread] Current Thread [Next in Thread>