Friday, February 8, 2008

A quota scan on directory "\[DIR]" on volume "\Device\VSPSnapshot0 (N/A)" failed unexpectedly

Source: Quota
Event ID: 12
The quota minifilter driver completed rescanning directories under quota management on volume "\Device\VSPSnapshot0 (N/A)". Some directories under quota management could not be scanned.

Source: Quota
Event ID: 11
A quota scan on directory "\[dir]" on volume "\Device\VSPSnapshot0 (N/A)" failed unexpectedly. Error code: 0xc0000010 The quota usage for the quota on this directory and any parent directories may be incorrect. The affected quotas may not be properly enforced. You can attempt to initiate a new scan using the quota management command line tool. If the problem persists, reboot your system.

Source: Quota
Event ID: 11
A quota scan on directory "\[dir]" on volume "\Device\VSPSnapshot0 (N/A)" failed unexpectedly. Error code: 0xc0000010 The quota usage for the quota on this directory and any parent directories may be incorrect. The affected quotas may not be properly enforced. You can attempt to initiate a new scan using the quota management command line tool. If the problem persists, reboot your system.

Since we have implemented File Server Resource Manager on our new Windows 2003 r2 server we are getting these cryptic errors every day. After lot of goggling I have found only these links
But none of them helped me.

Today suddenly after comparing it daily occurrence I got reason behind it. In our scenario this error is logged everyday between 4 to 5 am which is time of File server backup (which is dome through Symantec Backup Exec). This happen because at the time of backup disk is too busy to respond to quota scan service.

1 comment:

townman said...

Thanks you enlighten me, I'v same error since the setup of FSRM.

Look like the BackupExec is interuupt the FSRM scan proccess