That is what Management classes and the ability to bind different management
classes to different files are there for.
We have somthing similar in the fact that we want different retentions for a
subset of files on a server, so we create a different management class and
add an include for those files to bind to the other management class.
Works as designed. (As long as a user does not run the Setup Wizard on a pre
4.12 WIN32 client - then the wizard merrily removes all of your
include/exlude statements!)
Tim Rushforth
City of Winnipeg
-----Original Message-----
From: Brian Nick [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 1:54 PM
To: [EMAIL PROTECTED]
Subject: Backup versions
Good afternoon everyone,
I have a question concerning backup versions.
We have an existing policy domain that is using the standard 30 day
backupretention period and I have received a request impacting several
clients in the domain to keep specific files for 7 years. My first thought
was to build a new policy domain with a 2555 backup retention but this
would hold all files on the clients for this length of time. I then thought
of building a new management class with VERExists=2555 VERDeleted=2555 and
RETExtra=NOLimit and point to that managementclass for the specific files
in the INCLUDE / EXCLUDE list of the DSM.OPT file. We want to do this with
backup not archive and this way we will only backup the data when it has
changed.
Have any of you run into a scenario like this and can you tell me if this
would work or if there is a better way of handling this. Any information
that you give me is appreciated.
Thanks,
Brian
Brian L. Nick
Systems Technician - Storage Solutions
Phoenix Home Life Mutual Ins.
100 Bright Meadow Blvd
Enfield CT. 06082-1900
E-MAIL: [EMAIL PROTECTED]
PHONE: (860)403-2281
