Jerry, I have seen this problem in the past but it isn't really a problem. I believe Tivoli would refer to it as a security feature. What happens when backups are performed is that directories, not files, are bound to the management class with the longest retention period. If you look at individual files, they should still be bound to the standard management class. You can override the directories being bound to the LOG_POLICY-MC by including an option in the client's configuration files that specifies the STANDARD management class as the location to bind directories to.
Christopher S. Young Senior System Engineer Gresham Enterprise Storage www.greshamstorage.com Office: 303.413.1799 x 205 Mobile: 303.717.2745 -----Original Message----- From: Jerry Caupain [mailto:[EMAIL PROTECTED]] Sent: Friday, October 26, 2001 3:12 AM To: [EMAIL PROTECTED] Subject: Strange behaviour???? Hello everyone, I have noticed something strange. In my policy domain I have two management classes. One is called STANDARD and the other is called LOG_POLICY-MC. I want to use the last one only for my log server so I included the following line in my include/exclude file: INclude /logs/.../* log_policy-mc Managementclass STANDARD is the default managementclass. Why is it that all my other systems also use the LOG_POLICY-MC managementclass? It seems that the directories on my other systems are all bound to this managementclass. This can't be normal............can it??? Jerry Caupain
