Transcript
Just a few housekeeping items to kick us off. I want to make sure and let everyone know that your mics are going to be muted throughout this webinar. Also, the Q&A, use that up in the upper right-hand corner of the webinar. If any questions come up throughout the webinar, please feel free to ask those. We'll answer those as we continue throughout the webinar. Myself, I'm Jason Trier. I'm a senior customer onboarding engineer and America Team Lead. And then we have Gregory Barney on here with us as well, and he's a customer success engineer. We're going to go ahead and get kicked off. So diving right in, we're going to look at the Veeam Data Platform. A lot of information on this page. We've got right in the center, take a look, we've got Secure Foundation, Cyber Resilience and Enterprise Resilience on that right-hand side. So what we're looking at here is just a difference of licensing model with the platform. The main foundation, you get backup and recovery. The Cyber Resilience is advanced licensing and then premium licensing there. As we fill this out, you're going to see as you kind of go to the right-hand side, obviously, you're going to get some more features. You're going to get AI guidance. You're going to get detect and identify threats, secure and observability. Really what we're here talking about today is that orchestration and compliance piece. So diving in, what is Veeam Recovery Orchestrator? At the high level, it serves a couple purposes. It's really great for compliance, validating those RTO and RPOs. We'll get some reports that help you validate and ensure that you're meeting those compliances. We have clean recovery on that right-hand side. Again, this is going to be for ensuring that your data is clean, that you can recover from it, that you've done the testing, that we can do the bubble testing, ensure everything's good to go from that time that you may have to find yourself in that disaster recovery scenario. Dynamic documentation, automatic updated reports and audits. These things are great for compliance. These things are also great for executive leadership as you're working with the product. Anything that you do in the product, any recovery plans, anything that we build for orchestration, we're going to have reporting on that. We're going to be able to do some auditing on that information as well. As we look at recovery to the cloud, here on that right-hand side, this is just pointing out that we do leverage and have compatibility with Microsoft Azure. We can take your data from on-prem and we can recover that into Azure. You may have an Azure landing zone today, so we can work with that and bring your data back over there during a DR event. If you don't have Microsoft Azure, maybe that's something that you might look to in the future. Now as we go down to the supported platforms and applications at the bottom here, we're really just pointing out the different platforms that we work with. On the left-hand side, we have Azure, vSphere, and Hyper-V. These are the main products that we work with today. I know you probably got questions, what about Nutanix, what about Proxmox? Note that those are questions that are asked very often. Note that those are on the roadmap as well, but I couldn't give you a time on those. We also have integration with Veeam Agents. As you're working with your Veeam backup and replication product, as you're protecting that data in your environment, just note that everything you see here, we can leverage it with Orchestrator. The apps, Exchange, SQL, SharePoint, for doing application aware, we have more granular control for orchestration and recovery there. If you're leveraging one of the three storage providers as your production storage, NetApp, HPE, Lenovo, and what we're saying here is we can orchestrate from your production level replication. If your replication data source belongs from a production to a DR location, we 100% can integrate with that in the product. Custom scripting here, this is something that's used pretty widely. You've got specific use cases for your business. You may need something that needs to get scripted inside the guest operating system at the time that it recovers into a DR location. Just note that is a capability in the product. Taking a look at core architecture here, one of the things that we're looking at with Veeam Recovery Orchestrator, and I want to note that you might often hear us refer to this as VRO. It's just a term that we use for this product and shorten it up, and so we leverage it quite a bit. Now, on that right-hand side, you're going to see Veeam Orchestrator server there. Obviously, that's just the main application. There's the service as well as the web UI that gets us access to managing that platform. And then we have Veeam Backup and Replication. Now note, you already got a Veeam Backup and Replication server probably in your environment today. This is just an embedded product that we can leverage, and we'll get to that a little bit later in the webinar, maybe what some purposes are for that. We also use Veeam One. Again, you may have this in your environment today. This is going to be a lightweight variant of that product. We're going to leverage that for pulling data about your infrastructure as well as your Veeam infrastructure to pull data into Veeam Recovery Orchestrator so we can leverage it. So just note that that's what that's purpose for. It's not going to be to replace Veeam Recovery, sorry, Veeam One in your environment today. Now just to point out here, you know, independently, these products, some of them support Postgres, but currently today, as we do deployment of Veeam Recovery Orchestrator with V13, Microsoft SQL Database is required. And having a separate server that manages that SQL Database, you know, standard for enterprise is going to be the best practice requirement there. Now when we take a look at sizing of the server, a lot of people fall into that 1 to 1500. So on the left hand side, we see CPU anywhere from four core to eight core. If you have enough compute availability in the environment, obviously I would always recommend to shoot more for the eight core. You know, you can scale that as you go if need be, if performance becomes a hindrance or if you're seeing something there. Now for memory, 12 gigs for the orchestration server, eight gigs for Microsoft SQL. And as we mentioned, you know, earlier, we want to use that separate SQL server if possible. If you use a SQL box or a SQL instance on the standalone Veeam Recovery Orchestrator server, just note that you're going to have to give it more compute than you would if it was just acting as the application front end. So orchestration scenarios. This has taken us back into really some high level overviews of how we leverage some of the data protection in Veeam Backup and Replication. And we're looking at this at a, what are we doing with the data from a common scenario when we're going from production to DR, where are our management servers sitting, right? As you can see here, Veeam Backup and Replication is sitting on that right hand side. We've got Veeam Recovery Orchestrator also sitting there. Now this is going to be best practice placement for this product. Veeam Recovery Orchestrator needs access to Veeam Backup and Replication during an orchestration event. So if your Veeam Backup and Replication server is sitting on that production side, if that production side goes down, it has a power outage, it has, you know, a catastrophic event. The first RTO for your orchestration of your data is going to be recovering Veeam Backup and Replication. So you really want to make sure that this is available in the environment. That way you're not having to recover, you're not having to spend a half hour to an hour pulling that, doing a restore of that database. You could restore it back into Veeam Recovery Orchestrator, you know, because that does have an embedded instance there. We generally recommend that it is a separate instance. You could have a cold server sitting at the DR site, but note that cold server may need to be updated, you know, to the latest version if you're not keeping it up to date. So there's just a lot of things in the mix where generally Veeam Backup and Replication sitting at that DR site is the best strategy. The one caveat to that, obviously, is you're going to be able to, you know, when you take a look at having VBR at that site, if that connection goes down between DR and prod, because you've got your data movement components, such as your proxies and your repositories and gateways at that production site, you may not be able to back up that data because Veeam Backup and Replication cannot talk to those assets. So something to consider. Now this is just showing you a orchestration of VM failover. Got a few hosts on that left-hand side. We're managing it with Veeam Backup and Replication. The data is flowing, and this is kind of showing a very simple model, you know, simple deployment, like maybe Veeam Backup and Replication just acting as like your all-in-one component, and you're doing a replication to the DR site at that ESXi host, and Veeam Recovery Orchestrator is connected into that production Veeam Backup and Replication instance, and we're, again, we're managing the orchestration commands and the data here for that failover. VM failback. So if that production site comes back up, wasn't, you know, it was a power outage, it was something that wasn't too long-term, pretty simple, and we're just leveraging common technology that's baked into Veeam Backup and Replication here, and we're going to say, hey, we want to take that data that's been running in that DR site, and we want to bring it back. We want to fail it back. Storage and VM failover. Now this is just going to be a mention to the HPE, the NetApp integrations that we have for storage integration overlay for storage snapshot replication, and then failover here. So what we're depicting on the left-hand side is obviously we've got some data stores over there on the left-hand side on site A. We've got that storage array. We're going to have some API integrations that we're going to be able to send those commandlets to allow us to do the recovery of the volumes from site A to site B. Obviously, in the replication, the data is already there, but it's just that orchestration command to bring those volumes back online. So orchestrating restore to VMware vSphere, and what we're looking at here is the backups. We're looking at taking backups to that prod site, doing a backup copy of these over at DR. Note, this could be – it's not shown here, but this could potentially be a cloud site. Maybe the data is sitting out in VM Vault, and you want to pull the data back to a DR site. Maybe you have that type of connectivity. So that is something that we can definitely do with this product, and this is just showing that orchestration, showing all of the components that are in the mix here for making that work. We've got the backup – a backup copy of that data at DR, and VM Recovery Orchestrator is simply saying, hey, I know where that data is at based on having connectivity to VM Backup and Replication. VM Backup and Replication houses all of the information about the policies, the proxies, the repositories, where the data sits, and how to rehydrate that data. And so orchestrators are simply just leveraging commands and telling VM Backup and Replication to do what it needs to do. Now, of course, as you look at VM Recovery Orchestrator, you're going to be grouping what you want to recover into recovery plans, and that's something that Barney will cover a little bit later. Orchestrating Restore to Microsoft Azure. This one is – you can do this a couple different ways. So I just mentioned we've got prod, we've got DR to Azure. One of the things that isn't really necessarily depicted here, but what we do see is we are potentially taking data object storage. Maybe that object storage is sitting in production. Nope. You're going to want that secondary copy of the data sitting in Azure. If it's sitting in VM Vault or it's sitting in an Azure storage blob, that is going to be the most recommended path for recovery to Azure because the data is sitting there locally. Another infrastructural kind of architectural key point here that's not depicted is that you're actually going to deploy Azure proxies in Azure, and those Azure proxies will then be able to pull data out of that object storage, out of your Azure storage, or Azure blob, rather, and that container is going to be able to rehydrate that data, reformulate it into those VM files that it needs for Azure, those managed disks that it needs to present that and power those VMs back online. Restore to Azure local. Previously, Azure HDI stack. This is also a capability in the product, and we're saying, hey, we can take things from, say, maybe a VMware environment, and we can take that over to a DR site that's sitting in Azure local. So this is going to be one of the more complex explanations about the product, but data labs is a component of the product, and some of you may have used virtual labs or Azure backup within VM backup and replication. This is really just an extension of that. That's bringing that Azure backup and that virtual lab configuration into expanding it into VM recovery orchestrator as a data lab. And this is going to allow us to do the bubble testing that we'd like to do with anything that maybe we are orchestrating with. As I mentioned, recovery plans, we're creating recovery plans that are going to inventory and house all of those VMs that we may be wanting to recover from backup or maybe wanting to recover from replication. We could set that to be tested in a data lab. I mean, there's so many reasons why we want to definitely do that. It allows you to validate, you know, spin up time of VMs. It allows you to validate getting those VMs online, do some scanning against them. It allows you to verify that those machines can talk to each other. Potentially that new subnet that we're looking to isolate as well as kind of mimic. So that is a great use case. What we're talking about specifically here is that replica verification. And there's some different networking modeling that we can do or feature sets that we can do with the product. What we're looking at here on that left-hand side is we're just simply saying, hey, we've got a production host. We're doing a replication from prod to the DR data lab. And we are essentially have a host on that right-hand side where the data is being replicated to. And then we're leveraging a virtual lab to create an isolated network. And as we go down, you could see on that right-hand side on the data lab, we've got purple text. We've got the green text there. And really what we're indicating is just differences of networking there where we've got in green. That's the production, right? We've got the DR ESXIO2. We've got the DR vSwitch and the DR port group. And then we're actually creating in purple an isolated network for that replica machine to be powered on. And so it's not going to be able to talk to anything else. It's truly isolated. That virtual lab is going to be the one that communicates between, as you can see, as we follow that line up from VLAB, that virtual lab is going to communicate to all of the production beam components. But it also is going to sit one foot in each. It's going to sit on the fence between production on that green side and then one foot on that purple side. And that's what's going to be able to allow VM01 or maybe we bring several VMs back into this data lab and this isolated network. They're going to be able to talk to each other without talking to production. But VLAB allows that kind of firewall type routing to act as a mitigator between the two networks. So taking a look at clean room here as I can get it to progress, VRO detects if remote agent on the VBR cannot be reached. I'm going to go ahead and just fill this out. So we talked a little bit about data labs and want to talk about. Kind of some key differences with what clean room is now with clean room. We're actually utilizing some custom scripting to detect if a remote agent on VBR cannot be reached. When that is not reachable, if the VRO agent is offline, then by default, the embedded VBR is checked for the required restore points. So it's going to take a look. Hey, that agent's offline. I can't talk to that VBR server. Then it's going to check to see if the required restore points are available. And then it uses a pre-planned script in the recovery plan to allow us to check that data, attach the repository, pull the data back in and do a recovery of that data. And the clean room perspective, as we kind of dive in here, this is kind of what it looks like. Very high level. We're not going to dive into a bunch of detail here. But the clean room is more of a we're actually going to test like maybe we've got a full prod. We've got a clean room. We've got dedicated ESXi host or maybe even DR that's completely passive, that's sitting over there and that's available to us to do clean room type testing. We want to take control of a copy of the data that we have, a backup repository, local onto that clean room side, that potential DR side. It could be at a headquarters. I mean, it just needs to be available infrastructure. And it's going to take advantage of that backup repository data, and it's going to then do a clean room recovery with the backup data. So that's why, you know, here on that left hand side, you know, maybe we're going to schedule a connection disconnect between that prod and that clean room to isolate it to allow for that testing. So what I'd like to do now is I'm going to go ahead and hand it off to Gregory Barney. He's going to take over, talk about some of the new features with v13, and then he's going to dive into a demo a little bit later with you. Awesome. Thank you so much, Jason. Let me just go ahead and share my screen here. All right. So, yeah, some great new features here in version 13 of Veeam Recovery Orchestrator. Down at the very bottom of this page, if you notice here with v13 for Veeam Data Platform, we've also raised the version number up on VRO to align with our other products. So it's a little easier to determine that everything's kind of on the same level. But here at the top here, we've added software appliance support. So that great new v13 feature that we've added for software appliances, including the AHA clusters, are now supported in VRO. We have a brand new web UI, which we're going to dive into on the demo. I've probably seen it here on some of the slides that Jason has gone over. And that UI plugs and plays into all the other kind of web hooks and APIs that our other products offer, such as VBR and V1. New audit reports. So we'll be diving into that on the demo as well. You can see recovery plan activity, change tracking. We also have some new offline malware scans, which we'll touch on as well. You can do YARA rules. You can even reach out and touch that restored virtual machine, for example, and run antivirus on it for the installed antivirus that you have. We also have some failover vSphere data store support for VMs that are backed by Electra MPB 10,000. So moving on here, one great new feature, which is part of that new web UI, is multi-factor authentication, which you can enable and disable globally. It's enforced just for your UI login. It's not enforced for plan executions. So you'll see that on the demo when we're looking at plans. If you were to run a plan, you don't have to use MFA. And then inside of the roles section of the settings inside of Recovery Orchestrator, you can see all the status for MFA for all of your users. And you can also reset MFA for any users. Touching on the Veeam software appliance support here under the infrastructure tab under Veeam Data Platform, you're able to deploy agents and you can add the Veeam software appliance cluster to Veeam Recovery Orchestrator. You can just use the IP address or the cluster name and the VRO agent is automatically going to deploy to those nodes. Touching on some more of the new Azure stuff here, we can connect directly to Azure local clusters or via SCVMM. We could do direct cluster connection. So that's also supported for Hyper-V workloads. And Orchestrator can also treat Azure local the same way as Hyper-V, the same way that your VVR does. Then this here is our Recovery Orchestrator matrix for compatibility. So simple from and to column there. So your VMware backups can be restored to all Microsoft platforms, on-prem hypervisors and Azure. Microsoft on-prem Veeam backups can be restored to both Microsoft's on-prem hypervisors and agent backups can be restored to vCenter and Azure. These slides will also be getting sent to you as well. So you'll have this compatibility matrix in the deck when it gets sent out. There are some Hyper-V and Azure local limitations. So you won't have the ability to do your virtual lab or as we call them, data lab testings. Malware scanning is a little limited here, but there is malware flag on the restore point detection. So if your restore points were flagged as having malware from the VVR, your recovery plans will be able to see that and detect it. And they're unable to run ingest scripts and it is not available for replicas. And then this dives a little bit more deeper into some of those limitations, but also some of the robust cross compatibility that we have here on this matrix here. So you can see the replica plans, CDP plans, and their availability for VMware, but not Hyper-V, but we can restore from backup plans on both, for example, as well as malware flag checks. We are scanning for both readiness checks and post-recovery validation on both. And then on the right side here, we have that from to column again. So vSphere to Hyper-V to Azure. And the agent and your Hyper-V, which can go to Hyper-V and to Azure, sorry, to just to Hyper-V, but your agents can go vSphere to Azure. In this slide here, we're going to dive a little bit into some of the offline malware scanning here. So if we come down to our recovery plans here, you can click on one of these and go to manage. And under scheduling, we can enable our malware detection here and we can tell it to run once or weekly, what days we want to. So you can schedule these tasks to run and even check for malware here. And then we're going to flip on this antivirus scan. And we're going to tell it how many restore points we want to check back on. We can also use our YARA rules here that we mentioned previously. If we right click here again, we can hit scan. You can see here that. We have a verified state up at the top there. We can select our YARA rules. And then the restore points here, we can say our most recent restore point before a certain date. And then it's running here, as we can see. So we're going to go into the details here. You can see that these are queued. These are some of the steps here, which we'll touch on a little bit more in detail on the demo section portion. You can see here we have a lot of good success so far. Right now it's starting to scan the C drive. And we have another success down there for the volume. And a success on the malware scan. A very powerful functionality here in Recovery Orchestrator to do an on demand malware detection check on our restore points. Moving on. Recovery documentation. So this is also something we're going to touch on in the demo in a moment here. This is very powerful stuff here. We're able to run reports and automatically generate reports as soon as we create a plan, as well as audit our plans, data lab tests that we do will generate reports as well. So there's a whole host of dynamic documentation that we're able to provide through Recovery Orchestrator to really give you that deeper look into your environment, both from the perspective of a backup administrator. But as we'll see later also for stakeholders and audits. And this here is an example of one of the audit reports that we'll be looking at later. This you can set up to run monthly. And it has a summary page that's going to show everything across the whole month, everything that's happened on that plan. So every activity is recorded and we have the legend here in the bottom middle of the screen. You know, if a plan was halted, malware was detected, if the plan ran and had warnings. And, you know, if there was RTPO failures as well. I'm going to go ahead and move over into the demo portion here. So this is my Veeam backup and recovery and Veeam Recovery Orchestrator server here. So I'd like to just start off with backup and replication here. As we can see, we have a number of jobs here. And we'll keep an eye on these names here because we're going to see these in V-Row in a moment because they're going to get pulled in automatically via mechanism in VeeamOne. So over here is our dashboard for Veeam Recovery Orchestrator. If I come over to our settings here, we can see kind of some of the back end and some of the stuff that Jason was talking about earlier. So under our infrastructure here, we can see that we have a VBR server here. We have our VMware hosts as well. And we also have our recovery locations. So just as the name implies, these are going to be locations that are designated for restores to go to for things like backups. Whereas, you know, a replica is going to spin up wherever the replica resides. But for our backup restores, you know, we want to specify a location. So we're going to build those locations out here. And then under inventory access here, we can see our groups. And if you notice, these names here are looking familiar because they're getting pulled in from that VBR server. So we have groups that contain our VMs from what's being protected in VBR so that when we go to create jobs or edit jobs, we're able to select those. I come down here to recovery plan. I'm going to say add a new plan. And there's a few different types here. So we can do, you know, cloud workloads here. So we can recover VMs from vSphere or agents into Azure. We can do restores from VMs from agent backups to vSphere or Hyper-V replicas and storage failovers. So for this example, we're just going to do a restore. And for our type here, we're going to select a VMware vSphere. And we can give this plan a name. So for this example, we'll say test. And then we can enter in contact details as well. So we can say Donnie is going to be our contact. And that would be his email in this example so that when something happens with this plan or it runs, that's the contact who's going to be informed. We're also going to specify an RPO and an RTO. And this is going to kind of be that golden rule that the plan is going to hold itself to. So when we start running audit checks and other things like that, this is effectively what it's checking against to make sure that RPOs and RTOs are met. And then for our recovery location, as we saw earlier, we are going to select the DR site here that we have set up for vSphere. And then our reporting, you can create different templates. We're just going to go with the default template here. And then the summary page is just going to give you a summary of everything that we did. Now, when I click finish here, it's going to ask us to jump in and use the plan editor. I'm just going to say no for this portion here because I'm going to jump into a pre-created plan and show everything in there. So we're going to use this billing app to VMware plan. So if I come down here, I can go to manage and then I can go to edit. And in here, I can see I have pre-planned steps, post-planned steps, and I see my group of VMs, which would be added. So here, as you can see, we have our different groups. So our billing group has already been added in this example. And we have a lot of granularity here because I can add individual steps to these VMs or I can add a step globally to the whole group for this plan. And so in this example, I'm going to add two group options. And show here that we can actually restore the VMs with their original VM tags. We can also do re-protect a group, which would allow it to choose a template to back these up once they've been restored so that they continue to stay protected. Which is a very powerful thing because that's a question that I always get asked a lot is, OK, now my things are restored. How do I continue to protect them in case I have to run them for a while? So highlighting the group here, if I go to step editor. I have all of my steps here that have been selected, so it's going to restore the VM, which is useful. And we're also going to do a heartbeat check just to make sure that it can reach the OS and validate that. OK, the VM has been powered on and restored. You know, is it, you know, is it actually there? Is it in the OS? So I'm going to come here and I'm going to add. And I'm going to do a network check because I want it to be able to ping and make sure that I have some network connectivity. And if I click on any of these, I can go to step parameters and you have more granularity. So here I could put critical step if I wanted to. That says, hey, you know, this is this is critical. You know, maybe I want to halt the plan if I consider this to be critical. So the whole plan will stop, but we're going to leave that off for now. You can see here you can set timeout as well as retries. Now, if I hit save here, you'll see that it adds. That network check to all of those VMs inside of the group. So I'll just say save plan here. Back. And then what we will do is we will go to our schedule. And so under the schedule, just as the name implies, we can publish audit reports on the first day of the month here at 8 a.m.. We can also perform readiness checks regularly. And this is also where we can schedule malware detection here, which we touched on a little bit on the on demand side of things. But I can configure the schedule here just like we went over before. Here and then I can also schedule a plan execution. So say I want this plan to run regularly and generate those reports. I can do so. I'm going to cancel. So the next thing to do is a readiness check. I can run check. And this is going to tell us if the plan is ready to go and if it's able to perform the steps. In our plan. Here we go. Sorry about that. It's in use here. All right, so we had a fail to check and we got some errors there. So what I can do is I can come down here and. I can go to reporting. And I can see here. My report failed. I don't see a readiness check there, so I'm going to come here and I'm going to run a readiness check. Doesn't seem to want to cooperate here for some reason. So. Let's try on this one here on our engineering app. Since we saw that that one already completed successfully. So you'll get something like this when it's validated and passed its checks. We'll continue to use this plan here as an example, but another thing that we can do here. So another thing that we can do here is come to test. So we'll try to run a test here. On our billing apps to VMware. We can say we're going to go to our DR site that we had set up and our data lab. We could select our data lab that we have created here. And we'll just do a quick test here. And then we're going to power them off immediately because we're just testing. And we can even enable our malware flag checks and a virus scanning if we would like to as well. It's going to run test here. And while Barney's getting that to run here, I just want to let everyone know, if you have questions, please throw them into the Q&A so that we can get those answered. Thanks, Jason. Just waiting for this test here to run through. And we can get a little bit more information here as well if we go to that left-hand side on the data labs there on the nav. And you can see that that's starting. If you click into that, we're going to get that more granular information about what we're actually doing with that virtual lab, as well as what's happening with that recovery plan that he's testing out here. If we click on here. Thank you, Jason. We can see that we've gotten up to preparing our data lab here. And we're now waiting for these billing app to VMware prechecks to come through. And so while it's running, we can actually kind of skip ahead here like this cooking shows. But if we come to reporting here, what we can do is I can actually filter this by data lab tests. And we can see here there's some previous tests here that have run successfully, some that have been halted. So if I click on this billing apps to VMware, it'll download a PDF here. And I can open this up. So this is a resource plan data test summary report. Over here, down to the summary here, we can see everything that executed on the plan. We can see that the preplanned steps are successful. The VMs were successful and our post plan steps were successful. And if you notice, these are all hyperlinks as well. So we can click on these and get brought down. And then we can continue to drill down into each single one. So here we can see billing one here. We can see our recovery test. Our restore was successful. The heartbeat was successful. It also obviously checks beforehand that there's available licensing. So that we know that everything's going to be able to come up without any problems. Take a look at some of these other reports as well. So there is also our readiness check reports that we were trying to run earlier. Filter these out by success, even warnings. We'll do one of these ones with a warning. And show how that's useful to us. So on this readiness check report here, we'll go back down to summary. And we can see that certain things weren't ready. Certain things had a warning. So we'll click on this and we'll see that there are warning results for each of these. So if we click on one of the names, we can see that it wasn't able to restore. So this gives you that granularity so that you can dig in and kind of problem solve if something doesn't run successfully. Also execution reports. You can see here. Click on this one. Download. My lab environment clearly needs some work. Down here, a similar type of breakdown. Met its RPO. There weren't any RPO failures. And it gives us our timing on RTOs as well. So this is a great check to be able to kind of give to your teams or the people above you. You know, maybe that corporate level or auditors that says, hey, we are going to be able to meet our RTOs and our RPOs. Using Veeam Recovery Orchestrator and using the plans that we have set up and configured. And this report validates that. So it's a very powerful tool, again, for validation. I'd also like to check out the audits. The audit reports are going to generate and be able to show you everything that's happened to a plan, any changes that have been made. So these are. Really great for. RTPO showing errors. Here, we'll go to summary. So, again, just like we saw on that slide deck here, you know, it's running every day. We can see here that the readiness checks that passed recently. You know, there was a warning here. There was a RTPO violation here. So it gives you that kind of snapshot of how the how this restore plan is functioning and operating. So, you know, OK, things have been going good here. But if we start to see warnings and errors, then you can obviously surmise. OK, if something were to really happen and we had to run this plan, you might run into issues. So it's a great way to be proactive with all that and inside of your environment. Readiness check here. Do one for success. Check one of the CDP. So this one is for our CDP replicas here. So we can see here that the execution details, what the what's going on inside of the plan, our SLAs and RPOs. We can see ready, ready, ready. Lots of good green there. It's meeting its RPO, didn't have any RPO failures. It's within its SLA. So these are, again, reports that you can generate to show yourself and others that things are configured correctly and that the environment is being protected properly. So to close out the demo, we're just going to come back to the dashboard here. Dashboard is just what it sounds like. It gives you a high level view of everything that's going on. So we can see here that in this example in the lab, you know, we have some, we have a verified plan. We have a number that are not yet verified. And we have a few that needs verifications. So these are ones that haven't been checked yet. And these are ones that have failed and need to get verified. And then also we have our testing plan results here. So we have one that had halted and failed. And then as you can see here, high level overviews of RPOs and RTOs. And then you can click into these plans and drill down. So again, I can come in here. I can see, OK, there was an error. Where were my errors? And it wasn't able to process this. So the restore point didn't meet our desired RPO in this example. And in this example here, too, it wasn't in a ready state. So it was disconnected. So as you can see, again, just a very high level overview of some of the powerful options that you have inside of Veeam Recovery Orchestrator, including all those plans and reports that we can run to really show yourself again and others inside of your organization that things are kind of passing the smell test. So we know that, you know, if push comes to shove and you have to run one of these plans, if you have to perform recovery inside of your environment, you kind of know exactly what's going to happen. And you have the documentation not only to back it up, but also to run through. So you know exactly what's going to happen with your plans before they even have to kick off. And with that, I will stop sharing my screen. And so. If you want to get more involved in our community, we definitely encourage you to go to community.veeam.com. You can join our community hub. We have the VRO Heroes Den, which is a great resource and forum of other Veeam users using Veeam Recovery Orchestrator, helping each other out, answering questions, posting things they've used it for. There's also a lot of really great we call them Veeam user groups or VUGs that you can join up. You can find a local VUG in your area. We have them in the U.S. as well as Canada. There's some really great ones. It's great ones out in London, all over the world, really. And some of those communities are extremely active. So the community here is really a great place to not only get started, but also just to kind of continue your Veeam journey with keeping up with all the new things and features that are coming out. Also, if you're ever looking to take your VMCE, there's a lot of great resources on the community hub there for VMCE. You'll see Shane around there on the forums, posting practice quizzes and practice exam questions to help you get ready and sharpened for that. Great. Great, Barney. Yeah, I think we could definitely end it off there. I mean, we do have a little bit of time left. So, you know, a lot of great material was covered. If there's any additional questions, you know, feel free to get them in there now. We've got your information as well, so we can get you some feedback on obviously all of the data that we covered, the slides, like I mentioned, additional questions. But I appreciate everyone joining the call with us today, joining the webinar and reviewing Veeam Recovery Orchestrator and all of its features. But I think with that, we'll end it off and everyone have a great day.
