Modern Data Protection Made Simple – Why Is The Internet Broken?

Justin Parisi: I’m here in the basement of my house and with me today, I have a couple of special guests to talk to us all about NetApp Backup and Recovery Services. So with us we have Manohar Kulkarni. So Manohar, what do you do here at NetApp and how do we reach you?

Manohar Kulkarni: Hey Justin, thanks for having us in your show. I’m Manohar Kulkarni.

I’m a senior technical marketing engineer. Part of a data service product team and I predominantly work on creating solutions and content for databases and virtualization in NetApp backup and recovery space. You can reach out to me on the NetApp email ID [email protected], and I’m also available on LinkedIn. So if you do a search Manohar Kulkarni and more refined search with NetApp, you’ll always find me on the top of the list.

Justin Parisi: Also with us today we have Ebin Kadavy. So Ebin what do you do here at NetApp and how do we reach you?

Ebin Kadavy: Hey Justin, thank you for including us in the series.

I’m Ebin Kadavy, product manager for NetApp backup and recovery service, as well as SnapCenter. So I focus particularly on enterprise databases and virtualization. Everyone can reach me at [email protected] for any queries, any questions around product or services.

Justin Parisi: Alright, so like I said, today we’re covering NetApp backup and recovery service, and that’s not what it’s always been called. It’s been called something else in the past. Ebin, what was NetApp backup and recovery service before and what has it become?

Ebin Kadavy: Yeah, I think that’s a great question. In the past we had numerous names. NetApp Backup and Recovery Service is part of NetApp console. So NetApp Console is a control plane to host multiple protection services.

That includes backup and recovery, disaster recovery, and ransomware resiliency. So there are more services. I just want to focus these three in today’s discussion. In the past the console was named Blue XP. In the past it was called Cloud Manager. The service has also changed. In the past, we call this cloud backup service. Then eventually it was called Blue XP Backup and Recovery. And now we call it NetApp Backup and Recovery.

Justin Parisi: Yeah, it makes a lot of sense. It tells you exactly what it does. And you’re not guessing what Blue XP is anymore, right?

Ebin Kadavy: Yeah, that’s right.

Justin Parisi: That said, what exactly does NetApp backup and recovery services do?

Tell me a little bit about the value prop and the pitch for what it is and why people would want it.

Ebin Kadavy: So NetApp backup and Recovery, it’s completely a managed service offering from NetApp. I think the good part of our service is that it provides you a secure 3-2-1 backup.

Today, 3-2-1 backup is the industry standard for backup, where you have three copies, with two copies on different media, and one copy being at offsite. So in the past we had SnapCenter and other snap products where we used to support only backups between your ONTAP primary and ONTAP secondary.

Or it could be ONTAP primary to CVO or it could be a CVO to CVO, but it never supported long-term retention. Where if a customer wanted to retain backups for their compliance needs, like seven years, 10 years, 15 years of backup, I think that story was not there. Now with NetApp backup and recovery customers can protected their database, VMs, containers, and the nas for a long-term retention following this three 3-2-1 principle.

So that’s one of the coolest part. The second thing is being a managed service unlike traditional softwares, customer doesn’t have to manage on their own. That means upgrading whenever the new versions are available. So these things are not needed because you don’t have to manage the backup infrastructure. So NetApp is managing the backup infrastructure for the customers. I think that’s one of the coolest thing because traditionally the admins have to take the risk.

They have to take a backup before they perform something, and if something screws up, they need to roll back. So now nothing is needed. You are running always at the latest and the greatest when you run on the managed service offering.

Justin Parisi: When you talk about upgrading when it’s done in a cloud resident nature, is there any sort of disruption that happens when you upgrade or when we upgrade? ’cause we’re managing it. So if I’m taking a backup as a customer, does it start an upgrade while I’m taking backups or does it wait for opportunistic moments?

How does that process all play out?

