On this occasion we will be covering these new VMAX3 features: FAST.X external storage tiering, FAST Hinting, SRDF/Metro active active remote replication, embedded NAS offering, embedded management, and FlashBoost performance accelerator.
Among the many areas we will be discussing, our experts will answer your questions in regards to best practices, supported configurations, challenges with multi-site replication, as well as consolidation opportunities to combine block and file workloads on VMAX3.
Paul Martin Principal Corporate Systems Engineer - EMC Paul started his career at EMC 10 years ago in tech support working in the OSAPI Unix team. After a few years he continued his career path in the Proven Solutions arena working with Oracle and SAP proven solutions team to produce white papers and proven solutions guides focusing on the integration with EMC products. This involved design, build and test of full EMC SAN environments with the Core EMC technologies, VMAX, VNX, RecoverPoint and DataDomain. He is currently working as Principal Corporate Systems Engineer in the Core Technologies Division VMAX focused.
Matt Acord has been in the IT business for 16 years, 11 of those with EMC. Since he joined EMC he has worked in the PSE lab and was one of the SRDF/A SMEs in the lab and Tech Support. In ESD Matt worked with Tier I partners in configuring their frames, migrating data and keeping them up to date with new EMC technologies. Matt is currently a Principal Corporate Systems Engineer where he focuses on hardware for all the VMAX families and D@RE.
Andrew has been with EMC for 16 years. In that time he has worked for Customer Service, Professional Services, and, for the past 10 years, Symmetrix Engineering. The products that he's currently supporting are FTS, FAST.X and ProtectPoint. Andrew also does a lot of work involving migration strategies and best practices.
Mike has been with EMC for over 15 years and part of the VMAX engineering team for the past 10 years. Mike's areas of expertise include SRDF, ORS, FLM, Access Controls, User Authorization, Host IO Limits, Performance, Databases, Code Development, and FAST.
Harold has been at EMC for 15 years. 11 of those years in NAS (Celera, NS, VNX). The last 4 years in VMAX Product Management with a focus on Embedded Applications and NAS in particular. Worked at DEC prior to EMC.
This discussion takes placefrom August 24th - September 4th.Get ready by bookmarking this page or signing up for e-mail notifications. RSVP to receive a reminder once this event kicks off: https://community.emc.com/events/3412
Share this event on Twitter or LinkedIn:
>> Join our Ask the Expert: The New VMAX3 - Features, Best Practices, Trouble-Shooting Tips http://bit.ly/1TricAF#EMCATE<<
This Ask the Expert session is now open for questions. For the next couple of weeks our Subject Matter Experts will be around to reply to your questions, comments or inquiries about our topic.
Let’s make this conversation useful, respectful and entertaining for all. Enjoy!
Hi team, first of all - many thanks for your participation in creating such a great product as VMAX3, cheers.
I am interested in any embedded hypervisor evolution: as I know, currently Hypermax OS hypervisor offers three types of VMs (Control Station VM, Data Mover VM, eManagement VM). Do you have any future plans or roadmaps for "placing" new services inside Hypermax OS hypervisor VMs?
So I have a question. I was reading this blog: vSphere 6 and VAAI performance boost on VMAX and found the discussion around copying with an extent size of 4 MB interesting. From reading the blog I understand that with vSphere 6 we can adust the values to allow for a maximum extent size of 240 MB. Steps in the blog take the reader through how to make the necessary changes.
Have you tried configuring for a larger extent size on the VMAX or VMAX3 and what have been the results?
with the September 2015 release of HyperMaxOS you can grow/expand devices non-disruptively, the neat thing about this is that you don't need to use any BCV as in previous generations just specify the new size in CYL/MB/MB or TB, a device can grow up to 64 TB with this release. It's easy to do this via Unipshere or with the symdev command in Symcli.
As I mentioned in my blog I did not want to get into the weeds too much but if you read my whitepaper it explains there are only 8 segments available in a command and each one holds 30 MB so 240 MB is the maximum.
SMAS aka Unisphere for VMAX could run on the service processor before (if CE enabled it during install). So what's different now as far as VMAX3 management software is concerned ?
with the September 2015 release of HyperMaxOS you can grow/expand devices non-disruptively, the neat thing about this is that you don't need to use any BCV as in previous generations just specify the new size in CYL/MB/MB or TB, a device can grow up to 64 TB with this release. It's easy to do this via Unipshere or with the symdev command in Symcli.
in response to the embedded management, Unisphere is not running on the SP hardware, it's running in the HyperMax OS as a Guest OS (VM) on the director hardware in the FA emulation. When we run Unisphere for VMAX embedded it runs in a high availability mode so if for any reason a director goes offline we still have all of management functionality and monitoring. I think Harold has highlighted the main benefits already.
slucido
2 Intern
•
109 Posts
2497
0
Posted August 20th, 2015 12:00
Looking forward to participating in this ATE event!