Hi, Mark! Thanks for the reply.
We left the dsm.opt file exactly as it was, but changed the default management class to MS_SERVER_OS. Any backups now got (re)bound to PC_SERVER_USERDATA! Once we verified that this was all good, we changed the default MC back to TODISK and without changing the dsm.opt did the same backup. Everything went to DEFAULT. We changed the default MC to NW_SERVER_OS and once again everything started going back to the correct MC - PC_SERVER_USERDATA in this case. We deleted to TODISK MC and recreated it exactly and made it the default. Now everything is binding correctly! Was it corrupted? Who knows! Any thoughts? Mahesh On Wed, 2004-02-04 at 15:39, Stapleton, Mark wrote: > From: Mahesh Tailor [mailto:[EMAIL PROTECTED] > INTEL MS_SERVER_OS 7 1 > 30 60 > INTEL NW_SERVER_DATA 7 2 > 60 NOLIMIT > INTEL NW_SERVER_OS 1 1 > 30 30 > INTEL PC_SERVER_APPS 2 1 > 15 30 > INTEL PC_SERVER_GROUPWISE_LC 5 1 > 120 NOLIMIT > INTEL PC_SERVER_GROUPWISE_MAIL 5 1 > 14 14 > INTEL PC_SERVER_GROUPWISE_SOFTWARE 1 1 > 1 1 > INTEL PC_SERVER_METAFRAME 1 1 > 15 30 > INTEL PC_SERVER_NDS 5 1 > 30 30 > INTEL PC_SERVER_OS 2 1 > 30 30 > INTEL PC_SERVER_USERDATA 10 1 > 120 NOLIMIT > INTEL TODISK 2 1 > 1 15 > > Where TODISK is the default management class. > > In the client include exclude list we have the following line [just this one > line; no others present]: > > INCLUDE data:...\*.* PC_SERVER_USERDATA > > All files get bound to DEFAULT. We create a new file, same thing. An old > file does not get rebound either. > > ================= > > I think the problem may be your include syntax. It should read: > > include data:\...\* pc_server_userdata > > Don't forget that, without a directory management class definition, all > directory entries will be backed up to the management class with the longest > retention. > > -- > Mark Stapleton ([EMAIL PROTECTED]) -- Mahesh Tailor WAN/TSM/NetView Administrator Carilion Health System Information Services 37 Reserve Avenue Roanoke, VA 24016 Phone: 540.224.3929 Fax: 540.224.3954