Manohar Kulkarni: Yeah, that’s one of the great point with NetApp backup and recovery. Since NetApp is managing the backup infrastructure for the customer, all the microservices would be running within the customer environment, and whenever there’s an upgrade process happen, it is seamlessly managed wherein any microservices or the image or container that is running within the NetApp agent is replaced with a different container that we provide you the upgrade. And that is done seamlessly. Customer doesn’t have to run a separate upgrade process or have to plan the upgrade lifecycle, whatever. There is a new patch that gets released. We take care on the behalf of the customer.

Justin Parisi: Okay, that’s good. So then they don’t have to worry about disruptions because someone else is managing their stuff.

And that’s I guess, one of the main things that people would be worried about. Another that might be worried about is the security aspect. So how are you presenting customers with this idea that their backup software is secure in the cloud?

Ebin Kadavy: So the architecture is pretty interesting.

Unlike other cloud services where an external entity may have an inbound connectivity to the customer objects, right? For example, the console comes with a connector or we call it as agent. So it may need inbound connectivity to the agent, and then it has to have a connectivity to all our services, all the storage databases and VMs.

But that’s not the case with the NetApp console. I think the console is unique in that way. It doesn’t require an inbound connectivity from the SaaS to the customer’s network. It is always outbound. So the connector always interfaces between the customer’s infrastructure versus the SaaS.

So it has outbound communication and it always does some kind of a long polling from the SaaS from the console. And then it takes the action into the customer’s infrastructure. For example, if a customer tries to do something with a backup and it is stored in that message queue. And what happens is the agent which always does the long polling, it sees matching messages and forwards the actions to the respective components like plugins of NetApp backup and recovery. So it’s pretty secure in that way. And the second thing is we follow all the industry standard to ensure that data is always encrypted at rest and in flight. So that’s a basic standard things that every SaaS products should follow.

Which we are following it all together. And the third thing is, we have different layers of communication, but indirectly there is lot of things that has to cross through to even come down to the customer’s environment. And the customer’s data is never moving out from their data center or from their VPC or vnet to the cloud. Always the customer’s data is preserved in their own storage. So I think that’s the beauty of snapshots, right? Unlike any other backup softwares, they may pull the data from the customer’s host or from the storage, and then they move it to another destination. In the case of NetApp, we always rely on snapshots. So your customer’s data is always on the snapshot, and the snapshot is just simply replicated between the different storage systems, secondary and tertiary. So that way the customer data is never moving out from their environment to the cloud.

Justin Parisi: And does NetApp backup and recovery service leverage other security features, say autonomous ransomware protection at all? Or is that kind of baked into the ONTAP infrastructure?

Ebin Kadavy: We have NetApp Ransomware Resilience separate. It’s part of the same suite which offers ransomware protection for the customers. So it depends on autonomous ransomware protection provided by ONTAP. In addition to that, it can do much more stuff but yes that a backup is not involving in it because it focuses only on creating snapshots and it allows you to lock your snapshots using snap lock. So that’s the minimum thing that we offer in backup and recovery. While ransomware resilience can offer much more in terms of scanning the real time data and providing insights or providing ransomware alerts from that service.

Justin Parisi: So I guess ransomware resilience would be a separate service you’d purchase in addition to this?

Ebin Kadavy: Yes, that’s right.

Justin Parisi: Okay. So Manohar, when customers are looking at this solution and they start to realize that they can’t use it without being connected to the cloud, and I’m talking specifically about customers that are interested in dark site how do you handle that? Is there a way to leverage NetApp backup recovery service without having to interact with external networks and clouds?

Manohar Kulkarni: So the way the architecture is built on the cloud platform, we only collect the metadata information which is to orchestrate the backup scheduling of backup.

