Just looking for some clarification please...I have a client who was having some issues with disk space on a couple of disk libraries. One of things I discovered is there are 2 DDBs which have Enable Physical Pruning disabled (those are also the only DDBs present).
To my knowledge, this setting was not disabled manually but other than running out of available disk space, no other actions were carried out. There are numerous events 62:2525 showing
Validation/Resynch of Deduplication Engine [XXXX] cannot proceed. Reason [Pruning is disabled on store].
Each DDB is therefore showing with a status of resynch scheduled.
My question is, would there be any scenario which would force the disabling of this setting other than say a DR recovery? I'm planning to just enable this setting on both DDBs but looking to check if there are any other gotchas/reasons why this should not be done.
Thanks in advance,