|
|
|
date: Mon, 28 Apr 2008 15:39:00 -0700,
group: microsoft.public.exchange.clustering
back
Re: how to identify if it's CCR or SCC
1. I never configured CCR so was wondering if there is a GUI or something
that will show you the source and target and which DB has been set for CCR,
status, etc from a central point. If I have multiple CCR it takes time to
get information using cmdlets. The traditional cluster (SCC) console
provides more information.
2. I understand I can create a new fsw if the original failed and use manual
failover. Is it possible to have a standby fsw to take over if the original
one failed? Tried to avoid such manual action if possible. Also, people may
not be aware of fsw running on the failed server. For example, if fsw is
running on a DC which is controlled by AD team and it failed then AD team
might just rebuild the DC. No one will realize that FSW has to be re-created
on the same server or different server since it's part of Exchange team. If
there is a backup to take over automatically then there will be no impact for
auto failover.
3. If the original fsw wnet offline and I created a new one on a different
server. Later one the offline line server came back online with its original
fsw. Now, I got two fsw for the same CCR cluster. Will there be any
problems? I guess I have to remove one of them?
4. with CCR do I need to use windows cluster admin console at all? In the
console it showed me pretty much the same thing like traditional cluster,
cluster and exchange groups, each node, resources, etc. (is that supposed to
be?) But I think I should use EMC to manage the cluster. I never used
majority node cluster so trying to understand how to use the cluster admin
console.
5. will read the article for new fsw recommendation. A quick question.
Both nodes for CCR and FSW are at the datacenter. In such case is CNAME
recommended since there are not a streteched cluster.
Thanks.
"Bharat Suneja [MSFT]" wrote:
> Responses inline.
>
> --
> Bharat Suneja
> Microsoft Corporation
> ------------------------
> This posting is provided "AS IS" with no warranties, and confers no
> rights. Please do not send email directly to this alias. This alias is for
> newsgroup purposes only.
>
>
> "Chris" wrote in message
> news:1258CB10-11F1-4878-9409-051E0461170A@microsoft.com...
> > Bharat,
> > 1. I ran Get-MailboxServer and it showed me ClusterStorageType is
> > nonshared.
> > So I got CCR. But how can I view the CCR configuration?
>
> Not sure what you mean by CCR configuration. The available options:
> Get-ClusteredMailboxServer
> Get-StorageGroupCopyStatus
>
> >
> > 2. I ran Cluster houcmb1 res "Majority Node Set" /priv and got the value
> > as
> > "\\fsw_serv1\mns_fsw_houcmb1". what I found is that fsw_serv1 is a CNAME
> > pointing to a cas server houhcas1. I think it's OK but what should I do
> > if
> > houhcas1 is down? Do I need to configure another FSW on another server
> > then?
> > How can I implement a backup solution ahead of time?
>
> The earlier recommendation from Microsoft was to use a CNAME record for
> stretched clusters (cluster nodes in different datacenters).
> This has since been updated - we do not recommend using a CNAME any more.
>
> New File Share Witness and Force Quorum Guidance for Stretched Exchange 2007
> Clusters
> http://msexchangeteam.com/archive/2008/04/03/448615.aspx
>
> If a server hosting the FSW file share becomes unavailable, cluster
> operations will not be impacted. However, you will not have automated
> failovers. Manual failovers are possible.
>
> You can recreate the FSW on a different server using the same procedure that
> you used to create the FSW. This is documented here:
> For Windows Server 2003 cluster:
> How to Configure the File Share Witness
> http://technet.microsoft.com/en-us/library/bb124922(EXCHG.80).aspx
>
> For Windows Server 2008 cluster:
> How to Configure the Node and File Share Majority Quorum
> http://technet.microsoft.com/en-us/library/bb676490(EXCHG.80).aspx
>
>
> >
> > Thanks.
> >
> > "Bharat Suneja [MSFT]" wrote:
> >
> >> 1) Get-MailboxServer -> look at the ClusteredStorageType property.
> >> SCC = shared
> >> CCR = non-shared
> >> Disabled = server not clustered.
> >>
> >> 2) File Share Witness name is a property of the cluster group's Majority
> >> Node Set resource. It can be retrieved using the following command:
> >> Cluster "Cluster Name" res "Majority Node Set" /priv
> >>
> >> (step 5 in "How to Configure the File Share Witness"
> >> http://technet.microsoft.com/en-us/library/bb124922(EXCHG.80).aspx)
> >>
> >> --
> >> Bharat Suneja
> >> Microsoft Corporation
> >> ------------------------
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights. Please do not send email directly to this alias. This alias is
> >> for
> >> newsgroup purposes only.
> >>
> >>
> >> "Chris" wrote in message
> >> news:7E7EEA05-BE35-44E8-A15F-04431D8E125C@microsoft.com...
> >> > Two Exchange server 2007 are in a cluster. How can I tell if there are
> >> > configured as CCR or SCC? If CCR how can I tell which server is used
> >> > for
> >> > File share witness?
> >> >
> >> > Thanks.
> >>
> >>
>
>
date: Wed, 30 Apr 2008 08:27:00 -0700
author: Chris
Re: how to identify if it's CCR or SCC
Responses inline.
--
Bharat Suneja
Microsoft Corporation
------------------------
This posting is provided "AS IS" with no warranties, and confers no
rights. Please do not send email directly to this alias. This alias is for
newsgroup purposes only.
"Chris" wrote in message
news:E14F61C1-7916-429F-9133-69FDBE06680F@microsoft.com...
> 1. I never configured CCR so was wondering if there is a GUI or something
> that will show you the source and target and which DB has been set for
> CCR,
> status, etc from a central point. If I have multiple CCR it takes time to
> get information using cmdlets. The traditional cluster (SCC) console
> provides more information.
Only 2 cluster nodes participate in a CCR environment - one's active, the
other one is passive.
The cluster mgmt console or cluster.exe can tell you which node owns the
resources/CMS.
>
> 2. I understand I can create a new fsw if the original failed and use
> manual
> failover. Is it possible to have a standby fsw to take over if the
> original
> one failed?
No. Only one FSW is supported.
>Tried to avoid such manual action if possible. Also, people may
> not be aware of fsw running on the failed server. For example, if fsw is
> running on a DC which is controlled by AD team and it failed then AD team
> might just rebuild the DC. No one will realize that FSW has to be
> re-created
> on the same server or different server since it's part of Exchange team.
> If
> there is a backup to take over automatically then there will be no impact
> for
> auto failover.
One reason locating the FSW on servers controlled by the same team
(Exchange/messaging) is a good idea.
Locating it on a Hub Transport server is recommended- it provides mail
transport functionality to a CMS, and it also hosts another important piece
of the CCR puzzle - the transport dumpster.
>
> 3. If the original fsw wnet offline and I created a new one on a different
> server. Later one the offline line server came back online with its
> original
> fsw. Now, I got two fsw for the same CCR cluster. Will there be any
> problems? I guess I have to remove one of them?
The server hosting the FSW merely offers a shared folder where the cluster
stores some information.
The FSW's identity (shared folder name) is stored in one of the private
properties of MNS quorum.
When you bring up a new FSW, the old one goes away - though it may have the
shared folder and stale information left over from when it went offline.
Bottomline - there's no impact from a previous FSW coming online again.
>
> 4. with CCR do I need to use windows cluster admin console at all? In the
> console it showed me pretty much the same thing like traditional cluster,
> cluster and exchange groups, each node, resources, etc. (is that supposed
> to
> be?) But I think I should use EMC to manage the cluster. I never used
> majority node cluster so trying to understand how to use the cluster admin
> console.
Moving the CMS (Clustered Mailbox Server) should be done from Exchange
(using EMC or EMS).
Any cluster-related management tasks like changing resource or group
settings can be done using the cluster mgmt console or cluster.exe command.
>
> 5. will read the article for new fsw recommendation. A quick question.
> Both nodes for CCR and FSW are at the datacenter. In such case is CNAME
> recommended since there are not a streteched cluster.
Once again, Microsoft doesn't recommend using a CNAME any more, even for
streteched clusters.
The team blog post quoted earlier has details.
>
> Thanks.
>
> "Bharat Suneja [MSFT]" wrote:
>
>> Responses inline.
>>
>> --
>> Bharat Suneja
>> Microsoft Corporation
>> ------------------------
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights. Please do not send email directly to this alias. This alias is
>> for
>> newsgroup purposes only.
>>
>>
>> "Chris" wrote in message
>> news:1258CB10-11F1-4878-9409-051E0461170A@microsoft.com...
>> > Bharat,
>> > 1. I ran Get-MailboxServer and it showed me ClusterStorageType is
>> > nonshared.
>> > So I got CCR. But how can I view the CCR configuration?
>>
>> Not sure what you mean by CCR configuration. The available options:
>> Get-ClusteredMailboxServer
>> Get-StorageGroupCopyStatus
>>
>> >
>> > 2. I ran Cluster houcmb1 res "Majority Node Set" /priv and got the
>> > value
>> > as
>> > "\\fsw_serv1\mns_fsw_houcmb1". what I found is that fsw_serv1 is a
>> > CNAME
>> > pointing to a cas server houhcas1. I think it's OK but what should I
>> > do
>> > if
>> > houhcas1 is down? Do I need to configure another FSW on another server
>> > then?
>> > How can I implement a backup solution ahead of time?
>>
>> The earlier recommendation from Microsoft was to use a CNAME record for
>> stretched clusters (cluster nodes in different datacenters).
>> This has since been updated - we do not recommend using a CNAME any more.
>>
>> New File Share Witness and Force Quorum Guidance for Stretched Exchange
>> 2007
>> Clusters
>> http://msexchangeteam.com/archive/2008/04/03/448615.aspx
>>
>> If a server hosting the FSW file share becomes unavailable, cluster
>> operations will not be impacted. However, you will not have automated
>> failovers. Manual failovers are possible.
>>
>> You can recreate the FSW on a different server using the same procedure
>> that
>> you used to create the FSW. This is documented here:
>> For Windows Server 2003 cluster:
>> How to Configure the File Share Witness
>> http://technet.microsoft.com/en-us/library/bb124922(EXCHG.80).aspx
>>
>> For Windows Server 2008 cluster:
>> How to Configure the Node and File Share Majority Quorum
>> http://technet.microsoft.com/en-us/library/bb676490(EXCHG.80).aspx
>>
>>
>> >
>> > Thanks.
>> >
>> > "Bharat Suneja [MSFT]" wrote:
>> >
>> >> 1) Get-MailboxServer -> look at the ClusteredStorageType property.
>> >> SCC = shared
>> >> CCR = non-shared
>> >> Disabled = server not clustered.
>> >>
>> >> 2) File Share Witness name is a property of the cluster group's
>> >> Majority
>> >> Node Set resource. It can be retrieved using the following command:
>> >> Cluster "Cluster Name" res "Majority Node Set" /priv
>> >>
>> >> (step 5 in "How to Configure the File Share Witness"
>> >> http://technet.microsoft.com/en-us/library/bb124922(EXCHG.80).aspx)
>> >>
>> >> --
>> >> Bharat Suneja
>> >> Microsoft Corporation
>> >> ------------------------
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights. Please do not send email directly to this alias. This alias is
>> >> for
>> >> newsgroup purposes only.
>> >>
>> >>
>> >> "Chris" wrote in message
>> >> news:7E7EEA05-BE35-44E8-A15F-04431D8E125C@microsoft.com...
>> >> > Two Exchange server 2007 are in a cluster. How can I tell if there
>> >> > are
>> >> > configured as CCR or SCC? If CCR how can I tell which server is
>> >> > used
>> >> > for
>> >> > File share witness?
>> >> >
>> >> > Thanks.
>> >>
>> >>
>>
>>
date: Wed, 30 Apr 2008 10:20:32 -0700
author: Bharat Suneja [MSFT]
|
|
