For those who don’t know, EMC AppSync is a product that can provide application-consistent snapshots. In the case of Windows and MS Apps, this means AppSync coordinates an array snapshot, clone, or CDP bookmark to happen at the exact same moment VSS quiesces the I/O within the application on the host. There’s a bit more to it than that, but suffice to say that is the gist of it. AppSync is slowly replacing the functionality of Replication Manager from EMC. NetApp SnapManager products offer the same basic functionality if you’re familiar with that product line.
For VNX customers, there has been a bit of a gap in support for VNX Application-consistent snapshots with SQL server. AppSync did not yet support SQL Server in the 1.0 release, but Replication Manager did not support the new VNX Snapshots, which abandon copy-on-write for redirect-on-write. So, the biggest news with this release (from my perspective) is that now VNX customers can get full application-consistency with SQL Server leveraging the new VNX Snapshots.
Other big enhancements include support for Exchange 2013 and NFS datastores in VMware.
See the release notes for a full list of new features:
For the customers I talk to as part of my regular travels, a frequent request by EMC midrange customers using CX or VNX is an easier way to get high-level performance metrics out of their SAN. For folks who only have a single storage array in their environment, they typically don’t login on a regular basis as they have many hats to wear and a high-quality SAN tends to be somewhat “set it and forget it”. Although the built-in Analyzer tool is extremely thorough, if you don’t use it regularly it can be a bit cumbersome. The good news here is EMC released a product a few months back called VNX Monitoring & Reporting (M&R). This tool is an EXTREMELY cost-effective product that provides the user with an easy to use dashboard with a ton of reports yielding info on array performance (file and block). It is backwards compatible and supported on CX4-based platforms. I’ve even had one customer make it work with a CX3, though that is not supported.
Now, for some of my customers who had M&R and were also savvy with Analyzer, they were noticing a few anomalies in the data reporting between the two products. Those of you who have experienced this will want to upgrade to 1.1 whenever it is convenient.
See below for all the new features of VNX M&R 1.1, and don’t forget you can download the product from support.emc.com and run for 30 days in trial mode. It’s not documented in the download package, so as a tip the default password is admin/changeme. The install is a very straightforward Windows install (i.e. Next, Next, Next, Finish). Then plug in the IP’s of your array and you’re good to go.
Also, for VMware-EMC customers, don’t forget the EMC vCenter plug-in’s. Specifically, the EMC Storage Viewer plugin offers high-level real time reporting on array performance, but there is no historical reporting.
Beginning with this release, a new Data Enrichment feature called
Chargeback is available. Chargeback calculates cost-of-service for
business units and applications in an organization and displays it
in the Chargeback reports. The VNX Monitoring and Reporting
Administrator assigns a cost-per-gigabyte value to LUNs by RAID
type, tier, and array model. Specific LUNs are then associated with
a business unit and application. Total cost-per-gigabyte for each
business unit and application is calculated based on this
Heat Map Reports
Heat map reports are now available in this release. A heat map is a
grid in which metrics that have similar values are grouped together
in order to create “hot” and “cold” areas. These values will be
colored according to predefined thresholds. Unlike other types of
reports, visual thresholds for Heat maps cannot be adjusted.
Reports can now be scheduled to run at specific times and be
delivered as PDFs to selected recipients through email. Whenever a
report is scheduled to be generated, it queries the database for the
Alerts are now available and can be configured to trigger an email
or be captured in an SNMP trap based on when certain
performance thresholds are violated. For example, an Alert can be
configured to trigger whenever storage processor utilization
exceeds 75%. Alerts can also be configured to trigger only for
specific components, such as specific SPs on specific systems. The
Alert email recipients are configurable by alert.
There are six pre-defined alerts available with this release:
• Data Mover Processor Utilization (%)
• File System Percent Subscribed (%)
• LUN Response Time (milliseconds)
• Storage Pool Percent Subscribed (%)
• Storage Processor Dirty Pages Utilization (%)
• Storage Processor Utilization (%)
Regular readers have probably noticed that this blog has been dark for a few months. Life has been busy having been married about 10 months now, and along with that a new career opportunity popped up that was too good to turn down. I have updated my “About” page to fully disclose my new role and employer, which I believe is important to do as everybody has bias in some way, shape, or form, whether we like to admit it or not. What I love about my new role (with CDW) is the opportunity to have significant exposure to a large array of technologies and manufacturers, which allows me to “keep it real” so to speak when talking with customers. That being said, there are technologies that I don’t get much exposure to. Additionally, though I go thru training and maintain accreditation/certification in a wide variety of storage technologies, like anyone I can tend to gravitate to what I know best, which dates back to my years as a storage administrator/architect.
So, with that being said, let the blogging resume, albeit at what will probably be a somewhat slower pace as life just keeps getting busier and time keeps flying faster.
One of my work colleagues (Mike Ellis @v2mike) and I have been keeping track lately of any and all storage companies that have a name starting with the letter N. Whether it is purely coincidence or something else, I have yet to figure out. But, it is quite interesting how many companies have picked this letter to start their name. Any conspiracy theories out there?
Netgear (a bit of a stretch)
If you come up with any others, please comment and I will get it added!
Nick and I troubleshooted this issue for a client back in December. He beat me to the punch on blogging about it 🙂 This was the first time I had heard of heap size, and I hope it’s the last!
I’ve commented before that “Unified Storage” as a differentiator is no longer the differentiator it once was, given the fact that virtually all major storage vendors are now offering a “Unified” product. Previously, only EMC and NetApp offered a true Unified storage solution. Now, IBM has SONAS built into the V7000, HP is building IBRIX into their products, HDS released the HUS platform that leverages BlueArc NAS, and Dell also is integrating Exanet into their products.
However, it’s important to note that not all Unified storage products are the same. Just because a manufacturer can “check the box” on a spec sheet that they have NAS doesn’t mean all NAS products work the same. On a related note, now that EMC has acquired Isilon, which many perceive to be a superior product to Celerra, the rumors are always going around about when will VNX File be replaced with Isilon code on the VNX series.
I’m here to tell you that:
- EMC and NetApp are still best equipped to fulfill the needs of traditional enterprise NAS use cases compared to any other vendor.
- I don’t believe Isilon will replace VNX File (Celerra) anytime soon.
- While Isilon, SONAS, IBRIX, etc are superior for scale-out use cases, that’s not the case for traditional enterprise NAS requirements.
Why is this the case? First let me clarify, when I say traditional enterprise NAS requirements, I’m talking large enterprise, as in tens of thousands of users. For a smaller shop, these don’t apply. Here are some sample requirements:
- Support for hundreds of file systems and/or mountpoints (much different than the big-data use case people talk of today involving a single file system that scales to petabytes)
- Large enterprises have dozens if not hundreds of legacy file servers. Wouldn’t it be great to consolidate these or virtualize them behind some file gateway? Sure! Is it realistic in a huge environment with thousands of custom applications that have hard-coded UNC paths to these locations, immense user disruption and re-education, etc? Not really.
- Robust NDMP support
- Large enterprises may be using advanced features of NDMP such as volume-based backup and checkpoint/snapshot based NDMP backups. Do all scale-out NAS offering support these? I don’t know to be honest but I’d be surprised.
- Number of CIFS sessions
- Handling 20,000 users logging in each morning, authenticating against AD, downloading user/group SIDs for each account, and handling drive map creations for each user that may be part of the login script is a unique requirement in its own right. It’s very intensive, but not from the standpoint of “scale-out” processing intense. Being able to open all these CIFS user sessions, maintain them, and potentially fail them over is not what scale-out NAS was designed for.
- Multiple CIFS servers
- Same point as above under multiple file systems. It’s not necessarily so simple for an organization to consolidate tens or hundreds of file servers down to one name.
- Multi-protocol support
- Scale-out NAS was not designed for corporations that have invested a lot in making their traditional NAS boxes work with advanced multi-protocol functionality, with complex mapping setup between Windows AD and Unix NIS/LDAP to allow users to access the same data from both sides with security remaining intact.
- Most scale-out NAS boxes offer snapshots, but make sure they are Shadow-Copy client integrated, as most large organizations let their users/helpdesk perform their own file restores.
- Advanced CIFS functions
- Access Based Enumeration – hides shares from users who don’t have ACL rights.
- Branch Cache – increases performance at remote offices
- Robust AD integration and multi-domain support (including legacy domains)
- Migration from legacy file servers with lots of permission/SID issues.
- If you’re migrating a large file server that dates back to the stone age (NT) to a NAS, it most likely is going to have a lot of unresolvable SIDs hidden deep in its ACL’s for one reason or another. This can be a complex migration to an EMC or NetApp box. I know from experience Celerra had multiple low-level params that could be tweaked as well as custom migration scripts all designed to handle issues that can occur when you start encountering these problem SIDs during the migration. A lot of knowledge has been gained here by EMC and NetApp over the past 10 years and built into their traditional NAS products. How are scale-out NAS products designed to handle these issues? I am hard-pressed to believe that they can handle it.
The reality is that EMC’s Celerra codebase and NetApp’s ONTAP were purpose-built NAS operating systems designed to deal with these traditional enterprise requirements. SONAS, IBRIX, BlueArc, Exanet, and Isilon were not. These scale-out products (which I evaluated many years ago at a former employer and even had the opportunity to watch SONAS be developed and productized) were designed for newer scale-out use cases, often involving High Performance Computing (HPC). In fact, HPC was the sole reason my former employer looked at all of these excluding Exanet. Many of these products use SAMBA to provide their CIFS support. Isilon was just recently switched to a more enterprise-class custom CIFS stack. SONAS definitely uses SAMBA because it was built upon clustered SAMBA. HPC has completely different requirements for NAS than traditional corporate file sharing, and so companies that built products focused on the HPC market were not concerned about meeting the needs of corporate file shares.
Now this is slowly changing, as we see more traditional enterprise features being built into the latest Isilon “Mavericks” code release, particularly around security. I’m sure the other vendors are rapidly making code modifications as well now that they’ve all picked the NAS technology that they will make their SAN’s “unified” with. But it will take time to catch up to 10 years of complex Windows permission and domain integration development that Celerra/VNX and NetApp have as advantages on their side. From a quick search, it appears Isilon does not support MS Access Based Enumeration, so to think that EMC is going to dump Celerra/VNX code and plop in Isilon code on its Unified storage arrays is silly, when there are probably thousands of customers using this functionality.