Your mileage varies with whether or not I/O gets broken, but I've tested some settings for my customers that have overcome this issue for some workloads.
I've already posted some articles on this forum that aided me..h
Your mileage varies with whether or not I/O gets broken, but I've tested some settings for my customers that have overcome this issue for some workloads.
I've already posted some articles on this forum that aided me..h
I do have some concerns about what "DSS V6 will break i/o operation performed on the DSS V6 iSCSI target e.g. copying of files" really means in a real-world Hyper-V environmnet.
I hope to find out some time later this month. Right now I am waiting for a good time to move my current VMs off to a temporary third Hyper-V server while I build/test the cluster environment. During a catastrophic SAN failure, I could live with the VMs actually "crashing" and then restarting from the redundant SAN. 100% uptime is not a requirement for our environment; I'd just like to minimize any downtime.
I'll do some forum searches and look at your tips!Originally Posted by enealDC
Well what it's trying to say is that when a failover occurs that there is a risk of IO operations being broken.
DSS isn't just breaking stuff randomly![]()