Originally Posted by stevetoney
For those interested and those involved in helping me with my early questions - thanks........
I have now have a supermicro 734 case and x7dwe MB with 2 xeons and 8gigs ram with 64bit windows 2008 with hyper-V running.
I have space for 11 hardrives in the case -- currently have OS on a 500 gig drive and 2 other 500 gigs holding various VM's (WHS, XP PRO, VISTA, soon will try windows 7) and other files. I have four 1 TB drives in the 8 bay hotswap cage of the case..
I probably will reconfigure and mirror the primary OS on the first two of the motherboard's 6 sata ports -- should probably have done this from the start, but I'm an acronis image person and can image the OS drive for windows 2008 fairly easily to recover that part of the setup.. 2 of the MB sata port are pipe to a esata adapter to use on extermal drives/
The client OS VM's setup easily. The WHS setup easily for the sys and data drives.. adding the 1 gig drives in the bay to the WHS storage pool was a learning curve for having an offline drive and adding the in virtual scsi controller and hard drive pass through in the Hyper-V setup for the WHS VM. It works well, but was not overtly obvious on how to do this.... earlier help on here help me in the right direction.
one thing not so cool about Hyper-V compared to my VMware experience is not being able to simply make a clone copy of a VM. for testing or backup it only has a snapshot backup system for the VM configuration and underlying OS's (I have imaged within a VM OS, but this is not a VM backup)..
back to WHS.. The use of the physical pass thru drives basically shuts down the snapshot system in Hyper-V for the VM with pass thru drives -- again not good for backing up configuration. hopefully as I image the host os - I can image the drives with the VM's on it as well.
WHS is working well so far -- just under 4TB of storage configured -- backing up 4 networked vista PC's -- I copied my photo and music collection and setup duplication for that
still setting up backups for these and the storage database to external drives outside of the storage pool in WHS using a backup addin and Synctoy
My main concern so far with WHS is not being able to image / clone the OS and it's configuration. Given how it works no current image methods work and the OS backup options are currently quite lame.. basically only are restore install of WHS and reinstall and reconfigure all your software and settings..
I probably will only use this as a learning test setup of WHS until this specific issue has a better recovery option.. I will continw to use my larger raid base server with windows 2003 and my readyNas until then for the production media service.
I will try the mymovies for WHS software as I'm running a Mymovies server on the windows 2003 box, but if that work well - I'll still keepin the large movies ISO files on the larger 2003 hw raidbased server
thanks to those who answered questions as I was building the server setup..
Steve, glad you got Server 2008 and Hyper-V up and running.
As you become more familiar with it, you'll begin to appreciate it's ease of use.
There's a couple of different ways to backup a VM.
First you should be sure that you've installed the MS integration tools to the VM.
1. Within Hyper-V console use the 'export' tool to export a copy of the VM and it's configurations to another drive/share/storage area. This essentially creates a complete usable copy of the VM that can be 'imported' back into any Hyper-V server and started up.
First go to My computer and select the single drive or array that the VM is running on. Right click, goto tools and enable shadow copies for that drive.
Shadow copies will automatically be created depending on the schedule set.
2. Use native Windows Backup (WB) to take an image backup of the VM.
You'll need to google a registry edit that enables WB to use Hyper-V VSS writer. This is important to allow you to image backup a running VM, similar to image backups for a database.
The backup process calls up MS VSS service, tells it to take a snapshot, which in turn notifies Hyper-V to communicate with the VM and prepare it to be VSS'd. WB then completes and saves the backup.
The drawback here is that WB backups entire volumes like drive F: or an array volume and all VMs on it. It can't backup/image only 1 VM, unless it's the only one on that volume. Same applies for restore, but you could always restore the backup somewhere else copy over the VM you need.
3. Same as above, but more granular.
Use Acronis to take a file based image backup of the VM. The key here is go into the options of that backup task and enable 'use VSS'. This again notifies Hyper-V that a VSS snapshot is needed for backup, Hyper-V notifies the VM. to prepare. Snapshot is taken and handed to Acronis which then process the image backup into a .tib container and saves it where you specfied for that task. You can run incrementals on this backup.
The technet Hyper-V forum
is a good place to get more detailed info.
Hope some of this helps.