You need to deploy the application so that it is available if a single server fails

Your network consists of a single Active Directory domain. The network contains a file server that runs
Windows Server 2008 R2. All servers use internal storage only. You plan to deploy a client/server application.
You need to deploy the application so that it is available if a single server fails. You must achieve this goal while
minimizing costs.
What should you do?

Your network consists of a single Active Directory domain. The network contains a file server that runs
Windows Server 2008 R2. All servers use internal storage only. You plan to deploy a client/server application.
You need to deploy the application so that it is available if a single server fails. You must achieve this goal while
minimizing costs.
What should you do?

A.
Deploy RemoteApp.

B.
Deploy a failover cluster that uses No Majority: Disk Only.

C.
Deploy a failover cluster that uses Node and FileShare Disk Majority.

D.
Deploy Distributed File System (DFS) and configure replication.

Explanation:
HIGH AVAILABILITY OF APPLICATION/SERVICE
A client/server application is an application that uses a central place (server) to store its data butis accessed
from one or more client computers, e.g. SQL, Outlook/Microsoft Exchange, dynamic web-based applications.
Failover clusteringprovides high availability for client/server applications, DFS Namespace Server, DHCP
Server, Distributed Transaction Coordinator (DTC), File Server, Internet Storage Name Service (iSNS) Server,
Message Queuing, Print Server, Remote Desktop Connection Broker (formerly TS Session Broker), Virtual
Machine and WINS Server.
Failover clustering is configured according to quorum. Quorumfor a cluster is determined by the number of
voting elements (active cluster members) for that cluster to start properly or continue running. Cluster
configuration is stored in the nodes, disk witness and/or file share witness. There are 4 quorum configurations:
1. Node Majority(recommended for clusters with an odd number of nodes)
2. Node and Disk Majority(recommended for clusters with an even number of nodes)
3. Node and File Share Majority: An alternative to Node and Disk Majority by using a file share witness instead
of a disk witness.
4. No Majority: Disk Only(not recommended): Can sustain failures of all nodes except one (if the disk is
online). However, this configuration is not recommended because the disk might be a single point of failure.
(Comment: But how about providing high availabilityfor the disk witness, e.g. RAID 1/5 with MPIO? Such a
configuration maximizes the availability of the nodes!)
http://technet.microsoft.com/en-us/library/cc731960.aspx
http://technet.microsoft.com/en-us/library/cc731739.aspx



Leave a Reply 0

Your email address will not be published. Required fields are marked *