Just fooled with this, but on the latest 3.7.2 client. The syntax there is
exclude.dir c:\*
Kelly J. Lipp
Storage Solutions Specialists, Inc.
PO Box 51313
Colorado Springs CO 80949-1313
(719) 531-5926
Fax: (719) 260-5991
Email: [EMAIL PROTECTED]
www.storsol.com
www.storserver.com
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Tab Trepagnier
Sent: Wednesday, September 20, 2000 10:41 AM
To: [EMAIL PROTECTED]
Subject: Exclude.FS(?) on NT cluster
I haven't found the answer in the archives.
Server: ADSM 3.1.2.58 on AIX 4.3.2
Client: 3.1.0.8 on NT 4.0 Cluster Server
Two physical cluster nodes with 3 local drives each
Six shared drives hosting six virtual servers
In the next few days, we are transfering all data from our NT cluster's G:
drive
to newly-created K: drive. Of course, the virtual-server backup service
will
have to be reconfigured to follow suit. No problem.
The problem is with the services that back up the nodes' local drives.
Their
OPT domain statements say to use C:, D:, and E: drives only, but because the
OPT
file uses "include" and "exclude" rather than their more sophisticated
relatives, we get a full set of directory names from under each shared drive
associated with the local node backups. There are no files in those
directories, so the domain statement is working correctly there, but this is
a
big server and having duplicates of the directory names adds "noise" to the
ADSM
database.
Now that we are about to activate K: drive, I would like to prevent the
services
that backup the nodes' local drives from grabbing the directories of K:
drive.
Those directories will be backed up relative to the virtual server node.
How do I do this? I'm really just looking for the correct syntax for
"exclude.fs" or "exclude.dir" to force the schedule service of the
individual
cluster nodes to completely omit all references to K: drive, without
affecting
what the service for K: drive's virtual server backs up.
Thanks.
Tab Trepagnier
Laitram Corporation
