Storage Replica and HyperV physical / passthrough disk

%3CLINGO-SUB%20id%3D%22lingo-sub-2731655%22%20slang%3D%22en-US%22%3EStorage%20Replica%20and%20HyperV%20physical%20%2F%20passthrough%20disk%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2731655%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20to%20deploy%20an%20stretched%20HyperV%20cluster%20with%20Storage%20Replica.%20All%20is%20working%20flawlessly%20so%20far%2C%20however%2C%20I%20am%20unable%20to%20add%20an%20physical%2Fpasstrough%20disk%20to%20a%20HyperV%20VM%20after%20I%20enable%20the%20Storage%20Replica%20feature%20(this%20is%20a%20disk%20not%20replicated%2C%20or%20planned%20to%20replicate%20in%20the%20future).%20When%20I%20remove%20the%20Storage%20Replica%20feature%2C%20I%20am%20able%20to%20add%20the%20physical%2Fpassthrough%20disk%20to%20that%20VM.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20tried%20to%20remove%20Storage%20Replica%2C%20add%20the%20disk%20to%20VM%2C%20add%20Storage%20Replica%20again%20just%20to%20see%20the%20error%20message%20%22Physical%20disk%20not%20found%22%20in%20HyperV%20VM%20settings.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20expect%20this%20to%20be%20the%20behaviour%20by%20design%2C%20as%20it%20looks%20like%20the%20Storage%20Replica%20is%20claiming%20all%20disks%20upon%20arrival.%20So%20could%20please%20anybody%20from%20Microsoft%20confirm%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20chance%20to%20selectively%20exclude%20some%20devices%2Fdisks%20from%20claiming%20by%20Storage%20Replica%20(for%20example%20with%20specific%20device%20id%2Fdescription%20through%20registry)%20and%20freeing%20them%20to%20HyperV%20VM%20physical%20disk%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMartin%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2731655%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EHyper-V%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Visitor

Hi,

 

I tried to deploy an stretched HyperV cluster with Storage Replica. All is working flawlessly so far, however, I am unable to add an physical/passtrough disk to a HyperV VM after I enable the Storage Replica feature (this is a disk not replicated, or planned to replicate in the future). When I remove the Storage Replica feature, I am able to add the physical/passthrough disk to that VM.

 

I tried to remove Storage Replica, add the disk to VM, add Storage Replica again just to see the error message "Physical disk not found" in HyperV VM settings.

 

I expect this to be the behaviour by design, as it looks like the Storage Replica is claiming all disks upon arrival. So could please anybody from Microsoft confirm this?

 

Is there any chance to selectively exclude some devices/disks from claiming by Storage Replica (for example with specific device id/description through registry) and freeing them to HyperV VM physical disk?

 

Thank you,

 

Martin

0 Replies