Running SBS 2011 with single dynamic disk for files

Hi

I've been reading up on the difference between fixed and dynamic sized disks when related to Hyper-V 2008 R2.

The blog consensus appears to be do not put your exchange on dynamic disks. What I am thinking to work around this problem is virtualised small business server 2011 with a fixed C drive for the OS, fixed 100 gig D drive to store exchange and SharePoint information. Then create a 600 GB dynamic disk to store the clients word documents etc.

The client only has around 80 GB of data (of the word, excel variety). Currently I have been testing the small business server with fixed disks across the board. What this means is the bare metal backup from the Hyper-V host is taking forever because there is a 600 gig disc that only contains 80 gig of actual data.

To cut a long story short I would be running small business server on fixed disks with the exception of Word documents etc residing on a dynamic/thin provisioned disks.

The client has around 12 staff and the disk subsystem is a Dell PERC spinning six 450 gig 15 k SAS so throughput is pretty good.

Looking for thoughts on this from SBS and virtualisation experts

thank you
Amiga-2000Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DavidPresidentCommented:
Why not just buy a 128GB SSD.  Performance will be fantastic, and it won't make a difference how the SSD is configured, because it will still be the fastest VM you have by far ;)
Cliff GaliherCommented:
I could write an entire book on the subject (and some day, maybe I will) but the short version is this:

A backup is intended to help recover from a disaster. And there are different kinds of disasters that can impact a virtual server environment. If you actually break down what can go wrong, I think you'll find that doing a bare-metal backup of a virtual host rarely makes sense. So you can avoid your problem by rethinking your backup strategy.

In most Hyper-V environments, I back up the guest OS from within the guest OS. This allows me to schedule different backups based on the importance of the VM. My dc's rarely see change so they can be backed up less often than, say, an important SQL server that sees many transactions. But again, going into details of how often to back up....that'd be a book. Regardless, if you back up SBS from within SBS, you'll not take all that space and your backups will be faster.

Then, as far as the host goes, you can back up just the virtual machine configuration files so that if a crash on the host occurs, you can get your VMs back the way they were and then restore from within the VM, again giving you the option to bring up the most important VMs first.

Or you can back up the C drive and just exclude the VHD files. Thus making your host backup small.

Or, if you *really* want to be able to do a bare metal, reconfigure your physical layout so your VHDs are not on the system partition and then you can configure a bare-metal backup and set an exclusion on .vhd files. The only difference between this and the "backup the C drive" above is that you cannot set exclusions on the C drive when "bare metal" is selected, hence the VHDs have to be elsewhere.

Anyways, you have options. All of which are better than dynamic disks.

-Cliff

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Amiga-2000Author Commented:
Apologies Cliff for not being more detailed in my question. My focus really was on reducing the backup size of the bare metal recovery of the host . I'm absolutely backing up the guests with a mixture of 'virtual bare metal recovery' to each guest, file replication. On-site /  offsite data rotations for the VM guests, the backup is under control. My fault for not making this clearer
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Virtualization

From novice to tech pro — start learning today.