The service release for the Symmetrix SRDF Storage Replication Adapter version 5.1 has been posted and is available for download. This isn’t a must-update release for most users but there are some important changes in them that will be very relevant for a few environments. This release will be numbered 22.214.171.124 but in some places may be referred to as 5.1.1.
It’s been a bit but I’m (Drew Tonnesen, email@example.com) back for another guest spot on Cody’s blog. In August 2013 I wrote about the VMAX Content Pack for VMware’s newly released Log Insight product (v1.0). At the time of release VMware was pushing hard for content packs and rode me pretty ragged for 2 weeks to produce one. As a result much of the detail around items like widgets was minimal. This was perfectly acceptable as VMware was also in the nascent stages of the product and content packs. Now with VMware’s release of Log Insight 1.5, they have made some important changes, particularly to the content pack component, which has allowed me to expand our VMAX Content Pack. As I’m only going to cover the new features of the content pack and how it relates to Log Insight v1.5, if you want the full Monty on Log Insight v1.5, VMware’s lead developer goes into detail here. Another great resource for everything Log Insight is Steve Flander’s blog: http://sflanders.net/ . Steve does a great job explaining the new features and how to use them as well as answering any questions.
In my previous post I wrote about expanding a ScaleIO volume in a VMware environment. During that procedure there is a requirement to correlate the EUI of the device hosting the VMFS to the ScaleIO identifier so that you can ensure that you actually expand the correct volume. Especially important in large environments. So I thought is there a way to script this correlation in a simple fashion to save you some work? Can the whole process be automated?
The answer to both is yes!
In my last blog post I wrote about how to provision a new volume from ScaleIO to your VMware environment so the next logical step is what do you do when that volume is completely consumed. Well you have to options; provision a new volume or expand an existing one. Since the former option was covered in my last post, let’s look at the second option.
VMware vSphere has offered the ability to dynamically expand VMFS volumes since, well, vSphere was introduced (version 4.0). VMFS Volume Grow allows ESXi to recognize when a physical device has expanded in capacity and enables an administrator to non-disruptively expand the VMFS volume to take advantage of the extra space without resorting to using messy extents.
I recently posted about adding capacity to a ScaleIO storage pool, so the next logical step is provisioning a new volume. In this post, I am going to cover the straight-forward act of creating a new volume from a storage pool, mapping it to a ScaleIO Data Client (SDC) and then presenting it to the VMware cluster.
The first step is to assure we have enough space to configure a new volume of the size we desire. GUI or CLI will suffice:
When initially installing/configuring ScaleIO in a VMware environment the creation of a storage pool and adding capacity to it is included in the setup process. Obviously every time you want to add a storage pool, add capacity or simply create a new volume you don’t want to have to run the setup process again–that would be silly. And of course you do not have to, nor should you. So how do you add more capacity without adding additional nodes? Let’s find out!
My current environment has four ESXi hosts and one SDS/SDC VM per host (my SDCs and SDSs are the same VM in my environment). Each SDS currently has one virtual disk using the full capacity of a VMFS on top of a physical disk. The plan is to double the capacity of each SDS by adding a new physical disk to each ESXi host and presenting the full capacity (minus the space on the disk reserved for VMFS metadata) via a virtual disk to each SDS. The below image shows the current environment for one ESXi host and also how it will look after the capacity is added.
I’ve started recently playing a lot with EMC ScaleIO (version 1.2 just came out) and deployed it in my VMware environment. VERY easy to deploy and use.
During my investigation of the product I noticed in the vSphere Client that my ScaleIO datastore was marked as supported for VAAI. I looked around for some documentation saying so and I haven’t been able to find any off the bat (if anyone does let me know).
I posted a few months back about the EMC Storage Integrator (ESI) when EMC put out the 3.0 version here:
On November 18th, the 3.0.1 version of ESI was released and I wanted to write a quick post about what’s new. Even though numbering-wise this is referred to as a minor release, it is a very important one for those using (or want to use) the VMAX-related PowerShell cmdlets that are provided with ESI.
Recently I had a partner/customer who was migrating a lot of SAP data from one VMAX to another VMAX and they ran into an issue they weren’t sure how to solve, well at least what the best way to solve it was. This person had a ton of data on the VMAX and more than a few TimeFinder/VP Snap point-in-time copies of each SAP volume that they used for testing/recovery or backup.
For those of you unfamiliar with VP Snap it is a rather new (introduced with 5876) method of local replication on the VMAX that leverages the space-efficiency benefits of TimeFinder/Snap but also offers the flexibility of configuration provided by TimeFinder/Clone.
Quick overview, the SRDF Storage Replication Adapter for VMware SRM TechBook is an in-depth implementation guide focused on how to install, configure and manager SRDF with VMware’s vCenter Site Recovery Manager product. Overview of SRDF, the involved tools and how to perform test recovery, migrations and disaster recovery failovers.
My last hurrah with this TechBook! Since I have moved on to a new (and exciting!) role within the Open Innovation Lab in the EMC Office of the CTO it is time for me to pass on the torch of the SRM TechBook.
Anyways you can find the updated TechBook here: