We had an FM200 release in our data center. DDBs became corrupt and restore failed. Sealed and started new DDB to get backups running. Now all jobs have aged out of the sealed DDB, but I still have 387TB of data on disk and I need the space back ASAP. SIDBPHysicalDeletes not showing continuous activity. Data aging ran multiple times.
Already have an account? Login
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Please check the following setting, when enabled it keeps that data from being pruned.
You can also run a data retention forecast & Compliance report to determine why the sealed DDB is not aging off jobs.
I believe when all jobs are eligible for pruning (met retention) for a corrupt store the deletes will show in cvma.log (also known as macro-pruning).