Posts Tagged ‘Failover Clustering’

Post SP1 Hotfixes for Windows 2008 R2 SP1 with Failover Clustering and Hyper-V

August 3, 2011

In addition to my previous blog around the list of recommended hotfixes for SCVMM, Hyper-V and Failover Clustering, I do personally maintain currently a list with all post (recommended/required/regular….) SP1 released hotfixes especially with focus on Failover Cluster and Hyper-V:

http://ramazancan.wordpress.com/2010/11/21/recommended-hotfixes-scvmm-hyper-v/

KB2528357 – Nonpaged pool leak when you disable and enable some storage controllers in Windows 7 or in Windows Server 2008 R2
http://support.microsoft.com/kb/2528357

KB2568088 – Virtual machine does not start on a computer that has an AMD CPU that supports the AVX feature and that is running Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2568088

KB2547551 – Hyper-V Export function consumes all available memory in Windows Server 2008 or in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2547551

KB2550569 – "0×20001" Stop error when you start a Linux VM in Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2550569

KB2504962 – Dynamic Memory allocation in a Virtual Machine does not change although there is available memory on the host
http://support.microsoft.com/kb/2504962

KB2534356 – Some CPU cores are parked while other active CPU cores have a heavy workload in Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2534356

KB2496034 – Cluster service stops when an error occurs in the registry replication process of a failover cluster in Windows Server 2008 R2 (SP1) or in Windows Server 2008
http://support.microsoft.com/kb/2496034

KB2549448 – Cluster service still uses the default time-out value after you configure the regroup time-out setting in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2549448

KB2549472 – Cluster node cannot rejoin the cluster after the node is restarted or removed from the cluster in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2549472

KB2446607 – You cannot enable BitLocker on a disk volume in Windows Server 2008 R2 (SP1) if the computer is a failover cluster node
http://support.microsoft.com/kb/2446607

KB2462576 – The NFS share cannot be brought online in Windows Server 2008 R2 (SP1) when you try to create the NFS share as a cluster resource on a third-party storage disk
http://support.microsoft.com/kb/2462576

KB2485543 – You cannot access or mount a Windows Server 2008 R2 (SP1) based NFS share after a failover if the NFS share uses Krb5 or Krb5i authentication
http://support.microsoft.com/kb/2485543

KB2545685 – Recommended hotfixes and updates for Windows Server 2008 R2 SP1 Failover Clusters
http://support.microsoft.com/kb/2545685

KB2531907 – Validate SCSI Device Vital Product Data (VPD) test fails after you install Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2531907

KB2494162 – The Cluster service stops unexpectedly on a Windows Server 2008 R2 (SP1) failover cluster node when you perform multiple backup operations in parallel on a cluster shared volume
http://support.microsoft.com/kb/2494162

KB2552040 – A Windows Server 2008 R2 (SP1) failover cluster loses quorum when an asymmetric communication failure occurs
http://support.microsoft.com/kb/2552040

KB2494036 – A hotfix is available to let you configure a cluster node that does not have quorum votes in Windows Server 2008 and in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2494036

KB2496089 – The Hyper-V Virtual Machine Management service stops responding intermittently when the service is stopped in Windows Server 2008 R2
http://support.microsoft.com/kb/2496089

KB2521220 – "0x0000001E" Stop error when you perform disk I/O-intensive operations on dynamic disks in Windows Server 2008 or in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2521220

KB2512715 – Validate Operating System Installation Option test may identify Windows Server 2008 R2 Server Core installation type incorrectly in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2512715

KB2501763 – Read-only pass-through disk after you add the disk to a highly available VM in a Windows Server 2008 R2 SP1 failover cluster
http://support.microsoft.com/kb/2501763

KB2520235 – "0x0000009E" Stop error when you add an extra storage disk to a failover cluster in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2520235

KB2529956 – Windows Server 2008 R2 (SP1) installation may hang if more than 64 logical processors are active
http://support.microsoft.com/kb/2529956

KB2545227 – Event ID 10 is logged in the Application log after you install Service Pack 1 for Windows 7 or Windows Server 2008 R2
http://support.microsoft.com/kb/2545227

KB2517329 – Performance decreases in Windows Server 2008 R2 (SP1) when the Hyper-V role is installed on a computer that uses Intel Westmere or Sandy Bridge processors
http://support.microsoft.com/kb/2517329/en-us

