Skip to main content

Hi Team,

So I’ve been limping along with a dirty-flag on the drive hosting my DDB.

This actually occurred due to a CrowdStrike BSOD a few weeks back, but recovering data was more important than clearing the CHKDSK.

However, we obviously cannot limp along forever.
I am assuming the worst here, and that when we finally allow CHKDSK to repair the volume it will corrupt my DDB.  It usually does, and I have seen this before.

So I suppose the question is, do I just roll with it, or is there something else I can do to minimize the impact of a potential DDB Recovery? 

Thanks

Aside from ensuring that you have a clean DDB backup, I would make sure that the MediaAgent services have been shutdown (and that the SIDB processes have gracefully stopped) before attempting to repair the volume.

If you had space, you could also look at relocating the DDB to a different volume. 

 

Reply


Terms & ConditionsCookie settings