"Exchange2007-Q" <Exchange20***@discussions.microsoft.com> wrote in message
news:AD28502A-BBD3-4BF4-B8EF-266913B2392C@microsoft.com...
> in my company we performed a DR Test of exchange 2007 using SCR.
> source : CCR Cluster
> Targer : Standalone
>
> the source ship the logs to the target using the following configuration:
> Enable-StorageGroupCopy -ReplayLagTime 0.0:10:0 -TruncationLagTime
> 0.0:0:20
> -StandbyMachine $Target
>
> we have 7 SG (each can growth up to 100G)
> in the DR test we had SG1 with 50G and all the others were 100m
>
> we used Restore-Storagegroupcopy with the Force option.
>
> we ran the eseutil /r /a
>
> it took 30m for that command to run against SG1 (50G), all the other sg
> were
> less that 1sec
>
> and on the way back - Failback..it took only 0.3 sec - very fast.
> FYI on the way back the command to replicate was:
> Enable-StorageGroupCopy $DRServer\SG$  -StandbyMachine $hostname
> -ReplayLagTime 0.0:0:0 -Confirm:$False
>
> my Q:
> is the fact that ReplayLagTime was configured on the failback to 0.0:0:0
> caused the eseuti /r /a to run faster?
>
> if we will change the command of replication from Production to DR server
> also to 0.0:0:0 - will that help to REDUCE the time we had to wait for the
> eseutil to complete when we failover to the dr?
>
> appreciate your input

"Ed Crowley [MVP]" wrote:

> If you have a CCR cluster as your source, consider making your SCR target a
> single-node cluster, then you can use setup.com with the /RecoverCMS switch
> to do your recovery.
> --
> Ed Crowley MVP
> "There are seldom good technological solutions to behavioral problems."
> ..
>
> "Exchange2007-Q" <Exchange20***@discussions.microsoft.com> wrote in message
> news:AD28502A-BBD3-4BF4-B8EF-266913B2392C@microsoft.com...
> > in my company we performed a DR Test of exchange 2007 using SCR.
> > source : CCR Cluster
> > Targer : Standalone
> >
> > the source ship the logs to the target using the following configuration:
> > Enable-StorageGroupCopy -ReplayLagTime 0.0:10:0 -TruncationLagTime
> > 0.0:0:20
> > -StandbyMachine $Target
> >
> > we have 7 SG (each can growth up to 100G)
> > in the DR test we had SG1 with 50G and all the others were 100m
> >
> > we used Restore-Storagegroupcopy with the Force option.
> >
> > we ran the eseutil /r /a
> >
> > it took 30m for that command to run against SG1 (50G), all the other sg
> > were
> > less that 1sec
> >
> > and on the way back - Failback..it took only 0.3 sec - very fast.
> > FYI on the way back the command to replicate was:
> > Enable-StorageGroupCopy $DRServer\SG$  -StandbyMachine $hostname
> > -ReplayLagTime 0.0:0:0 -Confirm:$False
> >
> > my Q:
> > is the fact that ReplayLagTime was configured on the failback to 0.0:0:0
> > caused the eseuti /r /a to run faster?
> >
> > if we will change the command of replication from Production to DR server
> > also to 0.0:0:0 - will that help to REDUCE the time we had to wait for the
> > eseutil to complete when we failover to the dr?
> >
> > appreciate your input
>
>

"Exchange2007-Q" <Exchange20***@discussions.microsoft.com> wrote in message
news:54161D42-8B77-4FA2-B349-C43FF7EE9143@microsoft.com...
> and is that going to ELIMINATE the need to run eseutil /r /a ?
>
> as my goal is to reduce the time of activating the DR server in case of
> failover,
>
> currently i"m pleased with the stand alone process, unless you will tell
> me
> that it will dramatically will shorten the OUTAGE time
>
> "Ed Crowley [MVP]" wrote:
>
>> If you have a CCR cluster as your source, consider making your SCR target
>> a
>> single-node cluster, then you can use setup.com with the /RecoverCMS
>> switch
>> to do your recovery.
>> --
>> Ed Crowley MVP
>> "There are seldom good technological solutions to behavioral problems."
>> ..
>>
>> "Exchange2007-Q" <Exchange20***@discussions.microsoft.com> wrote in
>> message
>> news:AD28502A-BBD3-4BF4-B8EF-266913B2392C@microsoft.com...
>> > in my company we performed a DR Test of exchange 2007 using SCR.
>> > source : CCR Cluster
>> > Targer : Standalone
>> >
>> > the source ship the logs to the target using the following
>> > configuration:
>> > Enable-StorageGroupCopy -ReplayLagTime 0.0:10:0 -TruncationLagTime
>> > 0.0:0:20
>> > -StandbyMachine $Target
>> >
>> > we have 7 SG (each can growth up to 100G)
>> > in the DR test we had SG1 with 50G and all the others were 100m
>> >
>> > we used Restore-Storagegroupcopy with the Force option.
>> >
>> > we ran the eseutil /r /a
>> >
>> > it took 30m for that command to run against SG1 (50G), all the other sg
>> > were
>> > less that 1sec
>> >
>> > and on the way back - Failback..it took only 0.3 sec - very fast.
>> > FYI on the way back the command to replicate was:
>> > Enable-StorageGroupCopy $DRServer\SG$  -StandbyMachine $hostname
>> > -ReplayLagTime 0.0:0:0 -Confirm:$False
>> >
>> > my Q:
>> > is the fact that ReplayLagTime was configured on the failback to
>> > 0.0:0:0
>> > caused the eseuti /r /a to run faster?
>> >
>> > if we will change the command of replication from Production to DR
>> > server
>> > also to 0.0:0:0 - will that help to REDUCE the time we had to wait for
>> > the
>> > eseutil to complete when we failover to the dr?
>> >
>> > appreciate your input
>>
>>