KB2532917 – Hyper-V Virtual Machines Exhibit Slow Startup and Shutdown
http://support.microsoft.com/kb/2532917

KB2494016 – Stop error 0x0000007a occurs on a virtual machine that is running on a Windows Server 2008 R2-based failover cluster with a cluster shared volume, and the state of the CSV is switched to redirected access
http://support.microsoft.com/kb/2494016/en-us

KB2263829 – The network connection of a running Hyper-V virtual machine may be lost under heavy outgoing network traffic on a computer that is running Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2263829/en-us

KB2485986 – An update is available for Hyper-V Best Practices Analyzer for Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2485986/en-us

KB2494162 – The Cluster service stops unexpectedly on a Windows Server 2008 R2 (SP1) failover cluster node when you perform multiple backup operations in parallel on a cluster shared volume
http://support.microsoft.com/kb/2494162/en-us

KB2521348 – A virtual machine online backup fails in Windows Server 2008 R2 (SP1) when the SAN policy is set to "Offline All"
http://support.microsoft.com/kb/2521348

KB2519736 – Stop error message in Windows Server 2008 R2 SP1 or in Windows 7 SP1: "STOP: 0x0000007F"
http://support.microsoft.com/kb/2519736

KB980915 – A long time delay occurs when you reconnect an IPSec connection from a computer that is running Windows Server 2003, Windows Vista, Windows Server 2008, Windows 7, or Windows Server 2008 R2 (SP1) (in IPSEC scenarios)
http://support.microsoft.com/kb/980915

RemoteFX specific:

KB2501816 – "Display driver stopped responding but has recovered" error in a Windows 7 SP1-based VM that has a RemoteFX video adapter
http://support.microsoft.com/kb/2501816

KB2505030 – A RemoteFX VM does not start, and you receive the error "Microsoft Synthetic 3D Display Controller: Failed to Power on" when you try to add the RemoteFX 3D Video adapter from Hyper-V settings
http://support.microsoft.com/kb/2505030

KB2506391 – In Windows Server 2008 R2 SP1, RemoteFX virtual machines cannot start, and you receive an error: "Failed to Power on with Error ‘Insufficient system resources exist to complete the requested service’"
http://support.microsoft.com/kb/2506391

KB2505694 – Error message when you try to start a RemoteFX-enabled virtual machine: "Microsoft Synthetic 3D Display Controller : Failed to Power on with Error ‘Insufficient system resources exist to complete the requested service’"
http://support.microsoft.com/kb/2505694

KB2506417 – New and existing RemoteFX-enabled virtual machines do not start on a domain controller that is running the Remote Desktop Virtualization Host service in Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2506417

KB2506434 – In Windows Server 2008 R2 SP1, RemoteFX VMs cannot start if the Hyper-V server display adapter has been changed
http://support.microsoft.com/kb/2506434

KB2519946 – Timeout Detection and Recovery (TDR) randomly occurs in a virtual machine that uses the RemoteFX feature in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2519946

KB2523676 – GPU is not accessed leads to some VMs that use the RemoteFX feature to not start in Windows Server 2008 R2 SP1
http://support.microsoft.com/kb/2523676

KB2533362 – Hyper-V settings hang after installing RemoteFX on Windows 2008 R2 SP1
http://support.microsoft.com/kb/2533362

MPIO specific:

KB2277904 – You cannot access an MPIO-controlled storage device in Windows Server 2008 R2 (SP1) after you send the "IOCTL_MPIO_PASS_THROUGH_PATH_DIRECT" control code that has an invalid MPIO path ID
http://support.microsoft.com/kb/2277904

KB2406705 – Some I/O requests to a storage device fail on a fault-tolerant system that is running Windows Server 2008 or Windows Server 2008 R2 (SP1) when you perform a surprise removal of one path to the storage device
http://support.microsoft.com/kb/2406705

KB2460971 – MPIO failover fails on a computer that is running Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2460971

KB2511962 – "0x000000D1" Stop error occurs in the Mpio.sys driver in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2511962

KB2522766 – The MPIO driver fails over all paths incorrectly when a transient single failure occurs in Windows Server 2008 or in Windows Server 2008 R2 (SP1)
http://support.microsoft.com/kb/2522766/

Thanks to Alex K. for the MPIO part…..Winking smile

