GregE
ADSM.ORG Senior Member
If there is a way to do it, a useful feature would be an inclexcl option to allow files on a path and directories on the same path to go to different storage pools. Similar to what we now have as DIRMC, but that can be applied to specific data.
Example:
A client with a 35 day overall retention.
A specific path on that client requires 1 year retention (or whatever.)
Currently DIRMC applies to the entire client data. If DIRMC is not used, the management class with longest RETAINONLY applies, but to the entire client.
It would be nice to have an inclexcl option which would allow something like this:
include /path_to_data_A/ mc_data
include.dirsonly /path_to_data_A/ mc_dir
Same data path, but files and directories treated differently, at a more granular level than DIRMC.
Some environments may not get involved in archiving, choosing instead to simply retain data as backup. This would be of assistance to that environment.
Example:
A client with a 35 day overall retention.
A specific path on that client requires 1 year retention (or whatever.)
Currently DIRMC applies to the entire client data. If DIRMC is not used, the management class with longest RETAINONLY applies, but to the entire client.
It would be nice to have an inclexcl option which would allow something like this:
include /path_to_data_A/ mc_data
include.dirsonly /path_to_data_A/ mc_dir
Same data path, but files and directories treated differently, at a more granular level than DIRMC.
Some environments may not get involved in archiving, choosing instead to simply retain data as backup. This would be of assistance to that environment.
