Hi Tim, Have you showed this to Microsoft?
The output below is from Microsoft's tool for integrity checking (ESEUTIL). Microsoft may be able to tell you why ESEUTIL could not access the file. On a side note... in case you were not aware: For databases in an Exchange Server DAG that have two or more healthy copies, the database integrity check can be skipped. You can do this using the /SKIPINTEGRITYCHECK option. Thanks, Del ---------------------------------------------------- "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> wrote on 04/16/2013 11:59:49 AM: > From: Tim Brown <tbr...@cenhud.com> > To: ADSM-L@vm.marist.edu, > Date: 04/16/2013 12:24 PM > Subject: Re: tsm tdp vss issues exchange 2010 > Sent by: "ADSM: Dist Stor Manager" <ADSM-L@vm.marist.edu> > > Initiating CHECKSUM mode... > > Verifying log files... > Base name: E00 > > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E000003C7FB.log - OK > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E000003C7FC.log - OK > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E000003C7FD.log - OK > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E000003C7FE.log - OK > "" > "" > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E000003D273.log > ERROR: Cannot open log file (\\?\GLOBALROOT\Device > \HarddiskVolumeShadowCopy20\Logs\DB1_Logs\E000003D273.log). Error -1032. > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E000003D274.log > ERROR: Missing log file(s). Log file is generation > 250484 (0x3D274), but expected generation is 250483 (0x3D273). > "" > "" > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E0000041F67.log - OK > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E0000041F68.log - OK > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E0000041F69.log - OK > Log file: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy20 > \Logs\DB1_Logs\E0000041F6A.log - OK > > Operation terminated with error -1032 (JET_errFileAccessDenied, > Cannot access file, the file is locked or in use) after 772.548 seconds. >