Please let me know if I have missed any KB here.

PS: KB2496089 is already included in SP1 –> Hotfixes and Security Updates included in Windows 7 and Windows Server 2008 R2 Service Pack 1.xls

Stay tuned….. Smile

Regards

Ramazan

Every 20 min an Event 1069 and 1558?

May 15, 2011

DISCLAIMER: Event 1069 is an generic event therefore you should check and decide by your own if this blog post is an possible solution for your scenario and environment. This can be verified in the cluster logs when you identify "‘Failed to create cluster directory on witness”! which is generated by Quorum Agent.

Problem:

In a customer scenario we had identified every 20 min the events 1069 and 1558. They had pointed to quorum disk issues which we could not confirm in the 1st step as the disk was online and could be failed over to other nodes without any issues.

Event ID 1069 — Clustered Service or Application Availability
http://technet.microsoft.com/en-us/library/cc756225(WS.10).aspx

Event ID 1558 — Cluster Witness Functionality
http://technet.microsoft.com/en-us/library/dd353960(WS.10).aspx

After digging deeper and doing an cluster log analyses I had found an very interesting pointer there:

ERR mscs::QuorumAgent::PostOnline: ERROR_PATH_NOT_FOUND(3)’ because of ‘Failed to create cluster directory on witness, path \\?\Volume{5c65f7b0-15e4-11e0-b316-002655db949a}\Cluster

This tells me, that the cluster services has issues when trying to access the quorum disk when “he” want to write his cluster hive (=configuration) to the quorum disk.

As the cluster hive is “redundantly” available on each in the cluster and can also be manually created anytime when changing the cluster quorum configuration in your cluster, I used this scenario for troubleshooting my issue here.

Solution:

1. Changing the Quorum Modell temporary to “Node Majority” so that I can remove the Quorum Disk “Q:” from the cluster (Note: When changing quorum model, be aware of the available “votes” (keep majority) in your cluster)

image

image

2. Remove Quorum Disk from Cluster , Re-Format with NTFS and back to Cluster

3. Restore Quorum model – in my case “Node und Disk Majority” and point to new-formatted Quorum disk Q:

image

Result:: Die Cluster Hive is newly created on Quorum Disk Q:\

image

After the cluster hive is successfully created from cluster service, all entries in cluster logs and also events 1069 and 1558 are gone Winking smile

Information:

General Information’s around Cluster Logs can be found here:

How to create the cluster.log in Windows Server 2008 Failover Clustering
http://blogs.msdn.com/b/clustering/archive/2008/09/24/8962934.aspx

Troubleshooting Cluster Logs 101 – Why did the resources failover to the other node?
http://blogs.technet.com/b/askcore/archive/2008/02/06/troubleshooting-cluster-logs-101-why-did-the-resources-failover-to-the-other-node.aspx

Introduction to Cluster Diagnostics and Verification Tool for Exchange Administrators
http://technet.microsoft.com/en-us/library/aa996161(EXCHG.65).aspx

….wish you good luck with “troubleshooting” clip_image010

Best Regards

Ramazan

How to configure Windows NLB in (HA) Virtual Machines based on Hyper-V?

March 31, 2011

Here is some useful content when deploying Windows Network Load Balancing “NLB” within your Virtual Machines, especially when they are clustered and highly available.

To be able to use Windows NLB (Network Load Balancing) within Virtual Machines – based on Hyper-V – you must enable “Enable spoofing of MAC addresses”. For getting more details around the reason for this and the configuration please check out the following cluster team blog post:

Deploying Network Load Balancing (NLB) and Virtual Machines on Windows Server 2008 R2
http://blogs.msdn.com/b/clustering/archive/2010/07/01/10033544.aspx

Due to the fact that I see very often the issue, that NLB nodes (VM) does loose their “Enable spoofing of MAC addresses” setting after they are migrated to an different node in a failover cluster environment, I want to remember again, that you always should/must use Failover Cluster console when you changing any VM settings. otherwise the cluster service is not aware of your changes and those will not be migrated to the next node during next move.

Refresh the Configuration of a Virtual Machine
http://technet.microsoft.com/en-us/library/dd759135.aspx

PS Example:

Import-Module FailoverClusters

Update-ClusterVirtualMachineConfiguration –name “VMNAME”