It is all managed from the NetApp agent, which runs within the customer VPC. It could be either on-prem or in the cloud. So all the backup process, job, they’re all executed from NetApp agent. The requirement is to have the NetApp console agent connecting to our SaaS platform because we are able to efficiently manage the backup infrastructure for the customer. Whenever there is an upgrade, we can push for the upgrade within the NetApp agent. And if immediately any support is required for a particular feature within the database product or virtualization product, we can push it and customer can get that support in a few releases instead of waiting for months to get it upgraded and then start protecting a certain resources. So that’s something in the roadmap, if the customer is looking for a complete on-prem solution. But as of now, it is a requirement for NetApp console agent to be available on-prem, which should be connecting to our SaaS platform. So that’s the current requirement.

Justin Parisi: Okay. Makes sense. So when you’re talking about backups and recovery, there’s also some other, pieces that you might want to have insights into, such as capacity you are using or storage efficiencies or performance. Do you provide that sort of data sets for these backup and recovery solutions, or is that something that’s offered as an external as a service offering?

Manohar Kulkarni: So as far as the capacity is concerned, we have a dashboard wherein we give the detail like how many resources are being protected and what is the protected capacity. So those information are available in the dashboard across all our workloads that we currently support, such as in the virtualization for VMware, Hyper V, KVM.

Similarly for the database we are for SQL Server, Oracle, and volumes.

Ebin Kadavy: With respect to the backup thing, I think it’s more important to save in terms of time and cost. So when it comes to time, I would say snapshots are super efficient in terms of a customer getting a quick application or VM consistent snapshot. I think that’s the cool part which none of the other streaming solutions can offer. In addition to that it’s also being at the. Being space efficient, so the snapshots, when we are replicating to a different storage or to a object store, the efficiency in the primary is getting reflected in secondary as well as in the object store. So they get the same storage efficiency being replicated across the board. So that’s one of the cool part. The third thing is since we support features like flex clones and snap restores, we are not really hydrating the entire data. Especially with Flex Clones customer can create multiple copies of their production for the dev test, the QA analytics, and even for AI use cases as well.

And it’s going to be near a hundred percent efficient and it’s very instantaneous, right? And in addition to that if he’s performing a restore from an object store or from a secondary storage, we are not really pulling the entire data from that storage to do a restore.

We know what has changed, and we are just doing the restore for that delta, not the entire data is being pulled out from the storage. All this means we offer the best RPO/RTO in addition to the space efficiency that we guarantee as part of using our snapshot technology.

Justin Parisi: Yeah. And I get that what I was asking more of is do we show our work, right?

Do we show the dashboard saying you’ve saved this much capacity with efficiencies, or your backup took this long, or it did this many megs per second or gigs per second. Do we show any of that sort of information in the dashboard, or is that something that’s just not been asked for or on the roadmap at all?

Ebin Kadavy: Yeah, a few of the things are there in the roadmap. Otherwise we are showing the space efficiency. So we are doing a space efficiency chart. We have attractive stuff that shows how much you are efficiently saving by running on snapshots, as well as if you are doing with clones how much you are efficiently saving.

So we have a separate widget that shows the space efficiency part well. How much percentage of space, efficiency and few other things which are coming up in the roadmap. But yes, so we have something that, that is very valuable for customers that we do today. Yeah, absolutely.

Justin Parisi: So let’s talk about scale.

How much can we actually back up with this? How many clients can agents run? What sort of scale are we looking at with NetApp and backup recovery servers with each instance?

Manohar Kulkarni: Currently we have tested a scenario where you can back up more than 20,000 VMs from a single agent that we have right now. Our engineers are testing in the background with more than 40 or 50,000 databases running across these 20,000 VMs. So it can scale not only vertically, but no, there is a roadmap plan where it can also scale horizontally when the need comes, if the customer increases their infrastructure to go beyond, 30, 40,000 VMs. They can efficiently scale their agent because agent is the one through which all the activities are managed for backup, to restore, to clone operation. So everything is managed from the NetApp console agent. So we have a capability where it can scale up vertically and in the future roadmap, we also plan to do it horizontally.

