Professional Documents
Culture Documents
Guest VM’s
can run Hosts are
any OS clustered
Guests are
not clustered
VS is a clustered SAN
application running
on a cluster
.VHD’s reside on
shared disk
Virtual Server Guest Clustering
Applications failover from one Guest to another
Guests run
Win2003 Guests are
clustered
Hosts are not
clustered
.VHD’s reside on
host disk
Guests are effectively iSCSI
nodes in a cluster that
access shared storage
with a NIC and the
iSCSI Software Initiator
User data resides
on shared disk
Clusters In Longhorn
What’s Clustering in Longhorn all about?
Simplicity, Security, Stability
Cluster
Command Management Fully
line Console Scriptable
(cluster.exe) with WMI
d Task Oriented
n c e Ph
d va as ing
s A s Cluster out
o e
s tion
p Op MOM Management Pack MS
Ex Clu
s
Richer Tool
Experience
Programmatic Changes
Cluster Automation Server (MSClus) is being
deprecated in Longhorn
Cluster aware applications written that take
advantage of these interfaces should use
the Cluster API or Cluster WMI provider
See the following link for more information
on Cluster Automation Server
http://msdn.microsoft.com/library/default.asp?url=/library/e
mscs/mscs/programming_with_cluster
_automation_server.asp
Service Manageability
Improved Security Model
Cluster Service now runs in the context of
the LocalSystem built-in account
No more Cluster Service Account (CSA)
No more account password management
No need to pre-stage defined
user accounts
More resilient to configuration issues
Addresses supportability issues
where privileges are accidentally
stripped by group policies
Increased security
New Security Context
How does this impact you?
Cluster Service starts with set privileges
Resource Hosting Subsystem launched in the same context
with the same privileges
Resource DLL’s and Applications are launched in the same
context of RHS with the same set of privileges
No common identity
In short, any custom resource DLL or applications leveraging the
Generic Application or Generic Script resource types will have
reduced privileges and no remote-ability
You are responsible for handling the credentials your
applications require
Test your apps and resources with Windows Server Longhorn!
Majority Quorum Model
New majority based quorum model
Majority of Nodes based quorum
Disk is optional witness to have a vote in deciding majority
No single point of failure!
Can survive loss of the witness disk
Vote Vote
SAN
OR OR
IP Address IP Address
Resource A Resource B
Windows Server Longhorn
Will Be A Clean Slate
Compatibility
Some hardware may not be upgradeable
Can not assume any solution that previously
worked with clustering will continue to work in
Longhorn Clustering
Supportability
There will be no grandfathering of support for
currently qualified solutions listed on the
Windows Server Catalog
Solutions proven to work with Win2003 Clustering means
nothing in the context of Longhorn Clustering compatibility
SCSI Command Requirements
Storage must support the following SCSI-3 SPC-3
compliant SCSI Commands:
Unique ID’s
Vital product data (VPD), device identification page (page code
83h) with Identifier Type 2 (EUI-64 based), 3 (NAA), or 8
ClusAPI
WMI
RHS.exe
CPrepSrv ClusSvc.exe ClusRes.dll
Disk Resource
C:\ F:\ User
Kernel
Volume Volume
HBA
Storage enclosure
Persistent Reservation Table
Persistent Reservation
Table in the external storage
Registration Defense Protocol
Successful defense
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Timeline in sec’s
Defender Node
Existing
Reserve
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
Timeline in sec’s
Persistent Reservation
Issued
PR IOCTL converted to
Class Driver (Disk.sys) IRP_MJ_SCSI with PR opcode
MPIO
Questions?
Send mail to:
clushelp @ microsoft.com
© 2006 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions,
it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation.
MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.