Experiences in a Virtual World

Archive for November 2011

Vendor Spotlight: Veeam Backup & Replication v6 Released

leave a comment »

Written by VirtuallyAware

November 30, 2011 at 11:00 AM

Posted in Hyper-V

Blog Highlight: Add Possible Owner to a Cluster Shared Volume

leave a comment »

Came across this Post for an issue when adding a new node to and existing Hyper-V R2 SP1 cluster where the new node did not get added as a possible owner of the CSV disks or of the Quorum.  The presenting symptoms for me was DPMs inability to backup VMs that resided on a particular node since the ownership of the CSV could not be transferred to a node that was not allowed as a possible owner.

Running Cluster Validation returns these warnings.

(Click Picture for Larger View)



For the Quorum, the change is easy.  Just open the properties of the Quorum disk resource and on the Advanced Policies tab check the check mark next to the node to make it a Possible Owner.

(Click Picture for Larger View)


CSV disks this can be a bit more challenging however since you can not add or change the Possible Owner of a CSV from the GUI.  Luckily you can do this using the CLUSTER.EXE utility as outlined in Gustavo’s Post.

CLUSTER.EXE . RES “Cluster Disk 1″ /ADDOWNER:<nodename>

You could also use a PowerShell command to do the same thing.

  • Open PowerShell
  • Load the FailoverClusters Module
    • Import-Modules FailoverClusters
  • Run the Set-ClusterOwnerNode command:
    • Get-ClusterResource "Cluster Disk 1" | Set-ClusterOwnerNode -Owners <nodename>

Looking at the Cluster Validation report again now will show that there are no problems with incomplete disk ownership.

(Click Picture for Larger View)


Written by VirtuallyAware

November 28, 2011 at 4:15 PM

Posted in DPM, Hyper-V

Advisory Board Question of the Month: Which new server virtualization technology are you most thankful for?

leave a comment »

For the annual Thanksgiving Advisory Board question, the simple snapshot makes a repeat appearance for my Hyper-V feature I am most thankful for, but this time it is because of its new live merging capabilities in Hyper-V 3.0.


I am thankful for a Hyper-V 3.0 feature, but it’s not the flashier, increased number of virtual CPUs, the mammoth amounts of virtual machine (VM) memory, the concurrent Live Migration capabilities, or even the new VM replication feature.

Building on last year, I am thankful for the updated snapshot feature. The ability to roll back to a previous point in time after a botched application upgrade has always been a welcomed feature. But it came with a caveat: After you deleted a snapshot, you needed to shut down the VM to merge the AVHD file changes into the parent Virtual Hard Disk.

This requirement caused unwanted downtime for the application. Hyper-V 3.0 snapshots still provide the same valuable rollback method as before. But now the merging process happens live, without the necessary downtime. Thus, it eases the direct administrator interaction during application upgrades.

See the responses from the other Search Server Virtualization Advisory Board members here.

Written by VirtuallyAware

November 17, 2011 at 11:00 AM

Windows Server 8 Quick Tip: Hyper-V 3.0 Replication

leave a comment »

Came across this and thought I would share.

If you are trying to replicate a VM from one Hyper-V 3.0 host to another, you must make sure the the appropriate Network Resource Pools have been configured exactly the same on each node.  If your VM is part of a Network Resource Pool that does not exist on the replica server,  you will get the message below.




- Rob

Written by VirtuallyAware

November 11, 2011 at 2:36 PM

Posted in Hyper-V, Hyper-V 3.0

Recent Article: Overcoming Hyper-V Live Migration Limitations with PowerShell CMDLets

leave a comment »

image3With Windows Server 2008 R2, Microsoft lessened the feature gap between Hyper-V’s Live Migration and competitors’, but it still has some limitations. Thankfully, you can work around the shortcomings in Hyper-V Live Migration using Windows PowerShell cmdlets.

Hyper-V Live Migration allows admins to move a  virtual machine (VM) from one Hyper-V cluster node to another with no noticeable downtime, but some shortcomings still remain, include the inability to live migrate multiple VMs at one time, the lack of scheduling capabilities for live migration, and the inability to migrate VMs based on specific criteria. Hyper-V 3.0, slated for some time in 2012, promises to improve on Hyper-V Live Migration’s limitations, but for now, there are viable workarounds with the help of PowerShell cmdlets.

Using the PowerShell Failover Cluster cmdlet
Most large Hyper-V clustered installations implement System Center Virtual Machine Manager (SCVMM), but for organizations with only one or a few Hyper-V clusters, PowerShell cmdlets can automate and orchestrate the live migration process, while avoiding the additional cost of SCVMM. Most Windows cluster administrators are familiar with Cluster.exe for managing cluster resources, but the PowerShell Failover Cluster cmdlet can accomplish even more live migration functions.


To read the rest of the article see the scripts go HERE.

Written by VirtuallyAware

November 10, 2011 at 1:02 PM

Posted in Articles, Hyper-V


Get every new post delivered to your Inbox.

Join 328 other followers

%d bloggers like this: