A lot has been written about HP's acquisition of 3PAR. I see it as a real game changer in our industry. This screencast explains why.
A lot has been written about HP's acquisition of 3PAR. I see it as a real game changer in our industry. This screencast explains why.
Posted at 09:25 PM in 3PAR, Adaptive Optimization, Autonomic, Efficient, energy, enterprise storage, green computing, HP, multi-tenant storage, performance, reservationless, storage management, storage services, thin provisioning, tiering, utility computing, video, virtualization | Permalink | Comments (2) | TrackBack (0)
Tags: 3PAR, Autonomic, Converged Infrastructure, Efficient, HP, Multi-tenant
My friend JR, an SE at 3PAR (now HP) , made this demo showing our autonomic management capabilities. It was a bit long, so I scrunchified it and now it makes him sound like he was completely caffeined out when he made it. That's what friends are for, right JR?
Terremark is a leading cloud service provider that delivers just in time infrastructure services, as described in this excellent post on the Boxed Ice blog today titled, The New Server Density Infrastructure. This post, written by a Terremark customer shows that Terremark is not only interested in driving down their own costs, but also in helping their customers be more efficient too.
If you are interested in a behind the scenes look at how Teerremark does it, you owe it to yourself to check out this case study on Wikibon today. This chart from the Wikibon study shows how Terremark derives its operational savings (click on it to see an enlarged version)
Savings from storage were projected to be 86%.
Guess who their storage vendor is? (The report says what equipment they are using). But one big clue is that it isn't EMC, as EMC's Chuck Hollis suggested back in July.
Cloud industry insiders know this stuff. We don't have all the cloud customers, but we have some of the most largest and most influential ones. Nobody really knows what changes cloud computing will bring to our industry, but 3PAR is very well prepared to be a key component of those infrastructures.
Posted at 12:23 PM in 3PAR, bloggers, cloud computing, clustered storage, customers, EMC, enterprise storage, HP, multi-tenant storage, partners, SAN, storage companies, storage management, thin provisioning, virtualization | Permalink | Comments (2) | TrackBack (0)
Tags: 3PAR, cloud, EMC, HP, Terremark, virtualization, Wikibon
Posted at 08:26 AM in 3PAR, cloud computing, customers, enterprise storage, mid range storage, multi-tenant storage, partners, performance, SAN, storage management, storage services, thin provisioning, tiering, utility computing, video, Virtual Domains, VMware | Permalink | Comments (0) | TrackBack (0)
Tags: 3PAR, hotspot, virtualization, VMware, VMworld
To a lot of people, especially those who are unfamiliar with the storage industry, one of the obvious questions is "Who are these people and where did they come from?"
The answer is that the company was formed by a group of server-cluster engineers from Sun and has been around for over a decade developing and selling large scale storage products designed for something that used to be called "utility computing" seven years ago, but today is just called "the cloud".
We've been very successful with our cloud strategy and have 7 of the top 10 IAAS (infrastructure-as-a-service) customers as clients. 3PAR products work very hard in the background for a lot of household-name customers. Most people don't know or care.
However, cloud industry vendors know 3PAR because they are also very heavily involved with those same customers, competing with their own products. They see our storage systems in those large data centers and our customers tell them that they need to make sure they work with us. There's nothing unusual about that sort of thing, but we definitely are a player.
Here's what we do very well:
The thing that we didn't completely understand at 3PAR was how quickly the onset of the virtualized data center was going to tilt the storage world in our direction. 3PAR storage systems are based on a highly advanced, granular storage architecture. It's not always the easiest thing for people to understand because it is so different than any other vendor's architecture. However, people familiar with virtualized server features have a much easier time understanding how our technology works. There is nothing like a terrific, relevant analogy for explaining how your different widget works.
3PAR is a relatively small company, competing with much larger companies who use the benefits of their size, global reach and service organizations against us every day in sales opportunities. It hasn't been easy, but we've continued to grow our business in a very hotly contested arena where our competitors like to position us as the "small, new company" Storage purchases in this market are high stakes and careers can be made or lost on the right decision. We certainly don't win all the deals we are in, but we very seldom lose on technical merit. Usually it's because we are lesser known or because we can't match the service offerings of our larger competitors.
It appears that some of those variables will be changing for us relatively soon.
Posted at 09:08 AM in 3P, cloud computing, clustered storage, customers, Dell, enterprise storage, HP, mid range storage, multi-tenant storage, partners, storage companies, storage management, thin provisioning, utility computing | Permalink | Comments (4) | TrackBack (0)
Tags: 3PAR, cloud computing, Dell, HP, multi-tenant, storage , utilization
This is an older video I shot from late last year with Chakri Avala from Symantec and and Karl Swarz for 3PAR demoing how thin reclamation for Symantec Storage Foundation works. Storage demos like this are a bit like watching grass grow, but storage admins will get the idea of how file system-integrated reclamation works.
Derek Seaman posted in his blog yesterday about capacity thinning, zero reclamation technologies and included a test of 3PAR's Thin Persistence software. In his post he lists the steps he took to run the test, including the setup and final results. Please go read what he wrote, but I thought I'd post his summary:
This test proved that the 3PAR zero reclaim feature worked as advertised, happens in real time, and take very little effort to use. The same process would work for a virtual machine as well. If I was using the Veritas Storage Foundation I would not have to use the sdelete command and it would be fully automated. Hopefully they will work with Microsoft and VMware to support a fully automatic and native method to reclaim the deleted space. Until then, you can run sdelete from time to time to drop those extra pounds from your fat LUNs.
3PAR sees thinning technology as a strategic advantage that we are committed to advancing in the industry with software partnerships. Examples of progress on these fronts include the automated thinning for Oracle ASM and implementing VMware's VAAI Block Zeroing, which turns a thick volume into a thin one on 3PAR storage with Thin Persistence.
Posted at 08:26 AM in 3PAR, bloggers, customers, enterprise storage, green computing, mid range storage, multi-tenant storage, Oracle, storage management, thin provisioning, VMware | Permalink | Comments (0) | TrackBack (0)
Tags: 3PAR, block zeroing, Oracle ASM, reclamation, storage, Thin persistence, VAAI, VMware
3PAR designs its systems to provide huge time savings for storage administrators. Below is a video of our new InForm Management Console (IMC) 4.1, announced today, showing how incredibly easy it is to configure and operate 3PAR's Remote Copy application.
Things that the demo didn't show that are advantages of 3PAR's single software architecture are:
Here is a brief description of all the software functions available through IMC 4.1. As you can see, it's a pretty comprehensive list of features:
Posted at 06:00 AM in 3PAR, Adaptive Optimization, clustered storage, Dynamic Optimization, enterprise storage, mid range storage, multi-tenant storage, remote copy, snapshots, storage management, thin provisioning, tool talk, utility computing, video, Virtual Domains, wide striping | Permalink | Comments (3) | TrackBack (0)
Tags: 3PAR, console, GUI, IMC 4.1, remote copy, replication
It's getting very hard to keep up with all the crazy social media stunts coming out of Hopkington, but they seem to have done it to themselves again. First was the questionable spamming for viewers so they could claim they had a viral video, then today they just "leaked" a 3PAR sales "kill sheet" - and also apparently established a "secret" site with the URL Notapp.com, where they compared their own guarantee program to Netapp's. According to Simon Sharwood at Search Storage Australia, the site was removed and accessing the URL directed browsers to EMC's site.
Perhaps it is all part of a new marketing strategy by newcomer Jeremy Burton, who joined EMC as Chief Marketing Officer back in March. As best I can tell, Burton's new marketing strategy for the company is that people will believe anything. Maybe he doesn't think there are enough new products coming out of EMC - or that the delays in getting their ballyhooed FAST out the door are too embarrassing - but instead of trying to promote EMC on its own merits, it looks like he is doing his utmost to mud wrestle. Is that what EMC is paying him the big bucks for?
EMC suddenly is taking a bigger interest in 3PAR. That's good. Search Storage Australia just published parts of a competitive document that EMC was circulating to it's partners about 3PAR. It certainly wasn't a surprise because we'd seen it previously, but I was sorry to see it published because it made EMC look ridiculous, which was working pretty well for us. But now that it's been outed, here is what we have to say about it (in the guise of Ineption's lead character, the CRO)
The messaging is not built in, but our zero detection technology for optimizing capacity is. The host SW commands to do this are short and do not require "careful coordination". Veritas, Oracle, Windows Server and Linux software all work with minimal operator effort. For instance, this document from Oracle, describes the whole process, with the sole operator command being this: #bash ASRU LDATA.
Can EMC provide online reclamation of zeroed space without risking capacity overruns and with tolerable performance? 3PAR can. Does EMC have these capabilities in both mid-range and enterprise storage arrays? 3PAR does.
3PAR has both Flash and 1 TB SATA drives. We also have Adaptive Optimization software that uses Flash SSDs for storage tiering. EMC still doesn't have it after they made such a big deal about it last year. They like to tell customers that their size gives them development advantages, but their track record doesn't support their claim.
3PAR arrays allow users to create many tiers, but without the need for disk pools. Tiers are constructed from the combination of drive type plus RAID level. For instance, you can have separate tiers for SATA, FC and Flash SSD drives with the RAID level you select. Our Dynamic Optimization software allows admins to move data from one tier to another. You can "dial in" the performance and protection you want.
All systems have a peak output , ours just happens to have a lot more throughput than theirs - and at higher disk utilizations. We have published benchmarks that show how our systems perform. They don't. Adding disk drives to a system and utilizing those drives is far easier with a 3PAR system than either VMAX or Clariion where you have to wrestle with putting drives in the pools you want to use them for.
There are no disk pools in 3PAR storage. Pools trap resources so you can't use them. Work isolation in pools leads to hot spots and storage admin nightmares. Wide striping does not mean you can't have tiers. That is an idiotic statement.
VMAX can configure large pools - and all the drives in them have to be at the same RAID level meaning you can't create multiple tiers within those pools. If you want multiple tiers, you need multiple pools and all the headaches that involves. Change management in an environment with multiple pools is complicated. You also need to consider the pools needed for snapshots and remote replication. Are those easy to provision and change on EMC storage. Most would say "no".
3PAR uses all disk spindles all the time for delivering IOPS and pro-active sparing is done using reserved space on those drives. Rebuilds do process quickly. Would EMC have you believe they never have to perform drive rebuilds? Really?
Our front end archiecture was designed for large-scale parallel connectivity to match the massive bandwidth capabilities of our wide striped back end. Our benchmarks and the cost per IOPs in those benchmarks speak for themselves. Our customers also tend to run 3PAR systems at much higher disk utilizations than they run other vendor's arrays.
We support a huge number of ports on our systems w/full active/active data access across all controllers. All controller nodes can be used to access all data volumes. We have a number of customers that run fairly sizable SANS without switches because they have enough ports on their arrays so they don't need to consolidate access through switches.
5- 9s? We're there. Our systems get pounded on every day in some of the largest private and public data centers in the world. They are designed with complete redundancy in all components and have advanced capabilities such as Persistent Cache to maintain high levels of performance even after the loss of a controller.
The delays in bringing their FAST tiering software - a product they were hyping in April of 2009 - to market have shown that size doesn't matter much when it comes to delivering technology on time. I'm not saying 3PAR always delivers on time, but EMC is far from immune to these problems. In fact, the need for them to coordinate across multiple product lines creates certain disadvantages for them.
As to their comments on our support; they are pure FUD and grasping for straws. We would not be able to maintain the customers we have if it were not for our efforts at supporting them.
* * * * * *
The following content was added on July 30th by Rusty Walther, 3PAR's Vice President of Customer Services & Support.
Stating that 3PAR “outsources support” is just plain silly, especially coming from a company that keeps most of the worlds’ largest offshore outsourcing companies in business. Like EMC, 3PAR uses Third Party Maintenance suppliers (TPM’s) for break-fix field activities. In some geographies, EMC and 3PAR even use the “same” TPM. But EMC also outsources most of their volume call center
and Level-1 Technical Support to offshore suppliers. Not so at 3PAR. Everyone that touches a 3PAR support case is a 3PAR-badged employee. I challenge EMC to identify a single outsourcing company that handles 3PAR technical support. EMC’s outsourced technical support sub-contractors could be listed alphabetically, by geography, or by technology category … but you’d need a couple of sheets of paper to do it.
Posted at 03:40 AM in 3PAR, Adaptive Optimization, benchmarks, bloggers, clustered storage, customers, Dynamic Optimization, EMC, enterprise storage, flash, INEPTION, mid range storage, multi-tenant storage, Oracle, performance, remote copy, SAN, SSD, storage companies, storage management, thin provisioning, tiering, wide striping | Permalink | Comments (6) | TrackBack (0)
Tags: 3PAR, array, EMC, FUD, Netapp, Netopp, Oracle, RAID, storage, tiering, VMAX
3PAR customers like that fact that 3PAR arrays are so easy and fast to manage. In this video, Robert Cockerill from Thames River Capital in London talks about all the various things he does, his Windows-based infrastructure, how 3PAR's thin provisioning helps him manage it all and how simple it was to protect it with 3PAR Remote Copy.
Virtual Geek and I had a discussion on his post yesterday about vSphere's VAAI capabilities announced yesterday.
I wrote about the fact that we already had zero detect technology in our product, which is useful for the new Full Copy command because it allows customers to remove zeroed data from clones when they are created and return them to array free space.
The discussion became a bit confused when Chad interpreted what I was saying as pertaining to Block Zeroing.
Block Zeroing and Full Copy are different aspect of the VAAI API. The intent of block zeroing is to reduce the amount of CPU effort and storage traffic required to write zeroes across an entire EagerZeroThick (EZT) VMDK when it is created. The intent of Full Copy is to make clones of VMs quickly without consuming I/O bandwidth. Things get interesting when you start thinking about making a full copy of an EZT VMDK that was created using VAAI with block zeroing - but I'll discuss that later.
I also want to clarify what zero detection technology is. 3PAR T and F class arrays have zero detection technology, which is enabled by Thin Persistence software, that recognizes zeroed blocks as they are read by the array and returns them to the array's free pool. Any read requests made to these block addresses will return a zero value. In essence it is dedupe for zeroes.
However, Zero detection is not needed when an EZT VMDK is created using the VAAI plug-in because the array will recognize the intent of the command and not write the zeroes. In other words, the VMDK will only contain a very small amount of reserved space when it is created. Again, any attempts to read blocks in those ranges will return zero values. Zero detection is effectively bypassed during the creation of the EZT VMDK.
The exception to this behavior is when the EZT VMDK being created is written to a thick volume - in that case the array will write zeroes across the entire VMDK.
The remaining cases for the creation of EZT VMDKs on 3PAR arrays occur when the VAAI is not used. For a thick volume, the entire VMDK has zeroes written to it. Thin volumes not using zero detect also have zeroes written over the entire VMDK. Thin volumes with zero detect will not have zeroes written to them and will contain only a small amount of reserved space.
FWIW, the reserved space is used as instantly-available capacity that can be allocated on-demand when writes start coming into the volume. 3PAR arrays always "read ahead" free space to improve the performance of thin provisioning.
The next bit here could be a bit thorny, so clear your head. The matter of making a Full Copy of an EZT VMDK to a thinly provisioned volume was something Chad said was not allowed. My assumption here is that the type of thin provisioning used makes a big difference.
For instance, if you are using TP from VMware, I could see where they would not allow a full copy to be made. The problem is that the full copy will return all the zero values for the source VMDK, whether or not those zeroes were ever actually written - and write them to the target TP volume. In other words, the target could be much larger than the source. In the VMware TP scheme, this could make for problems in a hurry if you were making a bunch of clones this way.
In contrast, if you were using a 3PAR array with zero detection, the Full Copy of the source VMDK would return zeroes for the entire VMDK, but the zero detection would strip them out again as the target was being written. You could make as many clones as you wanted this way, knowing that the physical capacity they consume would be a multiple of the physical capacity consumed by the source VMDK. In other words, you wouldn't have to worry about virtual zero bloat making a mess of your VMFS volume.
One of the big differences between 3PAR's zero detection technology and other vendors zero-reclaim technology is that 3PAR's process is real-time-on-ingestion as data comes into the array, whereas zero-reclaim works in a post processing fashion after the zeroes have already consumed disk space. This could be a significant difference in many cases because the post-processing method has the potential to create unexpected capacity-full conditions before the zero-reclamation process even has a chance to start.
Posted at 02:15 PM in 3PAR, bloggers, clustered storage, de-dupe, EMC, enterprise storage, green computing, mid range storage, multi-tenant storage, storage management, thin provisioning, virtualization, VMware | Permalink | Comments (9) | TrackBack (0)
Tags: 3PAR, emc, VAAI, VMware, vSphere, vSTorage, Zero detect
We've been anxiously waiting for VMware's announcement of vSphere 4.1 for weeks. There are many big things in this release, including significantly scaling the management capabilities of vCenter and increasing the number of simultaneous vMotions that are supported. The door is open for ESX deployments to achieve much greater densities than they could previously and that's a big deal to large enterprises who want to get more resources under the control of fewer points of management. There are still great gains to be made in consolidation - more on that later.
In the storage world, there are a couple big things, SIOC and array integration through the VAAI API. Technodrone has put together an excellent post on SIOC and I highly recommend that anyone wondering how to make this functionality works should go to this post and read it. Array integration has been advanced in three ways:
Array integration through the VAAI API is already at a very advanced status at 3PAR with some of the most important functions implemented through our I/O co-processor ASIC. While some companies want to write off the importance of hardware, 3PAR believes there are many things that need to be done in hardware to get the performance needed to truly scale storage for virtual environments. Our co-processors are key to getting much greater storage utilization and higher VM ratios and are one of the 3PAR innovations that separate our best of breed products from everybody else. The capabilities discussed below are available in the hardware today, and will be enabled with a software upgrade in September.
OK, lets talk about hardware assisted locking first. For customers that have experienced locking problems, this is a big deal. The problem has been well-documented online - but in a nutshell, customers have run into problems where an operation that locked the LUN for a VMFS did not complete, thereby freezing all I/Os for all systems using that LUN. That was certainly a nasty problem - not a bug necessarily, but certainly an incredible pain in the rear to all involved.
VMware's response in vSphere 4.1 was to include a command in the VAAI API using an atomic test and set instruction for implementing fine grained locks for small block sizes. There will still be locking in VMware, but on a much smaller scale.
Unique to 3PAR is the fact that this new locking mechanism is implemented in our I/O co-processors where it completes very quickly, as opposed to implementing it in code in the controller. If you consider an environment with high VM ratios and multiple vMotions going on you want this granular locking mechanism to as quickly as possible. Nobody else comes close to the speed that 3PAR processes them.
Next is the new Full Copy capability - also with co-processor assistance to reduce the capacity of the copy that is made. 3PAR has zero detect and reclaim technology integrated into the co-processor. With zero detection running in an array, as new writes are made, strings of zeros are detected by the co-processor and those blocks are returned to free space inside the array. If future reads are made to those blocks, zero values are returned, but not from disk. The result is that copies of VMDKs with lots of zeros in it, will be much smaller after the copy is made - and the copy will proceed much faster.
This sort of functionality works amazingly well with EagerZeroThick (EZT) volumes in vSPhere. VMware requires EZT for Fault Tolerance (FT) and MSCS clusters and also recommends EZT for high performance. The main complaints about EZT are that it takes extra time to write all those zeroes when the VMDK is created and that it doesn't work well with thin provisioning. With 3PAR's zero detection, the time it takes to writes all those zeros and the space they consume is a non-issue, but more on that later. Virtual Geek at EMC wrote about VAAI today and in his discussion of what does not work for full copy he mentioned copying from an EZT volume to a thin provisioned one. Actually, he's wrong about that where 3PAR is concerned, because EZT to Thin works very well on a 3PAR array with zero detect.
The image below illustrates the advantages of using EZT on a 3PAR array with zero detection:
The last API element to discuss is Block Zeroing. The idea is that the host communicates to the array to write a string of zeros when it is provisioning storage or overwriting blocks to a non-EZT VMDK. vSphere writes a lot of zeroes in order to maintain data integrity with multi-tenancy. The hypervisor zeroes zero out blocks prior to writing them in order to ensure that a virtual data imprint from an old VM does not occur for a new VM.
But writing all those zeroes consumes CPU and I/O bandwidth that could actually be used productively, so VMware included a new command to offload the host from writing zeroes, effectively shunting that workload to the array. Voila - problem solved with 3PAR!! The zero detection and reclamation technology in a 3PAR array not only offloads the host from writing zeroes, but it also gives customers instantaneous reclamation of capacity with a smaller digital footprint (less capacity consumed) and faster performance. That's pretty cool and it's a trifecta that only 3PAR has.
What is amazingly cool about today's vSphere announcement for 3PAR customers is that all three API elements, hardware assisted locking, full copy and block zeroing are already implemented in 3PAR's T and F series hardware platforms, and will be usable by the end of September with a firmware upgrade.
Our co-processor architecture really delivered for us this time. But it's been delivering the goods for our customers for a long time already. In virtualized environments our customers tell us they double their VM density, while cutting their storage capacity in half - all while reducing the amount of storage administration necessary by 90%. Those stats can be hard to believe, but when you look at what we delivered on the first day vSphere 4.1 was announced - when most people didn't even know we were working on it - it might make it easier for people to understand why.
We take virtualized environments very seriously. People that don't know about 3PAR don't consider us to be a leader in virtualization, but when they find out the depth of technology we have and how well it works across our entire product line they understand we are leading in ways that really pay off for them. And the bigger they are, the bigger the rewards can be - especially after today.
Posted at 10:57 AM in 3PAR, bloggers, cloud computing, EMC, enterprise storage, mid range storage, multi-tenant storage, performance, storage companies, storage management, thin provisioning, virtualization, VMware | Permalink | Comments (8) | TrackBack (0)
Tags: 3PAR, array, full copy, integration, locking, storage, vaai, VMware, vSphere
Surprise, surprise. After months after bad-mouthing their competitors for their capacity guarantee programs, EMC has done an about face and has announced their own, very restricted, guarantee program.
EMC offers a 20% capacity guarantee, as opposed to 50% from 3PAR's Get Thin Guarantee program. (FWIW, other vendors have also made 50% guarantees) I guess EMC must be concerned they won't really be able to do it. Also, 3PAR's capacity guarantee applies to EMC customers, but EMC's program does not apply to 3PAR customers. What does that say?(Video note: For readers unfamiliar with #storagebeers, it was an event that started in the UK, by the blogger Storagebod and it has become a meme in the online storage community.)
There were some problems with the links that were posted this week regarding Oracle's ASM Storage Reclamation Utility (ASRU) and 3PAR's Thin Persistence.
ASRU is a stand alone utility that compacts data in a specified Oracle disk group and then frees up space that Oracle no longer needs. Here is a short white paper on it (PDF).
A second joint white paper written by Oracle and 3PAR describes the interaction of both products and gives an example showing how they work together.
Both of these white papers pretty fast reads, without hyperbole and do a nice job clarifying the differences between thin provisioning and storage reclamation.
The ability to reorganize an Oracle database shouldn't have to be limited by the storage structures that database resides on, but its a common problem for DBAs. In addition to the technologies discussed in these white papers, 3PAR's architecture is reservationless, which means storage resources (capacity) are not locked for future use by specific purposes or applications.
Another 3PAR product that database admins find very useful is Dynamic Optimization, which allows data to be transparently re-striped across resources in an array - which is especially useful when adding new drives to an array, adjusting RAID levels and changing the quality of service for a particular volume.