Eric Siron shares his experience of providing data redundancy for small businesses by offering 8 Best Practices for Small Business Backup using Hyper-V.
In part one of this series, we talked about Hyper-V’s key-value data exchange feature and got an idea for how it works. In this post, I’m going to provide you with some PowerShell modules that are intended to alleviate most of the pain of using Key-Value Pair Data Exchange. Once you’ve implemented these modules on your systems, you’ll be able to pass data back and forth from guests to hosts.
You’d be hard-pressed to find any feature of Hyper-V that’s been around as long as Data Exchange yet received so little attention. That’s not surprising, since it’s fairly difficult to use at all, much less effectively. My goal with this post is to introduce you to this feature along with a few methods that make using it easier. At the worst, you’ll get a decent understanding of what it does. If you’re lucky, you’ll come up with a use for it.
It is possible to connect the host’s physical optical drive directly to a virtual machine for the purpose of loading operating systems and software, but, unless the host is right next to you, it’s not very practical. The obvious solution is to use images of the necessary discs. Hyper-V makes some of that easy, but using it across a network connection can be somewhat more difficult. This post will examine your options.
We’ve had quite a few posts about Hyper-V checkpoints lately (formerly snapshots). We also spend a fair bit of time warning people not to tinker with them manually. There are still those people that are going to tinker despite any warnings, and there will always be those people who don’t even find the warnings until they’re too late to be of any value. The least I can do is provide a tool that can be of use to anyone that’s stuck working on a complicated tree of differencing disks.
It’s not difficult to find all sorts of lists and discussions of best practices for Hyper-V, however best practices lists are a bit tougher to find for failover clustering. What I’m going to do in this article is focus in on the overlapping portion of the Hyper-V/Failover Cluster Venn diagram, resulting in my 19 best practices for a Hyper-V Cluster.
2015 will be a memorable year for a great many reasons, ranging from the horrific to the spectacular. Assuredly, the biggest buzz for us is around all the exciting features that are currently being cooked up for next year’s Windows Server 2016. It’s an impressive list by any standards. Hyper-V users are going to have a number of things to look forward to. Y
As we stand at this junction point between years, both looking backward into 2015 and looking forward into 2016, I want to take this opportunity to talk about the ways that 2016 will resurrect old concepts both good and bad in Hyper-V.
By default, Hyper-V will store newly created virtual hard disks to C:\Users\Public\Documents\Hyper-V\Virtual Hard Disks. It’s not an intuitive path name to recall and most administrators will want to use a dedicated volume for the management operating system and at least one separate volume to contain virtual machines. Fortunately, the default can be very easily modified.
Virtual hard disks are usually created along with their owning virtual machines or, when a disk new is needed for an existing virtual machine, directly from the VM’s property sheet. There are times when you’ll want to connect an existing virtual disk, though. This post explains how to attach an existing virtual disk to a vm using Hyper-V Manager
Linux doesn’t always run smoothly on Hyper-V. Have you had issues shutting down or restarting a guest using Ubuntu Linux on Hyper-V? Here’s a post from Eric to help you out!
By default, the checkpoint files for any given Hyper-V virtual machine are stored in a Snapshots sub-folder of its primary containing folder. “Snapshots” is what checkpoints were called in earlier versions, but the folder naming and some other elements have not yet been updated to match.
Part of our reality is maintaining older guest operating systems on our hypervisors. One of the main issues that come along with that is maintenance of Hyper-V’s Integration Services. Eric shows us how to Install integration components in Hyper-V in this post!
One of the things I commonly lament over is the poor state of the management tools available for Hyper-V (from Microsoft; I’m pointedly not talking about third party solutions). One issue I see a lot of is that there isn’t a quick way, when looking at the Hyper-V-specific tools, to know how much free memory a host has. People then have to resort to other tools like Task Manager to determine this. These methods are usually effective, but imperfect. Sometimes, you are unable to match up what those tools display against what happens in Hyper-V.
My standing recommendation on allocating virtual machine resources is to start small. It’s very easy to grow almost all virtual resources with very little, and sometimes no impact. Taking resources away, on the other hand, can be trickier. The most difficult resource to remove from a virtual machine is drive space. If it’s just a matter of removing a disk, that’s usually not so bad. Making a virtual disk smaller is somewhat trickier.
Creating and managing VDI are not trivial tasks in Hyper-V (or any other hypervisor) and can end in disaster if not properly planned. My goal with this article is to reach you during the contemplation phase where you’re trying to determine if VDI is worth tackling.
Here are 7 things to think about before even starting a pilot project.