Month: December 2015
Task Manager Freezes on Windows 8/Server 2012
Reading Time: 2 minutesI’m the kind of guy that ALWAYS has task manager open. I’m serious, ask anyone I work with — I sometimes even have a whole screen for Task Manager and Resource Monitor (Maybe that’s why I like SCOM so much?). Though, I’ve noticed a couple of times on Windows 8, Windows 8.1, Server 2012, Server 2012 R2 that when I open task manager the stats just freeze. The system is fine, everything is normal but the stats just freeze — like this.
They never do anything else, and just stay at that initial opening mark. So frustrating! I’ve SFC’d, I’ve rebuilt my performance library, I’ve copied new bits for taskmgr.exe, everything! It turns out for some reason sometimes the view speed gets set to pause. I never would have though of that, but somehow it just happens (though, I’ve never seen it happen in any OS earlier than Windows 8/Server 2012).
Here’s how you fix it. Go into View –> Update speed and notice it’s set to pause. So strange.
Go ahead and set it to normal and you’re back in business!
I hope I’ve made your day, at least a little bit easier.
Thanks,
VMware Shared Raw Device Mapped Disk
Reading Time: 3 minutesThe purpose of this configuration is to decrease the time for large SQL backups in VMware virtual machines that are being backed up by VEEAM. In our scenario we have a SQL server and a File Server. We want to mount this in physical compatibility mode on the SQL server, to increase backup time by contacting the LUN on the SAN directly. Since RDM disks are independent, we want to mount the same volume in virtual compatibility mode on the FileServer so that it can be backed up by VEEAM.
For further detail on RDM, please reference the following documentation.
http://www.vmware.com/pdf/esx25_rawdevicemapping.pdf
1. Configuring the SQL Server RDM in Physical Compatibility Mode
Here are the general steps to configuring RDM for physical and virtual compatibility mode.
- Create a LUN on the backend storage device.
- Rescan for storage devices in to confirm the LUN shows up correctly, for documentation I’m using a 15GB volume.
- Once you’ve created that, go add a new hard disk. When you choose your disk type, choose “Raw Device Mappings”, and then select the LUN that was created earlier.
- Next choose a datastore that’s on the SAN that other VMs can access.
- Select a new virtual device node that resides on a new SCSI controller. I picked SCSI (3:0). Upon doing that a new SCSI controller will be created, then finish creating the disk.
- You must now change the newly created SCSI controller type to “LSI Logic SAS” and change the “SCSI Bus Sharing” to “Physical”.
2. Configuring the File Server RDM in Virtual Compatibility Mode
At this point, we’ve now created a LUN and created a RAW mapping to the SQL virtual machine. Now it needs mapped to the File Server virtual machine so it can be picked up by the VEEAM backup.
- Edit the settings of the File Server virtual machine, and add a new hard disk.
- When creating this new hard disk, select “Use an existing virtual disk” and point to the datastore where the RDM was mapped in the last step.
- Choose a Virtual Device node that is on a difference SCSI controller than the other disks, I choose SCSI (3:2).
- You must now change the newly created SCSI controller type to “LSI Logic SAS” and change the “SCSI Bus Sharing” to “Physical”.
At this point, we’ve now created a LUN that has been mapped RAW to a SQL Server. That SQL server can perform it’s backups to that disk which increases backup times by about 20% based in my testing. The File Server virtual machine and the SQL Server virtual machine both now have SCSI adapters that have bus sharing enabled, and thusly the disk is also mapped to the File Server. It is mapped here in virtual compatibility mode (inherent by adding an “existing virtual disk”). This means it’s persistent and can be backed up by VEEAM.
I hope I’ve made your day, at least a little bit easier.
How to find the Hyper-V host name of a guest VM
Reading Time: < 1 minuteIn all of our environments we all know EXACTLY what’s going on, where it’s going on, and where everything is right? Chances are that’s not true, and like most of us, especially in large home-grown development environments there are servers sitting under peoples desks, in some random closets, etc. Here’s an easy way to find out on what Hyper-V host a guest resides.
(get-item “HKLM:\SOFTWARE\Microsoft\Virtual Machine\Guest\Parameters”).GetValue(“HostName”)
Pop that into powershell and you’re good to go!
Hope I’ve made your day at least a little bit easiser.
Thanks,