As I have blogged about before, TLS 1.0 and SSL v3 were deprecated in Purity 4.7, requiring all connections to use either TLS 1.1 or TLS 1.2. This affected a variety of integrations, some we updated, some you just had to alter their behavior. A few VMware products do not/did not use TLS 1.1/1.2 by default, so they either need to altered or upgraded. This almost invariably boiled down to the JDK version that was in use. vRealize Orchestrator is no exception.
It has been awhile since I have done a solely Purity operating environment post and with the recent release of our Purity 4.6 operating environment I thought it was a good opportunity to do one. I will overview some new features and changes, some big some small.
4.6 has been in Directed Availability (DA) for some time, so many of you might already have this, but I decided to wait until it was closer to GA (this is imminent) to post. Not a gigantic release, but I think there is some cool stuff in it regardless.
Here is a brief listing of some of the new stuff:
- VLAN tagging Introduces support for VLAN tagging for iSCSI connections to the FlashArray. VLAN tagging allows multiple VLAN interfaces to be configured on physical iSCSI ports.
- Replication network bandwidth throttling Introduces the ability to set a maximum network bandwidth utilization for replication between two connected arrays. Allows configuration of a default maximum bandwidth and/or a time window during which a different maximum bandwidth is enforced.
- Deduplication-preserving replication Introduces the ability for Purity to preserve inline deduplication savings when transferring replication data to a target array, to reduce the network bandwidth utilization.
- Protection group copy Introduces the ability to copy protection groups, including their member hosts, volumes, and snapshots. Protection group copy is supported in the CLI and REST API.
- The Pure Storage SMI-S Provider Release 1.0.0 of the Pure Storage SMI-S provider is embedded in Purity 4.6.0 release. SMI-S enables both hardware and software interoperability between different vendors’ enterprise storage products and allows vendors to develop to a single standard interface. For more information, please see the SMIS-S release notes.
- Improved readability of graphs in the Purity GUI In the GUI Dashboard and Analysis tabs, changes the color of the write graph to orange to distinguish it from the blue read graph.
- CLI Changes This is mostly to cover the new features above
- REST API version 1.5 Some new REST calls for new features and general enhancements and fixes for our REST API service.
Recently the Purity Operating Environment 4.1.1 release came out with quite a few enhancements. Many of these were for replication, certain new GUI features and the new vSphere Web Client Plugin is included. What I wanted to talk about here is a space reporting enhancement that was made concerning VAAI XCOPY (Full Copy). First some history…
First off a quick refresher on XCOPY. XCOPY is a VAAI feature that provides for offloading virtual disk copying/migration inside of one array. So operations like Storage vMotion, Cloning or Deploy from Template. Telling an array to move something from location A to location B is much faster than having ESXi issue tons of reads and writes over the SAN and it also therefore reduces CPU overhead on the ESXi host and reduces traffic on the SAN. Faster cloning/migration and less overhead–yay! This lets ESXi focus on what it does best: manage and run virtual machines while letting the array do what it does best: manage and move around data. Continue reading FlashArray XCOPY Data Reduction Reporting Enhancement
The Pure Storage Content Pack for VMware vCenter Log Insight is now live on the VMware Solution Exchange! Download it today for free. As past posts have shown I have done a decent amount of work with Log Insight here at Pure and in my previous job. A product I have really liked from VMware for a variety of reasons, a big one being that it is so very easy to use. We really improved our syslog feature on the FlashArray in the 4.0 Purity release, so it was the perfect time to create our first content pack!
Today I posted a new document to our repository on purestorage.com: Pure Storage and VMware Storage APIs for Array Integration—VAAI. This is a new white paper that describes in detail the VAAI block primitives that VMware offers and that we support. Furthermore, performance expectations are described, comparing before/after and how the operations do at scale. There are some best practices listed as well, the why and how of those recommendations are also described within.
I have to say, especially when it comes to XCOPY, I have never seen a storage array do so well with it. It is really quite impressive how fast XCOPY sessions complete and how scaling it up (in terms of numbers of VMs or size of the VMDKs) doesn’t weaken the process at all. The main purpose of this post is to alert you to the new document but I will go over some high level performance pieces of information as well. Read the document for the details and more.
Ah my first official post during my tenure at Pure and it couldn’t have happened at a better time! Just in time for the Purity 4.0 release which we just announced today. While there are plenty of under-the-cover enhancements I am going to focus on the two biggest parts of the release: new hardware and replication. There are other features such as for example hardware security token locking but I am not going to go into those in this post. So first let’s talk about the advancement in hardware!