Andy,

Is it possible to specify a mgmtclass for "SYSTEM OBJECT" sysfiles?

We have tested and successfully implemented
       exclude.systemobject sysfiles
for 350 Win2K/XP clients [no active/inactive sysfile backups remain
for these clients], but we have an additional 650 Win2k/XP clients
that are still actively backing up ~2200 sysfiles/client daily.

The active policy set for these nodes contains two management classes
with the following backup copygroup settings:

Policy    Policy    Mgmt      Copy      Versions Versions   Retain  Retain
Domain    Set Name  Class     Group         Data     Data    Extra    Only
Name                Name      Name        Exists  Deleted Versions Version
--------- --------- --------- --------- -------- -------- -------- -------
YOD       ACTIVE    EXPIRING  STANDARD         1        0        0       0
YOD       ACTIVE    STANDARD  STANDARD         2        1       35      60

Before I exclude sysfiles from backup, I would like to specifically include
them to backup with our EXPIRING management class so that sysfiles will be
eligible for immediate deletion by "EXPIre Inventory" processing the next
day after I exclude them from backup, rather than having to wait for the
STANDARD RETOnly=60 days to pass.

Adding the following line to dsm.opt:
       Include "SYSTEM OBJECT" sysfiles expiring
does not generate any error, but I doubt that it's doing what I had hoped!

Is it possible to assign a specific mgmtclass for "SYSTEM OBJECT" sysfiles?
--
Jim.Owen AT Yale DOT Edu   (203.432.6693)