Hi Gerardo,
Unless I am mistaken (others correct me if I am wrong)
The include/exclude list is read from the bottom up. By including /t/.../*
you have also included the 'tuxedo' directory and subdirectories. The would
therefore be subject to the rules of policy1. You should redo the order of
the statements in your include/exclude file
include /t/.../* policy1
include /t/tuxedo/bialog/.../ politicy2
include /t/tuxedo/procesos/.../ politicy2
As long as you do not change the include/exclude file you should not see any
rebinding after the first backup.
Remember 1 mgmtclass per file. The only way to apply different mgmtclasses
to any given file is to define more than one server stanza in your dsm.sys
file, and that can get ugly real quick if you're not careful
Jim
-----Original Message-----
From: Gerardo Zapata [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 18, 2001 6:21 PM
To: [EMAIL PROTECTED]
Subject: INCLUDE/EXCLUDE STATEMENT
Hello,
I have a question about the utilization of the include exclude list.
I have specified the following statments in the list:
include /t/tuxedo/bialog/.../ politicy2
include /t/tuxedo/procesos/.../ politicy2
include /t/.../* policy1
The intention is to backup /t/.../* filesystem using the rules specified in
the policy1 management class (general policy for the filesystem.
And apply policy2 management class rules to the two specific directories.
We have a schdeuler that launches the /t/tuxedo/bialog and
/t/tuxedo/procesos
backups (includeing subdirectories) and another scheduler three hours later
that launches the backup of the /t/* filesystem (including subdirectories).
Is this combination valid?
Won't I have binding/rebinding problems in the future?
Thanks in advance
Regards,
Gerardo Zapata
IT Specialist
IBM Mexico
(52)-5270-5889
[EMAIL PROTECTED]
____________________________________________________________________
Get free email and a permanent address at http://www.netaddress.com/?N=1
