Hyper-V Storage considerations for Backup Strategy
As you plan your backup strategy, consider the compatibility between the storage and backup solutions:
· Virtual hard disks. These offer the best compatibility and can be stored on many types of physical media. For more information about the types of storage you can use with Hyper-V, see Hardware Considerations.
· Physical disks that are directly attached to a virtual machine. These disks cannot be backed up by the Hyper-V VSS writer. As a result, this type of disk will not be included in any backup performed by a backup program that uses the Hyper-V VSS writer. In this situation, you would need to use some other process to back up the physical disk, such as running a backup application within the guest operating system.
· iSCSI-based storage. This storage is supported for backup by the Hyper-V VSS writer when the storage is connected through the management operating system and the storage is used for virtual hard disks.
· Storage accessed from a virtual machine by using an Internet SCSI (iSCSI) initiator within the guest operating system. This storage will not be included in a backup of the physical computer. In this scenario, you must use another process to back up the data from the iSCSI-based storage before you perform a full server backup. For example, you could run a backup of the data on the iSCSI storage from a backup application running in the guest operating system.
For more information about deploying storage for Hyper-V, see Implementing Disks and Storage.
Buongiorno
Possiamo considerare come configurazione dello storage migliore utilizzando windows server backup passare dei VHD alle macchine guest dentro hyper V? partendo da una lun iscsi creata sull’host, invece di creare più lun e connetterle alle rispettive macchine, esempio un host fisico hyper v, con al suo interno 2 guest. ??
In termini di prestazioni ?
Grazie
Cordiali saluti
Hi Alessandro
I don’t know if I understood your question, but talking about storage planning, please have a look here : http://technet.microsoft.com/en-us/library/dd183729(WS.10).aspx
and here http://www.hyper-v.nu/archives/tag/troubleshooting/ and also here : http://go.microsoft.com/fwlink/?LinkId=186519
hi Alessandro ! (same name)
thank you a lot for your express answer.. you must forgive me to misunderstood that despite the clear italian name.. you are not italian.. 🙂 i took a look at your blog.. and first many compliments for your work.. you are surely one of the many people that improve for real this enormous world of computers and os.
i will take a look at your links..and again thx…
by the way and now in english my question was..
is it better with a iscsi storage to attach one lun to the hyper host then pass vhd to virtual machine inside for backup storage (windows server backup) or.. to create multiple luns each for any machine? inspired by your above article i understood that its better ine lun with the hyper host then vhds created in the inside virtual machines, infact my hyper lab is returning me a warning when backup start about the various shared luns.
what a about performance between the two solutions .. anyway my backups host and guests are ok and solid.
thx lot again !!
ciao
alessandro
Hi Alessandro
Although my background is italian, I dont’ speak italian.
BTW, I recommned you to use ISCSI connected to the Host not to the VM. I am using 1 LUN per Host with all vhd’s created inside that LUN. The number of LUN’s will depend of various factors, like workloads, storage capacity, etc.
Hi
thx again for your answers.. actually i knew that.. but i real wanted your last word about it before changing my strategy.. well i did it and it is working like a charm.. one lun on hyper v host then i created disk, one logica disk for the host backup then a second one wich contain two virtual disk connected to the two respective guests.. since they are storage for the two windows server backup i used the scsi controller.. and not ata.
keep up your wonderful job.
Ciao
Alessandro
p.s. what your italians origins are from?