I just bumped in to a bunch of new VMware EVO:RAIL demos which I wanted to share. Especially the third demo which shows how EVO:RAIL scales out by a couple of simple clicks.
General overview:
Customer Testimonial:
Clustering appliances:
Management experience:
Configuration experience:
x
Dear Duncan,
Thank you for the very useful post.
We are planning to deploy Supermicro Evorail and wondering:
1. Is there any disk IO performance hit when we need to replace a failed hard disk on this evorail/vsan?
2. If we have 2 nodes per data center (2 data center) is there any DR capability from this evo rail where we could replicate the data and ideally not using any snapshot feature?
We had bad experience using Veeam Snapshot when doing replication and now we are trying to avoid it as much as possible.
1) Yes there will be a minimal hit for IO coming from disk instead out of read cache on SSD. This will be minimal hit though and not something I would normally expect the user to notice even
2) EVO:RAIL comes as an appliance with 4 nodes, this is the minimum you can have per site. For DR capability you can use vSphere Replication, or when it is available EMC Recover Point (virtualized).