The storage market has gradually been using more and more flash to increase speed and lower cost for high I/O workloads. Think FAST VP or FAST Cache in a VNX or SSDs in an Isilon for metadata acceleration. A little bit of flash comes a long way. But as soon as you need enormous amounts of flash, you start running into problems. The “traditional” systems were designed in an era where flash wasn’t around or extremely expensive and thus simply weren’t designed to cope with the huge throughput that flash can deliver. As a result, if you add too much flash to a system, components that previously (with mechanical disks) never were a bottleneck now start to clog up your system. To accommodate for this increased usage of flash drives the VNX system was recently redesigned and is now using MCx to remove the CPU bottleneck. But what if you need even more performance at low latency? Enter EMC XtremIO, officially GA as of November 14th 2013!
EMC sends out a VNX Uptime Bulletin every quarter to update customers on best practices and fixes which will help you in achieving the maximum possible uptime and robustness for your VNX. You can subscribe to them as you would to with any other ETA (EMC Technical Advisory): log in at http://support.emc.com, go to Support by Product, open your product page (in this case the VNX) and click “Get Advisory Alerts” to subscribe. This bulletin discusses pools and LUN ownership, vault drives, software versions, etc.
In 2013 the EMC Elect story started: 75 top social media influencers were hand-picked by their peers for sharing their knowledge and enthusiasm about EMC products and solutions over the past year. I myself am honored to be part of the EMC Elect, together with my fellow Open Line colleagues Rob Koper and Menno de Liège. With 2014 around the corner, it’s time to continue the story and nominate the EMC Elect 2014.
LUNs on a storage system represent the blobs of storage that are allocated to a server. A (VNX) storage admin creates a LUN on a RAID Group or Storage Pool and assigns it to a server. The server admin discovers this LUN, formats it, mounts it (or assigns a drive letter) and starts to use it. Storage 101. But there’s more to it than just carving out LUNs from a big pile of Terabytes. One important aspect is LUN ownership: which storage processor will process the I/O for that specific LUN?!
Once your Isilon cluster is up and running you’ll want to keep an eye on it. A piece of software that’s extremely useful to monitor both performance and capacity usage is InsightIQ. Very easy to set-up, it’s extremely powerful both in pro-active and reactive monitoring scenarios. Either sit back and watch the scheduled reports land in your mailbox or take a more active approach and drill down to find the source of a performance problem. Let’s explore further!
Earlier this month EMC announced the new VNX series which promises more performance and capacity at a lower cost per GB and a smaller footprint. The hashtag for the event was #Speed2Lead which was trending on Twitter during the official event and the weeks leading up to the Mega Launch in Milan, Italy. With performance being key in the new systems, the announcement was built around the Monza race track which had the Formula 1 circus in town. Guess what the logo for the launch was?
I myself was on summer holidays during the big event (ending up only a hundred miles away from Milan, albeit a week late ;)), so I couldn’t do much more than refresh twitter and get my timeline blasted to bits. So consider this a catch-up post!
When migrating servers from one storage system to another there are basically two options: Migrate using storage features like SAN Copy or MirrorView, or migrate using server based tools like PowerPath Migration Enabler Host Copy, VMware Storage VMotion or Robo Copy. Which option you choose depends on a lot of factors, including the environment you’re in, the amount of downtime you can afford, the amount of data, etc. I’ve grown especially fond of PowerPath Migration Enabler due to its ease of use. You can throttle its migration speed, your “old” data is left intact (so you’ve got a fallback) and once you’ve gotten use to the commands it’s child’s play to migrate non-disruptively and quickly.
I’ve treated myself to a shiny toy not too long after I started working in IT: a 2004 Honda VTR 1000 SP-2 (branded the RC51 in the US). It’s immense fun to ride and makes all the right noises when you twist your wrist. I’ve spent two summer holidays in the Alps on this bike and another three days on a race track in the south of France. With riding comes maintenance, something I enjoy doing myself. I’ve always had a fascination and curiosity with technology: if it makes a lot of noise, looks pretty and goes fast that’s even better. It’s a chance to get my fingers dirty, learn something new, assure myself it’s done correctly and save some money while I’m at it. A while ago I had to perform a valve clearance adjustment due to hitting the 30k km mark. A job that scares most people right from the start, but actually isn’t that hard if you pay attention. Read on to find out how to do it on a VTR SP-2 / RC51!
Yesterday we racked and stacked the EMC Isilon systems, prepared most of the cabling and pretty much prepared to start the Isilon systems. Which is pretty uneventful if you consider we’ve been dragging along hundreds of kilograms of equipment all day yesterday… The whole process can be pretty much split in four parts: configure the cluster and initial node, join the remaining nodes, configure the network, configure the rest.