CSV stuck in Redirected Access/Backup in progress after a faulty backup job


If you follow the step detailed in http://blogs.technet.com/b/askcore/archive/2010/12/16/troubleshooting-redirected-access-on-a-cluster-shared-volume-csv.aspx, about deleting shadows and get:


> delete shadows /all

Error: Shapshots were found, but they were outside of your allowed context.

Try with:


DISKSHADOW> delete shadows all

Number of shadow copies deleted: 1




Hyper-V Update List

First time you implement Hyper-V a question pop-ups, what are the hotfixes needed for Hyper-V? Besides KB950050 that is required to bring your Hyper-V to the RTM version, there are serveral updates that might apply to your environment. This url has the “live” list of updates:


Cloning Linux guests on Hyper-V

Most of the current linux distros use UDEV to map NIC to names (like eth0), that is based on MAC or PCI Ids. When you clone a virtual machine in Hyper-V, you’ll get a new PCI ID and MAC Address, so a new name will be assigned.

The easy way to fix this issue is editing /etc/udev/rules.d/z25_persistent-net.rules
Original (Debian 4.0):
SUBSYSTEM=="net", DRIVERS="?*", ATTR{address}=="00:11:22:33:44:55", NAME="eth0"
SUBSYSTEM=="net", DRIVERS="?*", ATTR{address}=="00:11:22:33:44:56", NAME="eth1"

<remove first entry>
SUBSYSTEM=="net", DRIVERS="?*", ATTR{address}=="00:11:22:33:44:56", NAME="eth0"
So MAC ending in :55 was the NIC in the original install, and the one ending in :56 is the NIC on the cloned VM; now mapped to eth0 as one could expect.

Windows Vista/2008 full mouse support on Hyper-V

If you migrate a VM with Vista or 2008 from Virtual Server, you don’t get full mouse support even when you install Integration Services. By full mouse support, I mean to be able to use mouse from a RDP session connected to the Hyper-V host. You’ll get “Mouse not captured in Remote Desktop Session”.

The solution that I found is adding more than 1 CPU to the virtual machine, and activate detect HAL option. More details in my previous post: https://folgaizer.wordpress.com/2008/07/17/migrating-windows-server-2008-guests-from-virtual-server-to-hyper-v/

Migrating Windows server 2008 guests from Virtual Server to Hyper-V

Virtual server is limited to one CPU per VM. When you go to Hyper-V, it’s posible to use up to 4 virtual CPU inside each VM.

To be able to use more than one CPU you have to change from uni-processor hal to multiprocessor hal. So far I could research this change is not well documented for Windows Server 2008. Here it is:

Execute MSConfig, and then go to tab Boot -> Advanced Options…, check option “Detect Hal”, restart to these options take effect.

Or using command line:

bcdedit /set detecthal yes