[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 595
  • Last Modified:

Hyper-V best practices - page file, vCPU, partition, UPS software, backup, etc.

The host is a new Dell server PowerEdge T620 as below
Raid 0, 2x300GB
Raid 10, 10x600GB
Dual Xeon CPUs 2x E5-2660 v2
Host OS: Windows 2012 R2 STD

I will need to configure 2 VMs at this moment, and 1 or 2 more in the future.
- SBS2011 STD
- SQL2008 R2

There are about 60 users.

I would need some best practices to configure the followings
- Page File
For both host and VM
- Virtual processors for VMs
- Hard disk controller
- UPS software
I usually use APC PowerChute. Should I installed it on host only or install it on host and all VMs
- Backup
I usually use ShadowProtect. How is it doing with VM backup?
- VHD vs Partition
Should I assign one VHD to each VM with separated OS and Data partitions?
should I assign two VHDs corresponding to OS and Data to each VM?
should I assign one VHD to each VM with only one large partition?

I am sorry there are so many questions. Please help as you can.

Many thanks!!

4 Solutions
Cliff GaliherCommented:
For page files, leave sizes alone. Let windows handle then. Virtual or physical, you will always get better performance if you out then on a separate spindle though.

Processors: SQL has processor licensing limitations, so unless you've made alternate plans, you'll only be legally allowed to assign one virtual processor to that second VM.

VHD choices: Mainly this is about disaster recovery. I prefer OS on one, and data on a other, per VM. That's a personal preference though and not written in stone.
techcityAuthor Commented:
Our SQL license are per user not per CPU, so I guess I could as many vCPU as I want?
How will separated VHDs help disaster recovery?
Cliff GaliherCommented:
You can back up fast-changing data more often and slow-changing data less often for one thing. For another, in some disaster types that don't kill a machine, such as cryptolocker, restoring an entire data VHD is still faster and easier than restoring an entire OS, especially if that OS is a DC.

You might want to verify your SQL license. Unlike Windows, even user licensed SQL instances usually have processor limits. There were very few ways to license SQL any other way in the 2008 era of products.
When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

David Johnson, CD, MVPOwnerCommented:
I use Veam for Hyper-V backups and DPM for the primary server.  UPS on the host only. Hyper-V is pretty good at stopping and starting VM's on server shutdown.  SQL backups (you can use a stored procedure to keep the log files manageable )
techcityAuthor Commented:
Our SQL Licenses are "Premium Addon" coming with SBS. I will look into it.
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Don't use partitions, these are old fashioned, so create a VHD per disk you require, it makes them easier to manage, and easier re-size.

So if you require a C: drive, make sure this is "mapped" or created as one VHD.

The same with additional drives, D: make sure this is created as disk 2 (another VHD).

Best Practice for APC, is to use a Network Management Card in the APC Smart UPS, and then use APC free software...

see here

techcityAuthor Commented:
Thank you very much! Very helpful!

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now