NOTE: within your VMs, If you face issues with NLB like a.e. does not converge as expected or BSOD with an “STOP: 0x000000E1 (parameter1, parameter2, parameter3, parameter4)”, please checkout KB953828

Windows Server 2008 Hyper-V virtual machines generate a Stop error when NLB is configured or when the NLB cluster does not converge as expected
http://support.microsoft.com/kb/953828/en-us

Stay tuned…. Winking smile

Regards

Ramazan

Hyper-V Failover Cluster–Step-by-Step Guide Rolling Upgrade SP1

March 7, 2011

With SP1 for Windows 2008 R2 / Windows 7 there are great benefits – which I personally think is a must for test/lab/prod environments – included like RemoteFX and Dynamic Memory.In this blog post I would like to show an step-by-step guide for doing an rolling upgrade within your failover cluster.

Failover Clustering generally has always supported mixed version interoperability of service pack and QFE versions to enable Rolling Upgrades of incremental updates.

You can also set your cluster node with SCVMM in maintenance mode or you move all resources off from the 1st node which will be at first installed with Servicepack1.

image

just to confirm, that my cluster node hasn’t installed SP1 yet … Smile 

When you downloaded SP1 and moved all your resources to remaining nodes, you can start with the installation of SP1 on your cluster node:

clip_image001

clip_image002

clip_image003

Note: Unchecked to prevent automatic restart of cluster node :-)

clip_image004

clip_image005

clip_image006

……and finally

image

After you restart your node, the cluster node will automatically re-join to your cluster! The servicepack level of the upgraded host should be detected from the cluster service and also the new Hyper-V features like dynamic memory are now configurable from the Hyper-V/FC console:

image

image

image

Now you can failover your cluster resources (a.e. VM) back to your newly upgrade SP1 node and re-run the same steps on remaining nodes. All migration types can be used here (mixed SP level) – even Live Migration will work here. The VM memory settings will stay same, previous memory setting will “migrated” and DM will not be used unless you configure it dedicated per VM base.

image

Before you directly enable DM here there are some additional work to be done…..if a supported guest OS, update IC’s…..

Finally you need to update the Integration Components from the Highly Available Virtual Machines to be able to use the new Dynamic Memory feature. Of course this can also be automated with with Powershell Winking smile

After upgrading successfully the ICs you should see an new installed system device “Virtual Dynamic Memory” in device manager from your VM which takes care of the memory operations:

image

image

image

image

VM Guest OS requirements are given and listed here:

Guest operating system

Editions

Configuration requirements

Windows Server 2008 R2

Standard and Web editions

Install SP1 in the guest operating system.

Windows Server 2008 R2

Enterprise and Datacenter editions

Do one of the following:

· Install SP1 in the guest operating system.

· Upgrade the integration services in the guest operating system to the SP 1 version.

clip_image001Note

Installing SP1 is the recommended method because it provides the added benefit of installing all updates included with SP1.

Windows 7

Ultimate and Enterprise editions (32-bit and 64-bit)

Do one of the following:

· Install SP1 in the guest operating system.

· Install the SP1 version of integration services in the guest operating system.

clip_image001[1]Note

Installing SP1 is the recommended method because it provides the added benefit of installing all updates included with SP1.

Windows Server 2008 with Service Pack 2 (SP2)

Standard and Web editions (32-bit and 64-bit)

Upgrade the integration services in the guest operating system to the SP1 version.

