ADSM-L

Re: [ADSM-L] tsm tdp vss issues exchange 2010

2013-04-16 13:51:55
Subject: Re: [ADSM-L] tsm tdp vss issues exchange 2010
From: Del Hoobler <hoobler AT US.IBM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 16 Apr 2013 13:49:48 -0400
Hi Tim,

Yes.

Thanks,

Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu> wrote on 04/16/2013
01:18:06 PM:

> From: Tim Brown <TBrown AT CENHUD DOT COM>
> To: ADSM-L AT vm.marist DOT edu,
> Date: 04/16/2013 01:23 PM
> Subject: Re: tsm tdp vss issues exchange 2010
> Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT vm.marist DOT edu>
>
> Del,
>
> Thanks!
>
> If I have DB1 mounted as active on Exchange1 and DB1 mounted as
> passive on Exchange2 does that
> constitute 2 healthy  copies ?
>
> Thanks,
>
> Tim
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On
> Behalf Of Del Hoobler
> Sent: Tuesday, 16 April, 2013 1:14 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: tsm tdp vss issues exchange 2010
>
> 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 AT vm.marist DOT edu> wrote on 04/16/2013
> 11:59:49 AM:
>
> > From: Tim Brown <TBrown AT CENHUD DOT COM>
> > To: ADSM-L AT vm.marist DOT edu,
> > Date: 04/16/2013 12:24 PM
> > Subject: Re: tsm tdp vss issues exchange 2010 Sent by: "ADSM: Dist
> > Stor Manager" <ADSM-L AT vm.marist DOT 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.
> >
>