Hey @DanC , thanks for the post!
I’m trying to find the report (live) on my end, though I want to check if there’s an optional column for seal status or sealed date.
With that said, you’re only at a warning, you aren’t THAT low yet. It’s actually saying it doesn’t expect you to EVER be full, so either the projected growth is miniscule, or it’s already sealed.
Hello @DanC , thanks for bringing this up to our attention.
This is being addressed in future feature packs. Sealed DDBs will be excluded from this section of Health report.
Thank you @Mike and @Jahnavi
We have a long term SP retention for mailbox backup that prevent sealed DDB stores from reclaim.
- To get space reclaimed, I think i should open a support case to manually purge the references from CS DB right ?
@Jahnavi , that’s great news!
@DanC , it’s a pretty complex question regarding the space. If the DDB itself is large, then you likely have many records….and if those are valid, then without deleting jobs/references or lowering retention (same idea).
We can take a look at the Data Retention Forecast and Compliance report and see what jobs are still around using those DDBs, though a support case might be in store.
Worth checking out this thread which covers the process to see which jobs remain and why:
Let me know what you decide (and if you open a case, share the incident number with me here)!
@Mike Struening, thanks
Let me run data retention report to see what jobs are still around using those ddbs and also will take a look the thread that you provided and go from there and let you know what my next step
@DanC , following up on this one, did you find any evidence based on the data retention report?
@Mike Struening
DDB store has been removed and we’re good now
thank you for the assistance