A few days ago I posted about problems with Storage VMotion. Unfortunately it turned out that these problems appeared on an unsupported configuration. In the comments on my post, Bob Slovick wrote the following:
“Bob Slovick // Jan 24, 2008 at 8:26
That post refers to a person that is using the Qlogic HBAs with the IBM ES800, where table 8 of the Storage/SAN compatibility guide specifically states that only Emulex HBAs are supported for the IBM ES800.
Storage VMotion is very sophisticated technology and depends on using qualified storage configurations. If you use unqualified/unsupported configurations, it is unfair to criticize the technology, as you are knowingly in uncharted waters.”
I therefore decided to remove / rewrite this post. Thanks Bob for pointing it out to me!
This has been attributed to using unsupported storage arrays. The author of this post has already retracted it from the VMprofessional blog.
This article was removed by the poster on the original web site, as it was found that they were using unqualified/unsupported storage, and the poster apologized to us for posting it.
Hi
On this thread you can read about the same issue which still isn’t solved. http://communities.vmware.com/thread/121684?tstart=0 so I decided to not change this post yet, but I’ll be watching this closely. Thank you for pointing me to the retracted article !!!
Gabrie
That post refers to a person that is using the Qlogic HBAs with the IBM ES800, where table 8 of the Storage/SAN compatibility guide specifically states that only Emulex HBAs are supported for the IBM ES800.
Storage VMotion is very sophisticated technology and depends on using qualified storage configurations. If you use unqualified/unsupported configurations, it is unfair to criticize the technology, as you are knowingly in uncharted waters.
Excellent! Great article, I already saved it to my favourite,