Apply a hotfix as described in article 2230887 (http://go.microsoft.com/fwlink/?LinkId=206472).

Windows Server 2008 with Service Pack 2 (SP2)

Enterprise and Datacenter editions (32-bit and 64-bit)

Upgrade the integration services in the guest operating system to the SP1 version.

Windows Vista with Service Pack 1 (SP1)

Ultimate and Enterprise editions (32-bit and 64-bit)

Upgrade the integration services in the guest operating system to the SP 1 version.

Windows Server 2003 R2 with Service Pack 2 (SP2)

Standard, Web, Enterprise, and Datacenter editions (32-bit and 64-bit)

Upgrade the integration services in the guest operating system to the SP1 version.

Windows Server 2003 with Service Pack 2

Standard, Web, Enterprise, and Datacenter editions (32-bit and 64-bit)

Upgrade the integration services in the guest operating system to the SP1 version.

from DM Deployment Guide TechNet Reference

Further details for Dynamic Memory configuration in your Hyper-V environment can be found here:

Dynamic Memory Configuration Guide:
http://technet.microsoft.com/en-us/library/ff817651(WS.10).aspx

Re-Validation required?

I personally think here, in production environments an re-validation is required as we have here an servicepack level change at our node and any “major” changes – which are documented in the following articles – “should/must” be re-validated in your failover cluster environment:

Failover Cluster Step-by-Step Guide: Validating Hardware for a Failover Cluster
http://technet.microsoft.com/en-us/library/cc732035(WS.10).aspx

Understanding Cluster Validation Tests
http://technet.microsoft.com/en-us/library/cc726064.aspx

There are some documented scenarios when a re-validation is required within your failover cluster – see especially section “Operating System” changes for our “Upgrade SP1” scenario:

image

in our cause with the SP1 installation we need re-validate our cluster with a “Single-LUN” test scenario. The test scenarios, or here called categories, in validation here are also described in the same article:

Categories of validation test scenarios are:

  • Full: The complete set of tests. This requires some cluster downtime
  • Single LUN: The complete set of tests, where you run the storage tests on only one LUN. The LUN might be a small LUN that you set aside for testing purposes, or the witness disk (if your cluster uses a witness disk). This validates the storage subsystem, but not specifically each individual LUN or disk. You can run these validation tests without causing downtime to your clustered services or applications
  • Omit storage tests: The system configuration, inventory, and network tests, but not the storage tests. You can run these validation tests without causing downtime to your clustered services or applications
  • None: No validation tests are needed

General considerations when running validation against an productive cluster which serves real workloads are of course given here but there is some useful documentation which covers exactly this scenario here:

http://technet.microsoft.com/en-us/library/cc732035(WS.10).aspx#BKMK_considerations

In my case, I had added a new (small 1GB) LUN only for storage validation testing purposes:

image

After I updated (and validated+passedSmile) all cluster nodes with SP1, I’m now ready for using new features like Dynamic Memory and/or RemoteFX for high-end graphic emulation within my virtual machines – of course in case of RemoteFX, hardware changes are required to support this (Server Graphic Card, SLAT…) but that is a other “story” which I will cover soon in a separate post.

Further useful documentation in this topic can be found here:

Hardware Requirements for RemoteFX
http://technet.microsoft.com/de-de/library/ff817602(WS.10).aspx

Windows 2008 R2 / Windows 7 Service Pack 1 Download:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=c3202ce6-4056-4059-8a1b-3a9b77cdfdda

Knowledgebase Article – KB976932 – around Service Pack 1:
http://support.microsoft.com/kb/976932/en-us

Stay tuned…. Winking smile

Regards

Ramazan

Common Cluster Property – ShutdownTimeoutInMinutes

February 4, 2011

When you initiate an shutdown on a failover cluster node the cluster service issues an offline/failover of the owned cluster groups. in case of virtual machines it would initiate an quick migration to next configured node.The timeout values can be controlled in R2 clusters:

This property is also exposed as the ShutdownTimeoutInMinutes property of the MSCluster_Cluster WMI class.

Note  If the Hyper-V role is installed, the default time-out value is calculated based on the size of physical memory, using a ratio of 100 minutes / 64 GB. The minimum computed value is 20 minutes

http://msdn.microsoft.com/en-us/library/ee342507(v=VS.85).aspx

This is only applicable for Windows 2008 R2 failover clusters!

Stay tuned… Winking smile

Regards

Ramazan

Microsoft TechDay Online–Webcast und Expertenchat

February 2, 2011

Microsoft veranstaltet zwischen dem 21.02.- und 23.02.2011 die Techdays Online welche Themengebiete wie z.b. Hochverfügbarkeit, Virtualisierung, Cloud Management beinhalten wird. Dabei werden wirkliche sehr interessante Webcast zur Verfügung stehen.

“Der Microsoft TechDay bietet seit annähernd 3 Jahren geballtes Wissen rund um die neuesten Microsoft-Technologien. Egal ob Sie IT-Führungskraft, technischer Entscheider oder Administrator sind – bei uns erhalten Sie Informationen aus erster Hand!
Wir freuen uns, Ihnen neben den ursprünglichen Offline-Events seit neuestem auch den Microsoft TechDay Online anbieten zu können. Bei diesem Online-Event können Sie die Vorträge live oder auch on Demand anschauen und in unserem Expertenchat offen gebliebene Fragen klären. Unsere Offline-Events ganz in Ihrer Nähe behalten wir natürlich weiterhin bei.“

Dabei habe ich ebenfalls die Möglichkeit erhalten, meine bisherigen Erfahrungen in Bezug auf die täglichen Herausforderungen für den Datacenter Administrator, in einem Webcast zu komprimieren. Mein Track zu diesem Thema wird heissen “Virtualisierung für den Administrator: Die täglichen Aufgaben für Optimierung und Verfügbarkeit”

Weitere Informationen zu TechDay Online ist zu finden unter:

http://www.techday.ms/default.aspx

Agenda für Virtualisierung

http://www.techday.ms/Virtualisierung/agenda.aspx

Anmeldung

http://www.techday.ms/Virtualisierung/anmeldung.aspx

Stay tuned… Winking smile

Ramazan

Microsoft Windows Failover Cluster–VM Failover Policies

January 20, 2011

I’m very often asked or have seen confusion around the configuration option’s and possibilities for an “load balancing control mechanism” for highly available virtual machines within a failover cluster environment.

a.e. which VMs should run “preferred” (-> preferred owner) on dedicated node(s) or at the other side you want to control which VMs should never run together at 1 node (-> AntiAffinityClassNames).

a.e. from node/host capacity planning perspective you’re also able to configure on which node(s) your VM(s) can be failed over (-> Possible Owners)

In combination all of these parameters (AntiAffinityClassNames, Possible Owner, Preferred Owner….) you can configure a very well “balanced” environment to get the best performance for your VMs/Applications and a well utilized server hardware.

Interested? here we go::

Failover Cluster – WMI MSCluster_ResourceGroup Class
http://msdn.microsoft.com/en-us/library/aa371465(v=vs.85).aspx

How to configure Windows clustering groups for hot spare support
http://support.microsoft.com/kb/296799

Failover behavior on clusters of three or more nodes
http://support.microsoft.com/?kbid=299631

Windows Server 2008 R2 Failover Cluster PowerShell Command Reference
http://social.technet.microsoft.com/wiki/contents/articles/windows-server-2008-r2-failover-cluster-powershell-command-reference.aspx

Controlling Server Workload in MSCS Clusters (2003)
http://technet.microsoft.com/es-es/library/cc776607(d=lightweight,v=WS.10).aspx

In addition Elden Christensen (Senior PM for Cluster, Microsoft) has written an great blog around failover policies for Virtual Machines in Failover Cluster environments:

Understanding Hyper-V Virtual Machine (VM) Failover Policies
http://blogs.msdn.com/b/clustering/archive/2010/12/14/10104402.aspx

Any further questions? let me know….

Stay tuned for further blogs around failover policiesWinking smile

Best Regards

Ramazan

Recommended Hotfixes – Failover Cluster, SCVMM, Hyper-V

November 21, 2010

Here is a list of technet/KB articles where you can find a summary of the recommended patches around Hyper-V (R2) and SCVMM (R2).

Hyper-V Update List for Windows Server 2008
http://technet.microsoft.com/en-us/library/dd430893(WS.10).aspx

Hyper-V Update List for Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ff394763(WS.10).aspx

Recommended hotfixes for System Center Virtual Machine Manager 2008 R2
http://support.microsoft.com/kb/2397711

Recommended hotfixes for Windows Server 2008-based server clusters
http://support.microsoft.com/kb/957311

Stay tuned… Winking smile

Ramazan

TechEd 2010 in Berlin and Offline Sessions around Clustering, Hyper-V…

November 21, 2010

personally I was invited from Microsoft to be an MVP Cluster expert at the TechEd 2010 in Berlin and it was a pleasure for me to represent clustering and HA technologies at TechEd 2010. Mainly we had supported the Failover Clustering booth in 3.2 hall at the TLC (Technical Learning Center) and answered all your interesting questions.

I want to thank for all the interesting discussion’s with you guys and here I would like to share some of the great sessions around failover clustering, Hyper-V and generally high availability which you possibly have missed:

Failover Clustering & Hyper-V: Planning your Highly-Available Virtualization Environment
http://www.msteched.com/2010/Europe/WSV403

Failover Clustering in 2008 R2: What’s New in the #1 High-Availability Solution
http://www.msteched.com/2010/Europe/WSV313

Hyper-V and Dynamic Memory in Depth
http://www.msteched.com/2010/NorthAmerica/VIR304

Hyper-V Backup Deep Dive: A Look Under the Hood
http://www.msteched.com/2010/NorthAmerica/VIR322

Advanced Storage Infrastructure Best Practices to Enable Ultimate Hyper-V Scalability
http://www.msteched.com/2010/NorthAmerica/VIR207

Disaster Recovery by Stretching Hyper-V Clusters across Sites
http://www.msteched.com/2010/NorthAmerica/VIR303

Networking and Windows Server 2008 R2 Hyper-V: Deployment Considerations
http://www.msteched.com/2010/NorthAmerica/VIR310

Hyper-V Live Migration over Distance: A Multi-Datacenter Approach
http://www.msteched.com/2010/NorthAmerica/VIR323

Windows Server 2008 R2 Hyper-V Performance Analysis: How You Can Get the Most out of Hyper-V
http://www.msteched.com/2010/NorthAmerica/VIR315

Microsoft RemoteFX Deep Dive: Rich Media Desktop and USB Device Support
http://www.msteched.com/2010/Europe/WSV310

Failover Clustering Pro Troubleshooting with Windows Server 2008 R2
http://www.msteched.com/2010/NorthAmerica/WSV314

Windows Server 2008 R2 and Microsoft SQL Server 2008: Failover Clustering Implementations
http://www.msteched.com/2010/NorthAmerica/DAT407

Failover Clustering Deployment Success
http://www.msteched.com/2010/NorthAmerica/WSV313

All You Needed to Know about Microsoft SQL Server 2008 Failover Clustering
http://www.msteched.com/2009/Europe/DAT312

Innovating High Availability with Cluster Shared Volumes
http://www.msteched.com/2009/NorthAmerica/WSV313

Multi-Site Clustering with Windows Server 2008 R2
http://www.msteched.com/2009/Europe/SVR319

The Case of the Unexplained, 2010: Troubleshooting with Mark Russinovich
http://www.msteched.com/2010/NorthAmerica/WCL315

Mysteries of Windows Memory Management Revealed with Mark Russinovich, Part 1
http://www.msteched.com/2010/Europe/WCL401

Mysteries of Windows Memory Management Revealed with Mark Russinovich, Part 2
http://www.msteched.com/2010/Europe/WCL402

Pushing the Limits of Windows with Mark Russinovich
http://www.msteched.com/2010/NorthAmerica/WCL402

Many many other interesting sessions can be found at TechEd Online –> http://www.msteched.com/ 

I personally would like to recommended you the sessions from Mark Russinovich and of course all Clustering sessions from Symon Perriman (Program Manager Clustering @ Microsoft).

Stay tuned….Winking smile

Regards

Ramazan Can

Failover Cluster – CSV – Netzwerk Protokoll Konfiguration

June 17, 2010

Einer der “meisten” Fehler, was ich immer wieder bei Kunden Problemen gesehen habe ist, das die Netzwerk Protokolle "File and Printer Sharing " und  "Client for MS Networks" von den Cluster “Internal” Netzwerken (wie z.b. Live Migration, CSV, Cluster Kommunikation….) deinstalliert oder deaktiviert werden.

image

Dies war unter Windows 2003 Cluster (MSCS) noch eine sogenannte “Best Practice”, die “nicht” benötigten Protokolle vom “Heartbeat” Netzwerk Adaptern zu deinstallieren.

Seit Windows 2008 R2 Failover Clustering ist es sogar wichtig, dass die Netzwerk Protokolle “"File and Printer sharing" und  "Client for MS networks" installiert und aktiviert sind, damit z.b. eine erfolgreiche Live Migration durchgeführt werden kann oder eine erfolgreiche CSV Kommunikation aufgebaut werden kann.

Ansonsten kann dies zu unterschiedlichen Fehler produzieren, eine davon ist auch, das CSV Volume(s) von den anderen Knoten via SMB nicht erreicht werden kann –> siehe KB2008795.

http://support.microsoft.com/kb/2008795

Stay tuned…. Winking smile

Ramazan


Follow

Get every new post delivered to your Inbox.

Join 49 other followers