Re: Exchange 2007 SP1 - SCR vs CCR

My understanding was:

The source can be standalone, CCR, or SCC.
The target can be standalone or the pssive node of a cluster that is not a
possible owner of any other CMS.

John


"Darren" <Darren@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:82F73307-F933-40C8-BB63-426994A0D430@xxxxxxxxxxxxxxxx
Thanks Bharat,

I've been lucky enough to talk with an Exchange tech today at Microsoft's
UK
HQ in Reading, here's what I've learnt:

SCR as implemeneted in SP1 will still require clustering.

As explained to me, it effectively allows the active node to Seed and
Log-Ship to a storage area at a seperate datacentre (this is done in
addition
to the seeding/logshipping being done by the passive node).

This offsite copy can then be accessed by a dedicated server at that site.
My understanding is that the 'recovery' steps need to bring the offsite
service online in the event of the datacentre being unavailable would be
manual ones

Exchange 14 when it's released, will remove the need for MSCS to be used
to
cluster.

Hopefully I'm not speaking out of turn - All of the above are my views
based
on informal chats with Exchange contacts at MS, so please dont take it as
gospel. If it turns out to be mis-information because I haven't understood
I
apologise, but hopefully it'll be of some benefit until more official
info
is available.

All the best,

Darren


"Bharat Suneja [MVP]" wrote:

Friday's post on the team blog was probably the first time this feature
was
talked about/announced publicly. Not a lot of details are available at
this
point.

--
Bharat Suneja
MVP - Exchange
www.zenprise.com
NEW blog location:
exchangepedia.com/blog
----------------------------------------------



"Darren" <Darren@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6AE618E4-00B1-43A7-8A25-509ADB2257BD@xxxxxxxxxxxxxxxx
I read on the Exchange Team blog site that Standby Continuous
Replication
is
going to provide the facility for Exchange 2007 to run a geographically
dispersed standby server without the need to stretch the subnet, which
would
normally be needed with a CCR cluster.

The implication is that the MS Cluster Services is done away with - so
no
need for the file share witness role, potentially no need for
Enterprise
software (maybe).

There doesn't seem to be any info yet on how SCR works yet tho -
anybody
heard anything? I presume it uses the same database seeding and log
shipping/transport dumpster technology but that the failover & recovery
is
handled through Exchange Console/Powershell as a manual process. Can't
find
any info on how the server to server comms are done either.

Any info greatly appreciated





.

Relevant Pages

  • Exch 2003 SP2 - applied on one node, but cant move resources
    ... only upon taking the resources "offline" in the Cluster administrator tool. ... Virtual Exchange server and failover occurred normally again upon taking the ...
    (microsoft.public.exchange.admin)
  • Re: Exch 2003 SP2 - applied on one node, but cant move resources
    ... only upon taking the resources "offline" in the Cluster administrator tool. ... Virtual Exchange server and failover occurred normally again upon taking the ... We recommend that you upgrade one Exchange cluster node at a time. ...
    (microsoft.public.exchange.admin)
  • Re: New Exchange 2007 Design
    ... Another problem could be that nodes in a CCR cluster must be in the same IP ... I'm working on some different design scenarios utilizing Exchange 2007. ... I will also deploy a separate Exchange server in each site running the hub ...
    (microsoft.public.exchange.design)
  • Re: Exchange 2207 CCR on std (non-MNS) cluster
    ... My client uses a SCC-type cluster under Exchange 2003, ... Microsoft seems to recommend CCR ... then install Exchange in a CCR configuration instead of a SCC configuration. ...
    (microsoft.public.exchange.setup)
  • Exchange 2207 CCR on std (non-MNS) cluster
    ... My client is a relatively small business - instead of racks full of blades, ... My client uses a SCC-type cluster under Exchange 2003, ... Microsoft seems to recommend CCR ...
    (microsoft.public.exchange.setup)
Loading