Ebin Kadavy: Adding to Manohar’s point, we have sizing guidelines for agent. What’s the small configuration look like, what’s the RAM, CPU and what kind of scale you can expect with that configuration. So you can pretty well refer that scale guidelines and make sure how many agents you want to deploy based on your infrastructure.

I think that is very clear from this documents.

Justin Parisi: So with that kind of scale, how are we licensing this? Is this licensed per seat? Is it licensed per backup? Is it licensed per capacity?

Ebin Kadavy: So the NetApp console platform is not being charged on the customer because the agent is the only component that runs inside the customer environment.

And agent is nothing other than the vm, right? So customer has to provide that infrastructure to host the vm. The licensing is one only applicable for the services. For example, if he’s hosting NetApp backup and recovery service. So we charge on the front end capacity that is getting protected. It’s not on the primary snapshots. I would say only when you protect the snapshots to a secondary destination, and that’s where we enforce the licensing. Whereas if you have, okay. ONTAP, primary, secondary, and object store. So when you move the first needle, right after you take the snapshot, you replicate it to a secondary.

It could be even object store or secondary ONTAP. I think that’s where we expect that customers should have the license for those data that is getting protected. And it depends on the plugins. Since we support a lot of workloads we have support for nas we have support for VMware Hyper V KVM which are like VMware alternatives.

And in addition to that, we have OpenShift Oracle mssql. So these are the workloads that we support. So depending on the workloads we have a mechanism, how we charge it. For example, if you are using a database like SQL or Oracle, and if you want to see how the pricing works, it’s pretty simple.

It’s just the front end use capacity of that database, not the volume. For example, if you have a database DB one, and if the size is say 50 gig on a volume of one terabyte we charge 50 gig and you’re not charging the entire one terabyte volume because you’re not backing up the entire one terabyte volume.

You’re just trying to back up only that database, which is 50 gig. So we have similar stuff for VMs and other cases. And compared to the TCO side of the world, if you see we are much more efficient because of this, because we are not charging, unlike other vendors where they charge on the very first backup. When a customer protects the critical data to a secondary storage, that’s where we start charging them.

Justin Parisi: And do you also charge on restores, or is that included in the backup?

Ebin Kadavy: The restores and Flex Clones unlimited. No doubt about it. It’s free.

Justin Parisi: And what’s good about the FlexClone is you’re not actually incurring capacity costs there, right? Until you start to change it.

Manohar Kulkarni: No, it’s only based on the resource that we protected. So even if they take n number of clones or even someone is trying to protect a clone, it is not charged. The customer won’t be charged in that situation.

Justin Parisi: So you mentioned a lot of application based backup type of things, and that makes a lot of sense. But I guess the question for me is it just when those applications are hosted on NAS or is it also block

Ebin Kadavy: We support both NAS and SAN. Again, it is depending on the workload.

So like I said for databases and VMs. When I say VMs, it includes VMware so sql, Oracle, VMware, we are supporting NAS and SAN and with respect to OpenShift, Kubernetes, and, the volume which is pretty much NAS focused. So these are all NAS focused. We are planning to add more workloads in the coming future. So right now we have covered pretty much the top workloads used by most of the customers. And so to your questions, particularly SAN is supported for both databases and VMware as of now.

But yes, we’ll support SAN for hyper-V, KVM in the coming roadmap.

Justin Parisi: So when we’re talking about block versus nas, there’s often this idea of file system consistency where the OS communicates with it to quiesce whatever in flight operations are happening.

So basically, crash consistent versus application consistent. And does NetApp backup and recovery service interact with those OSes and applications to ensure that consistency? Or is it just basically all or nothing?

