Looking for general feedback on Hyper-V usability and Dell PowerEdge R905

we startup , finding increasingly having purchase new hardware support various environments , initiatives. toying idea of using hyper-v dell poweredge r905, have no experience either. because new stuff, wondering experience has been may have used either... , recommend development environment?

also, how hyper-v compare other vm's, such vmware? (i price, @ least)

finally, curious backup using veritas... there big cost upgrade hit here? can backup/restore entire vm?

ohers may reply here re experiences, started:

re hardware: 
hyper-v planning , deployment guide: http://technet.microsoft.com/en-us/library/cc794762.aspx

to find list of supported server configs:
go http://www.windowsservercatalog.com/ .
select certified servers on right hand side.
select windows server 2008 (x64) on left hand side.
select hyper-v on left hand side.

the performance tuning guidelines windows server 2008 has been updated include perf guidelines virtualization servers: http://www.microsoft.com/whdc/system/sysperf/perf_tun_srv.mspx

joeelway's blog links handy hyper-v ram calculator can use plan hyper-v deployment: http://cid-2095eac3772c41db.skydrive.live.com/self.aspx/public/hyper-v%20ram%20calculator.xls

re: backup:

taylor brown's blog post explains away of confusion around backup/snapshot in hyper-v: http://blogs.msdn.com/taylorb/archive/2008/08/20/backing-up-hyper-v-virtual-machines-using-windows-server-backup.aspx

see also:

how enable windows server backup support hyper-v vss writer : http://blogs.technet.com/askcore/archive/2008/08/20/how-to-enable-windows-server-backup-support-for-the-hyper-v-vss-writer.aspx

windows serever 2008 backup , recovery overview : http://technet.microsoft.com/library/cc770593.aspx

windows server backup step-by-step guide windows server 2008 : http://technet.microsoft.com/en-us/library/cc770266.aspx

microsoft data protection manager trial: http://technet.microsoft.com/dpm/bb727240.aspx

here preliminary documentation on planning backing hyper-v vms. made part of our planning , deployment guide on technet.

planning backup
when plan backup , recovery strategy virtualized server environment, there several factors consider. must consider different types of backups can make, state of virtual machine, , type of storage being used virtual machines. topic discusses advantages, disadvantages, , considerations these factors.

understanding backup options , considerations
the backup integration service , hyper-v volume shadow copy service (vss) writer provide mechanism backing virtual machines system-wide settings apply hyper-v. there 2 basic methods can use perform backup. can:

• perform backup server running hyper-v. using method perform full server backup recommended method because captures more data other method. if storage compatible hyper-v , hyper-v vss writer, can perform full server backup helps protect of data required restore server. data included in such backup includes configuration of virtual machines , virtual networks, snapshots associated virtual machines, , virtual hard disks used virtual machines. result, using method can make easier recover server if need arises, because not have recreate virtual machines or system-wide settings such virtual networks.
• perform backup within guest operating system of virtual machine. method useful when need data storage not supported hyper-v vss writer.

storage considerations
as plan backup strategy, consider compatibility between storage , backup solutions:

• virtual hard disks offer best compatibility , can stored on many types of physical media. more information types of storage can use hyper-v, see “hardware considerations” in hyper-v planning , deployment guide on technet (http://technet.microsoft.com/en-us/library/cc816844.aspx).
• network-based storage such shared folders should used caution. if network-based storage unavailable when backup attempted, backup fail.
• physical disks directly attached virtual machine (sometimes referred ‘pass-through disks’) cannot backed hyper-v vss writer. result, type of disk not included in backup performed backup program uses hyper-v vss writer. in situation, need use other process physical disk. example, run backup of data on iscsi storage backup application running in guest operating system.
• storage accessed virtual machine using internet scsi (iscsi) initiator within guest operating system not included in backup of physical computer. in scenario, must use process data iscsi-based storage before perform full server backup. example, run backup of data on iscsi storage backup application running in guest operating system.
• iscsi-based storage supported backup hyper-v vss writer when storage connected through parent partition , storage used virtual hard disks.
  

understanding online , offline backups
whether backup performed online or offline depends on whether backup can performed without downtime.
an online backup can performed no downtime on running virtual machine when of following conditions met:

• integration services installed , backup integration service has not been disabled.
• all disks being used virtual machine configured within guest operating system ntfs-formatted basic disks. virtual machines use dynamic disks or fat32 file system prevent online backup being performed.
• volume shadow copy service must enabled on volumes used virtual machine specific configuration. each volume must storage location shadow copies , mapping must available hyper-v vss writer. in other words, shadow copy storage of c: should on c:, shadow copy storage of d: should on d:, on forth.

if online backup cannot performed, offline backup taken. type of backup results in degree of downtime. variety of factors can affect time required take offline backup. if virtual machine running or paused, put saved state part of offline backup process. after backup completed, virtual machine returned existing state.

-http://blogs.technet.com/virtualization/archive/2008/08/29/backing-up-hyper-v-virtual-machines.aspx

---

tony soper

Windows Server  >  Hyper-V