[music] Howdy y'all and welcome to another session of the CS seriesWe've got him again, subject matter expert extraordinaire, technical product manager Chris Luth. >> Oh Jamie, thanks for the kind words and you know I'm excited to be here with you again.>> [snorts] >> [snorts] >> [snorts] >> So, uh, on the last video, if you've been following along, wetalked about the sustainability of the series systems, and today we're going to focus on the scalability. So, last time we talked about QLC, giving you a little bit more of that acronym S quad level cell media. Um, Chris, what more can you tell us about how these systems are primed for helping our customers scale their environments? Yeah. So, you hit the nail on the head, Jamie, when you talk about the quad layer cell QLC media that we use on the C series. Um, it's a very dense SSD uh in terms of capacity. How dense, you ask? 15.3 terabyte per SSD. That's what helps drive that scalability story in a very small amount of rack space. You don't need a lot of rack space toreach scale out capacities. But the other thing about that T-series system is customers have asked well okay it's great this QLC media um but is it standalone and that the answer is no it runs on so it plugs into existing clusters uh be it a series be it fast hybrid systems so it just plugs right in and it gives you the capability to have storage taring across three different performance levels within that same cluster basically you put the data on a storage tier that best suits the data your application needs uh and at the same time might be more cost effective than all flash uha series system. So if you know NetApp, you know we have unified systems. Wehave dedicated NAS. We now have we have dedicated SAN. Right now we're talking about the interoperability of the C series, the A series, you know, we have TLC, QLC, hybrid on's doing it all. Um so great input there, Chris. When I think about scalability, I'm thinking about starting small and then having the flexibility to get massive. Um, you know, business needs change over time. So, what are some of the capacity points of the C series systems? >> All right, Jamie, or you're going to like the answer here. So, the C250 and C400 starting capacity is eight of these GLC drives. And to do the math for you real quick, that's 122 terabytes of capacity as your entry starting footprint. The C800 on the other hand's minimum number of drives is 12. So this capacity goes up uh some to 184 terabytes for an HA pair. Now on the other end of the spectrum there, the C250 can scale up to 734 terabytes on an HA pair. the C400 up to 1.5 pabytes on an HA pair and then on the C800 up to 2.2 pabytes once again on an HA pair. Now that's on HA. What happens when you factor in cluster scale out and in that case the numbers explode. So the C250 will now scale up to 9 pabytes just under nine pabytes. Uh 7.6 pabytes on the C400 and the C800. This is old news, but when we launched it was 26.4 pabytes. Once we launched the C series, we received quite a few requests to increase the capacity point on the C800 and we were able to do that uh in short order and start quoting them immediately. As a result, when you scale out a C800, you're hitting 3.7 pabytes on an HA pair with the higher spindle, higherSSD count. But then on the upper end, uh, 144 pabytes in a scale out C800 cluster. >> All right. And folks, don't worry. Wehave this information recorded elsewhere if you couldn't remember all those facts and figures. Chrishas it uh just stored right up here. But for everybody else, you can check out the data sheets on the website. I heard 122 terabyte starting capacity for that C250. And if I'm not mistaken, I believe that's one of the lowest starting points for a capacity flash system in the industry. So, you know, making it more accessible to more customers. You taking that downstream.I want to go back to that storage taring in a cluster. You talked about how it provides customers benefits mixed scale out. You know, we have this opportunity. Can you spend a little more time there, Chris? Yeah, you bet. So what we've seen for some time in uh customer cluster systems is storage taring using the uh A series system or ourperformance flash system and hybrid faz which is the hybrid uh faz system thatthose two extremes right you either had highly performant very low latency uh storage available to your application or you had you know something that's slower or yeah, just to put it in perspective, you go from sub millisecond latency on a performance flash system, the A series to something like 10 milliseconds once you have NL status drives or even 10K status drives. It's kind of a little bit extreme. So, you know, and it probably presented some challenges the tiering like, you know, super fast or kind of fast. Well, the way C series plugs into that, Jamie, is it gives you sort of like a middle ground. You know, may maybe the applicationum you know, as it matures or the development work as it matures could live on slightly slower, uh storage. In this case, the C series could be a great fit. And then as data ages out even further, then you might tear it off to the slower spinning uh hard drives. I should point out that if you're wondering, okay, that's great, but what's the disruption going to be inside of clusters, this non-disruptive um activities like moving volumes across these tiers? Non-disruptive.So, you'll never know what's happening other than at some point these application data will be on a different uh storage tier. >> All right, thanks for the uh the additional piece there. It sounds like the C series fits really nicely between the A series and Faz lines. We've talked a lot about the greatness of the C series, but are there any tradeoffs or limitations when it comes to the features and functionality with respect to thescalability story? You know, what can you tell us about uh any sort of limitations where a customer could deploy it? Oh, you know, wecan take the uh short answer of nodifferences, Jamie, but let'sbuild out on that uh a little bit. So, it's a great question, by the way. But, uh you know, there's no trade-offs on the C series. It's ONTAB. Um it has the same limits as its counterpart A series system. So, there's no trade-off there. What about protocols? You know, which protocols does it support? It supports all the same protocols as the A series. um be it uhSAND, NAS, be it NVMe over fabric, it supports the full payload ofprotocols. And then finally, okay, less good deer, but what about application uh tiers? You know, it support tier one, tier two type applications. Tier one tend to be more mission critical. Um the answer is yes. Itsupports tier one, tier two, sand, all the protocols. So, no trade-offs at all. Jamie, >> you love to hear it. The C series being a comprehensive solution, filling a nice gap between that Faz and A series at a great price point, no software limitations. So, I'mnot seeing any downside. Sounds like an easy decision to me. Andspeaking of software, next time I'm going to be bringing on ONTAP product manager Keith Aen, who's going to give us some details on how we're simplifying the purchasing experience and providing customers with everything ONTAP has to offer. Put an emphasis on everything. So, tune in next time to learn more. We'll see you then.