Manohar Kulkarni: Yes, it does, especially when it comes to database. It is very critical to ensure when we take an app, consistent backup, many a times for performance reasons and manageability reasons since the database size have grown so large that the database files are spread across multiple LUNs, and when we take a backup, we ensure it is a consistent snapshot and the way we do it. If I take SQL Server as an example, Microsoft SQL Server provides an API, wherein first requires the database wherein the IOs are stalled for a few seconds, and in the background they quickly take a snapshot across all the volume, and once that is done, we release the IO and the transaction continues as it is. There won’t be any disruption as such.

Similarly, when it comes to Oracle, it there is a slight change the way it is managed. Sometimes we do use consistency group capability, the CG commands from the ONTAP to take an consistent snapshot across multiple volumes. So that intelligence is all built into NetApp backup and recovery when it comes to taking an app consistent backup.

Ebin Kadavy: Yeah. The same applies even for VM consistency. The VM consistent snapshots would help them to do that. And in fact, if you have any applications on top of VM and if a customer enables VMware consistent snapshots and of course he’s getting a completely consistent snapshot that includes both VM as well as the application running inside the vm.

Justin Parisi: Makes sense. As far as interoperability with NetApp products goes, I’m gonna go through a list of products and you just tell me yes or no if NetApp backup and Recovery Service works with it. And if there’s like a caveat or something, feel free to mention that. But we’ll start with Unified ONTAP.

Just regular ONTAP. I’m guessing that’s a yes all the way, right?

Ebin Kadavy: Yeah.

Justin Parisi: All right. StorageGRID.

Ebin Kadavy: Yeah. Maybe I can quickly justify on why StorageGRID. StorageGRID would be used as a target for backup. If the customer want to protect snapshots from their ONTAP primary or even from secondary to a tertiary. For long-term retention, they can use StorageGRID as a medium to protect.

Justin Parisi: Alright. E-Series.

Ebin Kadavy: No.

Justin Parisi: And I’m guessing not even as a source, right? You can’t even back that up or as a destination, like a BeeGFS destination?

Ebin Kadavy: Yes. We haven’t supported ESeries as a source or as a destination yet.

Justin Parisi: Okay. ASA.

Ebin Kadavy: So we have ASAr1 and r2. ASAr1 as a source as possible, because it’s more or less the same as AFF.

But a ASAr2 in NetApp Backup and recovery is yet to be supported.

Justin Parisi: Okay.

Ebin Kadavy: I don’t want to say r2. It’s the new ASA model. Yeah.

Justin Parisi: Yeah. The disaggregated ASA, basically. Yeah. So it’s the disaggregated ONTAP version of that, which brings us to AFX of course. So disaggregated, ONTAP AFX. What about that one?

Ebin Kadavy: Yep, that’s right.

Justin Parisi: That’s just NAS. We always tout it over there as it’s just ONTAP, so it’s really just ONTAP just a different way of consuming it. Alright, so let’s get into like maybe non NetApp targets. Could, do you support any of the non NetApp targets?

Ebin Kadavy: We have supported in terms of object stores, not for the source as a target.

As a target, you can copy backups to AWS S3, Azure Blob and GCP.

Justin Parisi: So the requirement has to be S3.

Ebin Kadavy: Yeah, it has to be S3 clients. Okay. And in addition to these, the familiar cloud and NetApp based object stores that include storage grid and ONTAP S3, we have done a previous support for limited workloads from Min.Io and Wasabi.

So if they want to protect to any other S3 clients we have given a limited preview support right now, and if customer are interested, let us know so we can also extend support for other S3 clients.

Justin Parisi: And what if you want to use a NAS protocol to dump a third or tertiary backup to? Is that supported with NetApp Backup and recovery service, or is that something you have to do on your own?

Ebin Kadavy: Right now we don’t have, I think we got some requests. We’ll assess on this and we’ll get back.

Justin Parisi: Yep. And this is more about what you do and do support, not so much as trying to show limitations of the product. There’s certainly a lot there already. And I know that you’re working on a lot of new stuff.

What about Metro Cluster?

