In my last post, I discussed building a lightweight VMware infrastructure for a customer using a Synology RS2414RP+ NAS. Today, I wanted to do some performance testing and baselining to get an idea of the kind of load it would support. To do this, I used a VMware Fling called VMware I/O Analyzer. A Fling is an ad-hoc tool built by VMware engineers or the community as one-off side projects.
Update: Looking for NFS instead of iSCSI? Check out this post: How to set up VMware ESXi, a Synology NFS NAS, and Failover Storage Networking
This week, I’ve been working on a lightweight virtualization infrastructure for a customer and I thought you’d like to see a little of how I put it together. The customer wasn’t really interested in paying for a full SAN solution that would include chassis redundancy and high performance. They opted instead for a 12-bay Synology RS2414 RP+, a couple of HP servers for ESXi hosts, and a Cisco 2960 Layer 2 Gigabit storage switch all tied together with VMware vSphere Essentials Plus.
While not exactly a powerhouse in terms of speed and reliability, this entry-level virtualization platform should serve to introduce them into the world of virtual servers, drastically reduce rackspace and power consumption, provide the flexibility they need to recover quickly from server hardware outages, and allow them to more easily migrate off of their aging server hardware and operating systems all without breaking the bank. Today, I’m going to show you how I set up Active/Active MPIO using redundant links on both the ESXi hosts and the Synology NAS, allowing for multipath failover and full utilization of all network links.