 Hi, this is your host, Nibbharti, and welcome to another episode of TF4LestTalk. Today we have with us Todd Dorn, Solutions Architect at Scios Technology. Todd is great to have you on the show. Hi, thank you. Yeah, and today we are going to talk about how to future prove your business with H&A and DR and ensure business continuity. If I ask you, how would you define H&A and DR for SAP HANA? Well, so now for SAP HANA, H&A and DR to me means five nines of availability. And no matter how you're going to get that, right? So you have to easily be able to execute takeover with Handshake, for example, for maintenance. You need automated testing and failover. SAP has the APIs, but you really don't want to be manually doing all of the H&A tasks, right? If your server goes down at one in the morning during a backup, you want that automated failover to provide the high availability. So SAP, again, has the APIs and Scios SAP Application Recovery Kit, has the automation monitoring and orchestration that you need. I'm curious if HR and DA is simple or complex in SAP HANA environments. And if it is complex, why so? H&A and DR and SAP HANA is extremely complex because the environment is extremely complex. You've got three layers. You've got your presentation layer, your application layer, and your database layer. The presentation layer is easy to protect. It's simple. HTTPS, but the application layer and database layer provide a number of challenges because you have so many different processes running. You've got data moving between the layers, between servers, you've got replication going on, and you've got so many possible failure scenarios. You can have physical, environmental application, network, and human error. So just the sheer number of things that you have to monitor to identify the quickest resolution and then also follow the SAP best practices to ensure a recovery point objective or RPO of near zero data loss is just a really daunting task. I would talk about how Scios is helping customers deal with some of this complexity, but I also want to learn from you what are customers doing, what kind of strategy they have deployed to simplify and future-proof their SAP HANA environment to, of course, ensure business continuity. So the key thing is reducing the single points of failure. Multiple servers at every layer with replication to a passive and standby server and a DR server, and those need to be distributed through multiple data centers. And again, the biggest cause of failure is when you have a lot of tasks and scripts that need to run, having a human do it, you're going to have introduced more human error. So automation is the absolute best strategy to being able to provide a good HR, DR environment. The other thing is, you know, planning and frequent testing. You need to have, you need to test these systems and make sure that they are constantly that that HA is working in the way you expect that your databases are getting re-registered and that, you know, failover is truly seamless. Can you really do a failover with handshake, for example? And our product makes that super easy. Now let's talk about Scios. What solutions do you folks have for high availability in SAP HANA environment? So once you have your SAP HANA environment set up, our installation and configuration is done through a GUI wizard. It takes about an hour. If you were to try to do this with pacemaker or something, it's going to take you probably several days. And then it doesn't cover all of the failure scenarios, like if you do failover, having your DR site re-register with the new primary server, right? And Scios Protections, we covers everything. We orchestrate and automate, make the failover extremely easy. We support all the SAP best practices. So things like if you get ASCS and ERS, you know, on, so say your primary fills, you're on your standby, it now has ASCS and ERS both running on the same server, which doesn't follow SAP best practices. We're going to go ahead and move the ERS to the third node or the DR server. We cover Scios here on a regular basis, but can you talk about any new feature, any additions that you folks made to make things even better for users? So we just recently added the HANA third node support, which, you know, when you had the HANA database before, we supported, you know, two nodes typically in the cloud in the same AZ. But now we're able to support a third and even a fourth node in a DR. So that's new for us. We've always been able to do that at the application layer, but now we can support it at the database layer as well. Todd, thank you so much for sitting down with me and talk about HNDR in SAP HANA environment. And I would love to talk to you again soon. Thank you. Thank you, Swapnil. It's been a pleasure.