As you might have read on my blog a few days ago, EMC released an updated version of the Virtual Storage Integrator tool for vSphere Web Client that supports direct provisioning and some management of VNX and VMAX storage. The previous version supported ViPR-only provisioning. If you didn’t see that post you can check it out here. Inevitably when a product involves cross-application and importantly cross-server integration many customers ask the question about what are the firewall requirements to get this thing to work? Let’s take a look.
Today the long-awaited update to Virtual Storage Integrator for the vSphere Web Client as been released! Six months or so ago EMC released the first iteration of the VSI Web Client (version 6.0) that supported provisioning of storage but only for environments enabled with ViPR. The latest release (version 6.1) now adds support for direct provisioning of storage from a VMAX or VNX array.
Increasingly, organizations, small and large, are attempting to or at least considering to implement some type of cloud-based architecture into their IT infrastructure. The benefits of tight integration, intelligent abstraction of resources, seamless automation and orchestration are becoming quite apparent. These benefits and the desire to obtain them are causing customers and partners to look at vendors such as EMC for such a solution. Importantly, a solution that doesn’t require re-invention of the wheel or painstaking initial setup.
My colleague Jonas Rosland (@virtualswede) has been doing some great work with Splunk recently (check out a post from his blog here) and it got me to want to get my own hands a little dirty. So far I’ve only scratched the surface on what can be done with Splunk but I decided to put a post together on some basics. For this post I am going to talk about Symmetrix VMAX logs and how to get those into Splunk.
Quick post here. As some of you may or may not know, the SRDF and VMware Site Recovery Manager techbook that I have “owned” for four years or so is now out of my hands since I moved onto a different role within EMC. Drew Tonnesen (drewtonnesen.wordpress.com) from Symmetrix Engineering is now the author of the book. Anyways the techbook has been updated to include the latest changes included in the SRDF SRA version 5.5.1 which we released a few weeks ago.
Quick post here. On February 10th, EMC released a service release for VMAX arrays which is code level 5876.268.174. You can find the release notes here:
As I wrote about in a recent post the 5.1 version of the SRDF Storage Replication Adapter was updated in a service release. Similar fixes and a few other changes have been also added to the SRDF SRA version 5.5. If you are running VMware Site Recovery Manager version 5.1 or 5.5 this is the SRA you should be using. SRM 5.0 users can only use the 5.1 SRA (while the 5.1 SRA supports SRM 5.0 and 5.1 I recommend SRM 5.1 users use the 5.5 SRA).
So what’s new in the latest SR for SRDF SRA (184.108.40.206)?
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 220.127.116.11 but in some places may be referred to as 5.1.1.
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.