Ebin Kadavy: Yes. So we support MetroCluster as well as SMAS, ActiveSync. So all the synchronous solutions are being supported right now.

Justin Parisi: And business continuity, does that also interact with that?

Ebin Kadavy: Yep, that’s right.

Manohar Kulkarni: You mean SnapMirror ActiveSync?

So that is supported. We have qualified it wherein, whenever customer flips their database from one site to another site, NetApp backup and recovery is aware of which one is a primary, and then it takes a backup from the new primary role in that SMS topology.

Justin Parisi: Okay.

Excellent. So we covered what sort of NetApp portfolio products are supported or not supported, and if you support third party now, what if I want to start using it? What’s the easiest way to go about that?

Manohar Kulkarni: So first step is to getting the NetApp console agent deployed within the environment. I know many of the customer already have it, but after that, the steps are easy.

They don’t have to install any appliance after that. They just have to go to NetApp backup and recovery Service under NetApp protection. And over there, they just have to choose the workload, which they want to protect. And once they select it, they just need to, activate a trial license. We offer 30 days trial license for most of the workload.

They can start evaluating it. And with this evaluation, there is no restriction. It has an unlimited capacity. So even if they have, terabytes of data that they want to protect and try it out, how efficiently they can backup, they can start using it immediately. So it is just a matter of enable it and start using it.

Justin Parisi: What happens after that 30 days?

Ebin Kadavy: Yeah, so after the 30 days I think it’s pretty simple. They have to request license. I would say we should not do towards the 30 day period. Now, if they want to extend the testing they can request for an evaluation license. Beyond 30 days, and we are ready to help you out.

It’s not like a hard limit from our side. And now how can you license? If you ask me in that way, we offer multiple ways. One is they can get from the marketplace in AWS Azure and Google. We offer private offers. Customer can get private offers like one year, two year, three year offers.

And apart from the paygos, and if they’re not. Having a marketplace integration, they wanna buy separately from NetApp, whereas we offer BYOL. So bring your own license. So you can again, quote it for one to three years. So as you buy for more years, you get a very great discounts. And that helps you to save more when you lock it for a longer duration.

Justin Parisi: And you mentioned the three major cloud providers. Is there a plan to include, say Ali Cloud or maybe some of the NCPs out there to have a more wide array of clouds you can choose from?

Ebin Kadavy: Not at this moment but if there is a request and if there’s an interest we can definitely look at it.

Justin Parisi: Earlier you mentioned that you can back up a lot of VMs, and of course that kind of gets people thinking more and more about who services those VMs. You have Hyper V, you have OpenStack, and you have OpenShift, and then you also have VMware, of course, which is, probably the largest provider of these VMs.

Now, there are a number of people that are looking for alternatives there. How is NetApp backup and recovery service enabling that sort of use case?

Ebin Kadavy: Yeah, I think that’s a great question because many customers these days have different solutions to have their infrastructure hosted. And like you said, VMware is our largest base. Many customers do have other platforms like Microsoft Hyper V, KVM and OpenShift. So these are the other common platforms that we see. In the past we never had a solution, like in SnapManager or SnapCenter. We didn’t have a strong solution. We had something for Hyper V, but it was not a detailed out solution. Now in NetApp Backup and Recovery, you get complete 3-2-1 support for all these platforms. And then anyone who is interested looking into alternatives apart from VMware, definitely they can reach out to us. We can help you get started.

Justin Parisi: So when you’re talking about VMware and people moving away from VMware to go to other places or moving from any virtualization platform to go somewhere else, does NetApp backup and recovery service aid in that migration, or are we just simply there in case you need us for backup?

Ebin Kadavy: So we have different tools right now, especially within NetApp we have Shift, which also helps customers to move, or if they want to transition from VMware to other platforms, they can leverage Shift. So we can definitely guide them. So that’s not a problem. We can always guide the customers how they can use different tools to migrate their existing infrastructure to a new one.

