Hi MS Community. This thread is locked. You can follow the question or vote as helpful, but you cannot reply to this thread. I have the same question 8. Report abuse. Details required :. Cancel Submit. SpiritX Volunteer Moderator.
That is correct, which means that the only way to attach the storage to the VM would be by encapsulating it in a VHD file or by directly connecting it in the case of iscsi.
So what you could do is create a large VHD on the SAN storage and then let the VM use that, however it sounds like you want it to be accessible to the host machine as well, which it would not. As for your specific application I generally don't like making specific recommendations with so little information, however it sounds like you plan on creating a VM if your hardware fails?
Then accessing the application files from the VM? That is technically possible as long as you are using Hyper-V which would allow the pass-through disks, however I have this nagging feeling that I am missing something.
Are you looking to setup a cluster with a physical and a virtual node? If that is what you are doing then it would be an unsupported configuration since it would be non-identical hardware.
Perhaps what you are looking for is HA on that application which would not even require virtualization. Or if there is more to your environment maybe HA VMs to run the application, either way you would need to have clustered hardware with the cluster configured appropriate to your requirements.
Am not trying to build a Cluster. I am trying to understand if the below mentioned scenario works with VM's are not. Lets assume i have a server and some LUN's have been presented to that server, i have some data on those disk's and the server hardware fails.
Then i would buy a new server with a new HBA and i will map the disks on san to the new server. This would perfectly work and i will be able to access all the data which was previously created from failed server. Now my scenario is, current working server fails, i will create VM using Hyper V on a standby server. Then i want to present the disk which was previously pointing to failed server.
Larger default size for dynamically expanding virtual hard disks Virtual Server now defaults to creating GB virtual hard disks by default. It's your feedback that drove this Service Pack Release and the feature set for Windows Server virtualization. Original post. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.
Please rate your experience Yes No.
0コメント