Changes in Windows cluster API
Hi,
What are the changes in Windows 2008 server failover cluster API from the Windows 2003 server cluster API? Are there any document addressing this?
Thanks, in advance for any pointers or light shed.
Answers
Hi Michelle,
In general we have made little changes to existing Cluster API’s. We have added a dozen or so new ones such as CreateCluster(), DestroyCluster(), AddClusterNode(), EvictClusterNode(), SetClusterQuorumResource(), and SetClusterResourceDependencyExpression() to name a few.
The only ones that have been completely removed are BackupClusterDatabase() and RestoreClusterDatabase(). You now need to use the new Cluster VSS Writer to perform backups and restores of the cluster configuration.
We are depricating our Cluster Automation Server (MSClus) COM interface, so none of the new API's are exposed through MSClus. http://msdn2.microsoft.com/en-us/library/aa369077.aspx MSClus will be there for Win2008, but will be removed in a future release... so I would recommend staying away from writing new code leveraging it.
In Win2008 we have full parity between our Cluster API and our WMI provider MSCluster. http://msdn2.microsoft.com/en-us/library/aa372876.aspx
We also have a new control code that will be of interest if you have a storage class resource called CLUSCTL_RESOURCE_STORAGE_GET_DISK_INFO_EX
One heads up is that we have broken backward compatability with some core protocol security enhancements. This means you can not call Cluster API's from a Win2008 Cluster to a downlevel cluster (NT4 / Win2k / Win2003). And the same you can not be on a downlevel client and remotely call Cluster API's against a Win2008 node. But this does not affect code running on a Win2008, so in general your code should just work.
And as Chuck said, you can find more info up on the MSDN link he provided.
Thanks!!
Elden Christensen
Program Manager
Windows Failover Cluster Group
Microsoft Enterprise Server Products
Of course, this posting wouldn’t be complete without a nice, juicy disclaimer from our lawyers: This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use. © 2007 Microsoft Corporation. All rights reserved.
http://www.microsoft.com/info/cpyright.htm
All Replies
Hi Michelle,
In general we have made little changes to existing Cluster API’s. We have added a dozen or so new ones such as CreateCluster(), DestroyCluster(), AddClusterNode(), EvictClusterNode(), SetClusterQuorumResource(), and SetClusterResourceDependencyExpression() to name a few.
The only ones that have been completely removed are BackupClusterDatabase() and RestoreClusterDatabase(). You now need to use the new Cluster VSS Writer to perform backups and restores of the cluster configuration.
We are depricating our Cluster Automation Server (MSClus) COM interface, so none of the new API's are exposed through MSClus. http://msdn2.microsoft.com/en-us/library/aa369077.aspx MSClus will be there for Win2008, but will be removed in a future release... so I would recommend staying away from writing new code leveraging it.
In Win2008 we have full parity between our Cluster API and our WMI provider MSCluster. http://msdn2.microsoft.com/en-us/library/aa372876.aspx
We also have a new control code that will be of interest if you have a storage class resource called CLUSCTL_RESOURCE_STORAGE_GET_DISK_INFO_EX
One heads up is that we have broken backward compatability with some core protocol security enhancements. This means you can not call Cluster API's from a Win2008 Cluster to a downlevel cluster (NT4 / Win2k / Win2003). And the same you can not be on a downlevel client and remotely call Cluster API's against a Win2008 node. But this does not affect code running on a Win2008, so in general your code should just work.
And as Chuck said, you can find more info up on the MSDN link he provided.
Thanks!!
Elden Christensen
Program Manager
Windows Failover Cluster Group
Microsoft Enterprise Server Products
Of course, this posting wouldn’t be complete without a nice, juicy disclaimer from our lawyers: This posting is provided "AS IS" with no warranties, and confers no rights. You assume all risk for your use. © 2007 Microsoft Corporation. All rights reserved.
http://www.microsoft.com/info/cpyright.htmThanks, Elden and Chuck. This is very much appreciated!