Backup Exec 2012 DLM
I hope someone could help me out with a DLM query. Our environment consists 2 sites. We have 1 CASO server which is used for job admin only. It performs no backup or dedupe jobs. We create the jobs here and point the jobs at a managed server. Each site has 1 managed server. We are running Backup Exec 2012 SP3 on Windows 2008 R2. The catalog mode is in distributed mode.
I understand DLM will not delete a backup cycle even if the backup set has expired if it is the last recovery point. What I don't understand is how DLM treats multiple copies of backup sets.
So we backup to disk with a retention period of 5 days. We run a Full on a Friday and Inc's each day until the Full runs again on the Friday. So DLM will not groom anything on disk despite being expired until 2 cycles are completed. Fine.
However, after each backup we duplicate the backup to a local dedupe disk and retain for 2 weeks. We then run an optimized dedupe job to the remote site and retain for 4 weeks. So there are now 3 copies of the backup set.
So should DLM groom the backup sets in the backup to disk location after 5 days even if it is the last recovery point as the backup sets have been duplicated to a dedupe store with a longer retention period. Or, will it wait until cycle 2 completes then groom the backups on disk without considering the dedupe storage? DLM for the dedupe storage is then handled separately?
Or, as each backup set is kept for 4 weeks in the off site dedupe does DLM wait for this 4 week retention to expire before grooming all backup sets together? (On disk, local dedupe and remote dedupe)
I understand tape backup sets are not considered for DLM grooming, but there is an added complication that backups are also duplicated to tape for off site recovery.
Basically, DLM isn't grooming backup sets in the backup to disk storage and I'm trying to understand why. In most cases I can right Click and delete so there are not dependencies so I'm trying to fully understand the DLM process with multiple backup sets.