I'd like to convert a physical machine to a virtual. Its an SBS2008 server. The catch is I have just the one server hardware to use. Is it possible to create VHDs for the system drive as well as a volume on the RAID drive saving the images to a network share, reformat the server and install hyper-v then bring the images in as part of the guest OS?
EDIT: Many answers have also asked why. These are my goals:
One goal is to get more than one server going, so that I can leave the SBS as it is, and install other services on a non-sbs running server. Also, I think it would make migration to sbs2011 easier, since I can install that into a clean virtual and migrate, then shut down the sbs2008 server (while leaving the services on the second server alone). In short, I think running virtuals will give me more options… one long term one includes moving to new hardware. I imagine it'd be easier to move to new hardware if you just transfer virtuals.
I'm currently running this out of my home office, so space is at a premium, and since I'm very small, price is as well. That's why only one server, and why when I do get a new server it'd be a replacement. However as my business grows I'd like to make it as easy as possible to expand out, and it seems like virtuals are a great way to make transitions easier.
Another goal is that I'm looking to have the option to run multiple servers (many are servers I'll setup to mimic client environments, but most of those won't be running until I'm actively doing development. I'll stop and start as needed).
I appreciate all the answers, and someone telling me this is a bad idea is fine as well. A virtual SBS2008 IS a supported MS configuration though, I've found documents telling you how to acomplish just that. Sadly I didn't come across these until recently, while I built the server a few years ago.
Best Answer
It should be possible, but it's difficult without knowing for sure that your hardware is is supported. I'm not going to say that it will work only to have you hit a snag and have it not work, then complain...in some circumstances it might.
The smarter thing to do is get a newer server dedicated to virtualization, then migrate your existing server over and decommission it.
Especially since your server is your only one. SBS will potentially die in the process, and leave your business high and dry.
Here's the options as I see it. One, make sure you have known-good backups, and verify that your p2v migration will support sparse disks, since if it will create the same size volumes you're going to have a size crunch. Then you can allocate a few days to trying it, and if it fails horribly, restore the computer back to the previous state.
Two, which I'd say would be safer, get a server with tons of storage dedicated to being a VM server, migrate your server to that, then decommission it once it's working well. Then turn your old server into a backup domain controller. Even for small business, it doesn't hurt to have 2 DC's.
Three, don't do this, unless you really have a compelling reason to move to a virtual system structure. What are you doing that you are running with SBS, but want to virtualize on that server? Especially if you don't have extra hardware for availability/redundancy? If you do idea two, you could migrate your server, make sure it works, and then turn the old server into another virtual server and install a backup DC and...something else you're trying to virtualize.
Depends on what exactly you're trying to achieve as an end goal (for what reason...?)