V2V Solution!

I recently found this V2V solution when converting VMs from VMWare to Hyper-V.

The Microsoft alternative was to setup System Center, which I’ve done before and also worked great for P2V, but it requires you have an AD domain and such and this wasn’t convenient for this small lab setup.

5NINE Free Converter worked like a champ for VMs running Win2K3Server and Win2K8Server.

Minor Issues:
It took a while I think mainly due to network bandwidth limitations.
After migration, the Hyper-V didn’t have the Drives Attached.
Also the Hyper-V VM didn’t have a DVD drive Network Adapter, but these were easily fixed.


Great Window Manager for Large Monitors

Resizing, Dragging, and Positioning windows on my 30″ display seems like an archaic practice in the age of Tablets and such. And the Microsoft Snap-To functions for position windows only lets you do side-by-side (left and right side of screen). And if you’ve got 2 monitors, it’s even worse….

This utility picks up where Microsoft left off. A simple CTRL+ALT and a number on the NumPad puts your window in any of the 4 Corners, or Centered in the middle – giving you 6 spots to easily position in with a simple hot-key. Kind of awesome.



Windows Software Mirroring Recovery Lessons

DISCLAIMER: Disclaimer for anyone stumbling on this from the series-of-tubes-net…. The following steps are not exact and doing any of this could totally JACK UP YOUR SHIT, so tread with caution or CLOSE YOUR BROWSER NOW.

So it seems I have seen this more than once in my life but have to relearn how to recover each time because it just isn’t commonly google-able.  So blogging it here for my future self to reference later.

Software mirroring in Windows Server (2008 R2 for this exmaple) is great and all, but when you have a drive failure it isn’t very clear how to exactly recover.

Should the Secondary Drive (secondary plex its called) fail, it seems you will never notice it unless it happens to be making clicking noises or perhaps you diligently check your system logs for notifications of such things (I do not).

When the Primary Drive fails, it is pretty obvious – since your system won’t boot.

One would think that you simply need to open the PC and swap the SATA cables on your drives, but that doesn’t exactly work.  In my most recent case, I was getting an error from Windows Boot Manager saying that a required device was not attached to the system (Like the Failed Drive? No shit!).  Instructions followed to Boot from a Windows DVD and do a REPAIR.

Okay I thought – I’ve done this before – easy enough….Except that the Windows Server 2008R2 Repair did not see my windows installation – which posed an obvious problem.

Okay, so the Boot Manager which I think is stored on the HARD DRIVE booted up enough to notice that something was missing, but then the Windows Repair process didn’t see the Drive.

There was an option to Load Drivers and I’ve had to do that before with special RAID controllers, but this was a plain ole SATA controller and drives on-board a Dell PC class system.  No drivers to be loaded.

Just when I thought all was lost, I kept clicking around the repair options and got to a COMMAND PROMPT.  Okay this is awesome I thought – let’s go to the command prompt check out the Windows Files and try a little FIXMBR action.

Except that the command prompt didn’t see my drive either.

To cut the story short for my future self the Real Key Here to Proceed was to run the DISKPART command from the command prompt…  Next do some of these commands:

(The actual commands here may vary because I must have tried 20 different things before I got to a place that worked so use these as HINTS at best to solve your new problem):

SELECT PARTITION 3         (some crappy dell shit on partition 0 and 1 apparently – the Windows one should be obvious by the size of it)
IMPORT                 ( The partition was listed as FOREIGN so needed to Import It)
ASSIGN                 ( Assign a Drive Letter to the PARTITION )
Could be more missing steps here
BREAK                 (This command breaks the MIRROR, but it didn’t work – instead gave me an error of MISSING PLEX)
(Seriously No Shit the PLEX is missing – I wouldn’t be at this command prompt if everything was still there and working – Sheesh!)
LIST VOLUMES   (DO this to see what Drive Letter DISKPART has given your Windows Partition)

EXIT                     (Ultimately exit back to command prompt where you have the DRIVE letter showing up now)

Now back at command prompt make sure your New Drive Letter is there and you see your WINDOWS folder.

Be sure you’re on your newly found Windows Drive, J: in my case.

Now run the BOOTREC.EXE utility.
Here you can do the following:


Reboot your crap box and see if it all works.  It did for me.
Now as long as the next drive that fails isn’t on THIS WEB SERVER where my Blog is stored, I can search here and find these notes. ;)