And on top of it, once they have migrated now we have stories from the backup side, so you don’t have to worry. We can protect you, we can safeguard your estate. And in fact, we are also trying to extend these capabilities to our different product lines as well, like disaster recovery as a service and other mediums where you can also have seamless dr for your new infrastructure. If you want to migrate from SnapCenter, you can use it today. So there’s a migrate option in NetApp Backup and Recovery that helps you to migrate from SnapCenter to the new NetApp Backup and Recovery.

So it’s a non-disruptive migration and it’s a single click. You don’t have to take the hassle of understanding the estate, the policies and all that stuff. We clearly understand what is there in SnapCenter and we can nicely bring that data all the metadata into the new backup and recovery. So when you start your one click migration and the next backup will start from the NetApp backup and recovery, while your SnapCenter schedules will be passed after doing that. So customers who are using SnapCenter. This is a great chance for you to try NetApp backup and recovery for these modern features that we offer today.

Justin Parisi: So shift, if you’re not familiar with that’s the virtualization, I guess the VM conversion, right? The being able to convert a VM for one platform to another. Is that accurate?

Ebin Kadavy: Yes, that’s right.

Justin Parisi: Yeah. So have you ever had a customer ask, can you use shift on all my NetApp backup and recovery service backup, so convert all my backup VMs to another provider.

Has that ever been asked? Is that something that’s even possible?

Ebin Kadavy: That’s an interesting question. As of now, we have noticed that most of them are focused on the transition part. We are yet to see how they want to carry forward their backups from the new infrastructure.

But yeah I think I’m also very interested to see, because there can be different dimensions to it, right? If they have backups protected in the object store or a tape or any other long-term retention, I think that is still there.

So they can use it anytime, but I’m not sure if there is a backward portability of the backups. Once they move out from the VMware to other platforms let us know so we can engage our experts. We can definitely see an option for it.

Justin Parisi: Yeah, it’d be interesting because I would imagine that if you had a vm, you converted and you have a backup with the old VM format, that might be challenging to restore it unless you’re just restoring certain aspects of the data maybe. But that might be something that needs to be looked at if they were Yeah. Moving and migrating. All right. Anything else you wanna cover before we get outta here?

Manohar Kulkarni: No, I would only say that if you have any additional questions you can reach out to us on ng- backup service feedback, and, we have a bunch of engineers and experts added to that group, and if they want to know more we can respond back and have further conversation with that customer.

Ebin Kadavy: Yeah. There’s definitely a better level of opportunity that you can have. So first thing is like the customers who are assessing VMware and other alternative. They can definitely walk into our solution and we are ready to help you in the deal.

So ng-backupservice-feedback and that’s external one. And any customers or partners can reach out to us directly on that DL. And second thing is if they want to do a POC, they want to have more demos from our site we can definitely help you with that. We can show how things work with NetApp backup and recovery, and like I said who all can definitely try especially the SnapCenter customers. Today we have a limitation. I know many customers might be using different tools to have a long-term retention story. And if they are interested to have that solution in one place, a single tool, single console, single platform.

Now we have the solution.

Justin Parisi: All right, so sounds like we got a lot of good information here about NetApp backup and recovery service. And if you’re interested in it, of course it’s in all three major clouds. Manohar again, if we wanted to reach you, how do we do that?

Manohar Kulkarni: You can either reach out to our team on [email protected], or you can also reach out to our email IDs that we shared at the initial. My email ID is [email protected].

Justin Parisi: All right. And Ebin

Ebin Kadavy: Yeah, you can definitely reach out to the DL on [email protected].

In addition, if you wanna reach out to me, you can simply write an email at E-B-I-N, [email protected].

Justin Parisi: Alright, excellent. So again, if you wanna reach out to these guys and talk about NetApp Backup and Recovery Service, or SnapCenter or anything else they’re there for you. Again, thank you for joining us and talking to us all about the NetApp Backup and Recovery Service.