Running disk defragment tool on backing store

AXCHU

We are on Windwos 2003. We are gradually experiencing interesting behaviors in the backing store, like inaccurate version history description, group sids being replaced by user sids, a few corrupted .tpl files and etc.

We don’t know what caused the problem. We know that our server operation group has been running anti-virus and disc defragment tools against the backing store drive. However, we cannot find any articles indicating that external processes running against active backing store might cause corruption to the store.

Could the external process be the cause of the problem? If so, do we have documentation to support the statement?

Has anyone experienced similar problems?

Any feedback is appriciated, Thanks.

Adam Stoller

We are on Windwos 2003. We are gradually experiencing interesting behaviors in the backing store, like inaccurate version history description, group sids being replaced by user sids, a few corrupted .tpl files and etc. We don’t know what caused the problem. We know that our server operation group has been running anti-virus and disc defragment tools against the backing store drive. However, we cannot find any articles indicating that external processes running against active backing store might cause corruption to the store. Could the external process be the cause of the problem? If so, do we have documentation to support the statement? Has anyone experienced similar problems? Any feedback is appriciated, Thanks.

There are a number of support KBs and I think some documentation in one of the manuals (probably the Admin manual) about the use of anti-virus software and the backing store.

To the best of my knowledge - I've never seen anything about defrag and the backing store - but then I would never thing to try such a thing - at least not with TS running (was TS running when they ran the defrag?)

My recommendation is:

BIRTXMLError.doc