Backup Exec 2010 Hyper-V GRT Issue

So I recently fired up a few new virtual machines in my 2008 R2 Hyper-V cluster for a new project I’m working on. Got everything up and running and set up the new VMs on a backup schedule in Backup Exec. The next morning I went to check to make sure the backups happened correctly, and was greeted with this error:

V-79-57344-38721 – Failed to mount one or more virtual disk images

So the VMs backed up, but the GRT (granular restore) portion of the backup failed, and I wouldn’t be able to recover individual files from the VMs. Searching through Symantec’s KB articles was less than useful (as it often is) so it seemed I had to figure this out myself.

I went over everything I did and didn’t come up with any variation on my normal procedure for creating VMs. However, I realized that these are the first VMs I had created since I upgraded to SCVMM 2012 SP1 from 2008 R2, so perhaps something changed there. I do know that if you’re creating a VM in a cluster, you no longer get prompted to make it highly available, that’s now a checkbox, and if you forget it, the VM creation fails, so that seemed like a good place to start. Well, after checking Event Viewer logs, which were of no help.

So I stepped through the process of creating a new VM in SCVMM paying very close attention at each screen to see if there may have been something I missed. Everything looked good until I got to the Configure Settings portion of the wizard, and I noticed that the vhd files no longer get placed in the same folder as the configuration files by default, they were going to the default storage location for the server they were being created on. So I checked there, and SCVMM had created a VMMDisks folder and all the vhd files for the new VMs were there.

Well, there was something different. So using the Migrate Storage option, I moved the vhd files for one of the VMs back into the folder where the configuration files were and reran the backup job. And no more GRT error.

So it would appear that Backup Exec 2010 R3 is not capable of doing a Hyper-V GRT backup if the vhd files reside in a folder other than where the configuration files are. I’ll just have to make sure I’m manually setting them up in the right place going forward.

I’m Going to TechEd!

I got approval this week to once again attend Microsoft TechEd. This year it will be held in New Orleans June 3-6 (I still wish they’d go back to the five-day format, I liked having that extra day to get more sessions in). There isn’t much happening on the TechEd site right now other than registration related items and a link to the Channel 9 forums which you’ll miss if you don’t check the footer.

Hopefully they’ll have a schedule builder up soon, and some handy blog decorations I can use now that I actually have one to decorate. In the meantime, I installed a countdown timer in the sidebar.

More info to come as it becomes available.

Fixing Windows 8 Trackpad Driver in Bootcamp

Another issue I have had with Windows 8 in Bootcamp on a Mac is that the trackpad drivers did not initially install correctly and I wasn’t able to use it at all. I was able to solve that by following these steps.

Go to Device Manager and on the two “Touchpad” entries with the bang on them, go to “Update Driver” -> “Browse My Computer” -> “Let me pick from a list…” and change them both to USB Input Device. Reboot.

Go back to Device Manager, do an “Update Driver” again, let it search automatically, and one comes back as Apple Multitouch and the other as Apple Multitouch Mouse. Reboot again, trackpad will be working and will show up in Boot Camp control panel.

Fixing Windows 8 Wifi Issues in Bootcamp

I’m not a fan of OSX, but working at an advertising agency, there’s no way to avoid it. I have a MacBook Pro that I need to use to admin some Mac things occasionally. The rest of the time, it runs Windows very nicely using Bootcamp.

However, when Windows 8 came out and I scrapped my Windows 7 partition and installed Windows 8 Enterprise, I found that I could no longer attach to our corporate wifi network. We use 802.1x and certificates to authenticate via radius, so I checked the radius server and determined that I wasn’t even making it that far, there was no indication of my machine even trying to authenticate. I figured it probably wasn’t a Cisco wireless issue, since my machine was the only one having a problem. What next then?

I checked the driver, and the Broadcom 802.11n wireless card was using the built in Microsoft driver. Which was working fine as long as you didn’t have to use certificates. I had no problem connecting at home, or at Starbucks and the like.

I decided I’d try using some older Broadcom drivers to see if that would remedy the situation. Installing those did the trick. You can download the Broadcom driver I used here. Don’t use the Setup.exe, it won’t run. Go through Device Manager and manually install the driver that way.