Hyper Convergence in the Era of Always On Business

Transcription

1 Hyper Convergence in the Era of Always On Business Speakers: Mike Perkowski, TechTarget Brien Posey, Freelance Technology Writer Jason Leiva, Veeam Certified Engineer Trainer Mike Perkowski: Ladies and gentlemen, welcome to today's web seminar. I'm Mike Perkowski with TechTarget. I'll be your host and moderator today. We're glad that you joined us for Hyper Convergence in the Era of Always on Business. Two hot topics, thrown into one, fortunately, we have two expert speakers today who are going to going to cover a lot of ground. But we before we do, I first want to acknowledge and thank you sponsors for today's program, Veeam and Hewlett-Packard Enterprise. We do appropriate their support greatly. Our program today as I said is going to feature two expert speakers, we're going to hear first from Brien Posey, a freelance technology writer and speaker who's also a 14-time Microsoft MVP with more than 20 years of I.T. experience. He's a former CIO. And he also served as Network Engineer at Fort Knox. And Brien also has the additional distinction of being a commercial scientist astronaut candidate. After Brien, we're going to hear from Jason Leiva from Veeam. Jason has been with Veeam for the past six years, first as a pre-sales engineer and then as a Solutions Architect for Global Alliances. Jason also was a co-host on Veeam's web based technology show, "Veeam Live", where he talks about Veeam and industry technologies and issues and how they fit into today's modern enterprises. Jason is a Veeam Certified Engineer Trainer as well as VMware vexpert. We're fortunate to have both of these gentlemen here today. So with that, I'd like to turn the proceedings over to our first speaker Brien Posey. Brien, the floor is now yours? Brien Posey: So thank you for having me everybody. Just a little bit about my agenda for today. I'm not going be going in the super technical depth or anything. I'm not trying to make anybody's heads hurt. What I really want to accomplish today is to kind of set the stage for Veeam by talking about is hyper-convergence, just for the benefit of anybody who might not have been exposed to the technology.

2 So along the way, there are few things I'm going to do. I want to talk about why does it matter? So, you know, it's one thing to introduce the technology but really the bigger question is, why should anybody care? So, that's part what I'm going to talk about. I also want to talk about some limitations and some potential gadgets. So, I'm going to be talking about hyper-convergence from the standpoint of the good and the bad and just introducing the technology. So I think I can pretty much keep the bio slide because, I got a better introduction that I could ever possibly give myself although I do want to take just one second and clarify that I'm not NASA astronaut. I'm working toward a commercial scientist astronaut certification. And if anybody's curios about that, there are details on my Web site at brienposey.com/space. So let's get into it. First question, I want to explore is what is hyper-convergence? Or what is hyper-convergence infrastructure? Well, it's a lot of things but the simplest way I can really think of to put it is that hyper-convergence infrastructure can be thought of as match hardware. And the basic idea behind hyper-convergence infrastructure is that there are number of vendors that are offer the technology and based on match hardware and match software. So, a hardware vendor will assemble storage compute and network resources that are perfectly matched to one another's performance level. So that when you get a solution that designed to work really well together because if you think about it throughout the history of I.T., the approach that most organizations have taken to several deployments is kind of piecemeal. Well, the server, they might buy some kind of storage appliance then they buy networking resources and generally those things do work together but the relationship between the various components might not optimal. Typically, you're going to have one component that performs the others and because of that there's the bottleneck that exist and you might not get the full benefit out of the one piece of hardware that outperforms the others. So hyper-convergence is intended to take away that bottleneck by closely matching the performance of all of the different hardware elements. You know hyper-convergence infrastructure involves more than just hardware. There are also software components that play. There's a hypervisor and this isn't something that the vendor or the hardware vendor creates themselves. Typically it's an off-the-shelf hypervisor, it might be VMware. It might be Microsoft Hyper-V, it could be something else. And then, there was also a management layer. Depending on which product is being used, this management layer could be something off-the-shelf. It could be something custom, but in the vast majority cases that I've seen the vendor that supplying the hyperconverged solution and some of their own code to whatever software they supply. And

3 that code is typically designed just to optimize the software for that one specific environment and to expedite the deployment and configuration process. OK. So let me give you a more concrete example. What I've done in the slide is a couple of examples of hyper-convergence infrastructure software. This is the software that might come with the hyper-converged product depending on what you get. Now, before I get too far into this, I just do I want to clarify the point that I'm talking vendor diagnostic approach. So, even though you might see some vendors listed on the slide and the next one and possibly some others slides. I'm not trying to say that one vendor solution is better than another, make a direct comparison between the various products. These are just here for illustrative purposes. So, with that said, one of the big things that was initially and misconception about hyperconvergence infrastructure was that, it was designed to be completely uniform. I remember it an I.T. conference quite a few years back when hyper-convergence infrastructure first begin gaining traction. Having some there was some people, and the topic of hyper-convergence infrastructure came up. And with somebody said, whether that they have a perception that hyper-converged infrastructure was kind of like a gaming console and that there was a total uniformity across the broad. In other words, the hardware is the same for every installation, the operating system is the same across the broad and the only thing that really differs is the software that you put on yourself. That's truly not the case, because when it comes of hyper-converged infrastructure, you do have some choices. There are differences in hardware. There are differences in software and this is really what the slide is all about. So, I wanted to do is show a couple of different examples of some the software that you might get with hyper-converged infrastructure. So, the column in the left is VMware solution. They call it EVO:RAIL. VMware doesn't make a sever hardware but they do make software. What they knew is they license that software to various several manufactures and then VMware certifies their software to work with those particular hyper-converged hardware deployments. So, if you go with the VMware solution, the EVO:RAIL, when you get in the way software is the EVO:RAIL engine, vsphere enterprise plus, Virtual SAN, vcenter Server, and vrealize Log Insight. And again, I'm generalizing depending on what you get you might end up with something a little bit different. But this is by large what you would expect. Now, on the right, what I've got is H.P. enterprise solution, the HPE 250. And, you'll notice that this is quite a bit different from what you get from VMware, with the EVO:RAIL.

4 And the point that I wanted to make is that there's a lot of flexibility. If you go out and you get an HPE 250, you're not going to put all of these on there. Some of these things are mutually exclusive. But you get a choice because you'll notice that there are VMware products on the list. There are Microsoft products in the list. And there is also some H.P. specific components. So, you have this freedom to pick and choice a little bit. So, what about hardware? Well, the same thing applies to hardware. If you go ahead and you buy a hyper-converged solution, you're not just lacked into whatever the vendors tells you, you're going to get. Typically, a hyper-convergence vendor will offer several different tiers of several hardware. So, maybe you need a mid grade appliance. Maybe you needed something higher end. Typically, you're going to be a redefine something that meets your needs. So for example, if you look at the column on the left, you can see that with the VMware solutions depending on which vendor product you ultimately go with for hardware. There are differences in memory that you can get. There are storage differences and network differences. And, then on the right that's the HPE 250. Now, there are far more choices than what I could fit on the slide but you can at least see that there are multiple choices for storage. And there are variety choices for the other components as well. So, let's turn the table for a little bit. And start talking about some of the benefits of hyper-converged infrastructure. There are a lot of different benefits. Some of these I've already touched on a little bit. The first and probably most important listed here is performance match and benchmark hardware. So, as I said before, the hardware components that you get with the hyper-converged infrastructure products are matched together for performance so that when you truly do get an optimal experience but notice the keyword on the slide, "benchmarked", that's important and that's going come up a little more times throughout my presentation. The next benefit guaranteed hardware and software compatibility. Now, this is one of the both things that it's kind of easy they just glance over and move on. But there's an important point to be made here. And that important point is that because you're not going with the piecemeal solution, you're generally got one single point of contact. Anybody who's worked in I.T. for very long, is probably faced the situation where something getting wrong, you had to call tech support and in doing so tech support blames another vendor. So they called that vendor and then that vendor blames the problem on the first vendor that the person talked to. So, there's others vendor finger pointing going on back and forth. Well, in hyperconvergence, you got one point of contact and the software certified to work with the hardware and all the hardware is certified to work together. So they really shouldn't be

5 any vendor finger pointing. So, that's a really nice plus. And let's see, the next thing on slide, simplified, unpredictable scalability. That's another thing that ties back into the benchmarking that I mentioned earlier. Because the hardware is performance-matched and it's certified to work the other, typically what you'll find is it's been benchmarked before you ever purchase it. So you know exactly what level of performance to expect. And if you have the scale to meet some workloads needs, you know upfront how many servers or how many appliances you're going to need in order to be able to do that. Let's see. A single point of contact support I've already touched on and plug in and play deployment almost. Well, this is kind of one of all those gadgets that I mentioned at the very beginning because you see typically what you'll find is that with hyper-converged infrastructure vendors advertises it as being super easy to deployment, and comparatively speaking it is but it's not truly plug and play. You're not just going to be able to plug in the server to a power outlet and be up running. A lot of vendors will advertise that you can be up and running in 10 minutes, 15 minutes, and realistically, you can if you've done your homework ahead of time. But there's a lot of planning that you're going to have to do first, you have to plan things like I.P. usage, cabling, power and cooling, that sort of thing. So as long as you've laid the ground work upfront, yes, you can be up and running within just a few minutes time. So, what about some other benefits? Well, typically, you're going to find that there is some redundant hardware that you can get. And most hyper-converged deployments are oriented towards high availability, which is always a good thing. And then you'll notice I listed cost on this slide, by enlarged hyper-converged infrastructure deployment are relatively inexpensive compared to other types of server deployment. And there are few other things that are listed on the slide. This is just screencapture that I took from the HPE Web site. Just pick some and I'll show you the types of benefits that vendors commonly cite. For example, on this slide, we've got 96 percent fast reconfiguration, 315 percent better ROP and 50 percent reduction in tools. So these are things that are being claimed by a vendor. That's what they see as being some of the big benefits to deploying hyper-converged infrastructure. So what about some common use cases? Well, there's quite a few, VDI is probably the biggest one, at least that's been my experience. And it makes perfect sense that it would because you see in a VDI environment typically there's a certain performance associated with this virtual desktop, the administrator knows that every virtual desktop is going to consume so many CPU cycles, so many IOPS, so much memory. Well, because hyper-converged infrastructure is pre-benchmarked they can compare of the virtual desktop performance against the known performance of the hyper-converged

6 infrastructure product and variously figure out how many servers they're going to need and where to meet their virtual desktop requirements. But the VDI isn't the only thing that hyper-converged infrastructure is used for. It's also used for server virtualization and it's also starting to gain traction for using branch offices. And that make sense because think about, hyper-converged infrastructure is designed to be low cost, low maintenance, you see the deployed perfect for us operation in a branch office, where you need some computer resources but maybe you don't have an I.T. staff there to take care of it all the time. I'm also starting to see hyper-converged infrastructure used quite a bit in Dev-test environments. And that's also a very good fit because a lot of times in Dev-test environments, the Dev team needs access to hardware that is at least somewhat similar to what's being used in the production environment but they can't always get that. Well, hyper-converged infrastructure provides a relatively low cost way of getting better hardware for the Dev-test environment so that the developers are able to more close simulate what they'll be encountering in the real world in production environment. And then the last thing on the slide is backup and disaster recovery. Now, I'm pretty sure the people at Veeam are going to be able to talk much more about this than I ever could but one of the things that I have seen people using hyper-converged infrastructure for is for disaster recovery failover. I've seen organizations that will have hyper-converged infrastructure servers at remote facility just waiting as hot spares (ph) to failover workload in the event if there's a disaster at the primary data center. So, those are just a few of the more common use cases. So what about some issues to be aware of? Well, one thing that you have to keep in mind is that in spite of the all performance matching and the fact that hyper-converged infrastructure is heavilyoriented towards virtualization, the server platform doesn't eliminate resource contention issues or the trade-off between virtual machine density and performance. Any time that you're doing with virtual machine, you've got multiple workloads that are competing for finite set of hardware resources. And so resource contention is going to be an issue. That doesn't go away just because you move to hyper-converged infrastructure. Also, in some cases component level upgrades may not be an option. What you'll find is that supposed you decide you need more storage than what you initially purchased, you might not be able to add that addition storage on the flight. Typically, you would have to add an extra node or an extra appliance to the deployment in order to add that additional storage that you need. And the same thing also goes for compute and for network resources. So, some more is used to be aware of. If you wanting to do hyper-converged infrastructure and you've already had quite a bit of hard work on site, you may not

7 necessarily have to do the rip and replace, there are some vendors out there that will let you use what they call a referenced architecture. Referenced architecture is essentially a list of hardware that the vendor has certified. So, you maybe able to use of your existing hardware if it meets the requirement of the vendor and it's listed on the reference architecture sheet. And then pair that with couple of more hardware, each vendor kind of has their only guidelines for that. And then, as I mentioned ahead of time of last point is that hyper-converged infrastructure is not one of those things you're just going to plug in and be up and running in 10 minutes, there is some planning that's required ahead of time. Typically, you're going to have some plan out things like I.P. address usage, VLAN usage, power and cooling, network switching connectivity, cabling. So, the same types of things that you would have to plan out within the other server deployment. So, we've covered a lot of ground in a short amount of time and I'm just about out of time, so I want turn it all over to Jason from Veeam. Jason Leiva: Thanks a lot, Brien. You did a great job of setting up the hyper-converged infrastructure, why it exists, why people are moving over to it. You know, I think that it is important to mentioned that, you know, the need for an always on business doesn't really change because of hyper-converged. Well, in my opinion, it really becomes even more important because some of the reasons that people are doing hyper-converged is they got more efficient, meaning that they and they are being able to extend I.T. services. And more funny today is that more, more people becoming are turning into more global operations, transacting business that's overseas. But more often, people obviously connected more and more with smartphones and tablets. You know, just the overall internet of things obviously makes I.T. much more important. One of the things I find funny about I.T. is the more efficient you become and the more services you can offer, the less amount of time, you can accept to be down, because less people (have sealed) services that is having them, those are the first they're going to tell you when they got available. So, really keeping things online is up and running is very importing, right? So, I'd like to hear some inputs you have, what you're seeing today as in a modern enterprise as (inaudible) always on business, any kind of input you may have there. Brien Posey: Well, I don't there're a couple of things that I generally see going on. One of the big things I heard I.T. Pros talk about sometimes that they're not involved in the decision-making process when the SLAs are established. So you might have somebody from management come up with some arbitrary figure about what they expect from an SLA and just expect the I.T. department to be able to meet it.

8 The other issue that I hear from time to time budgetary concerns, the technology may exists for meeting whatever SLAs has been established but that technology comes at price, so often times these organizations in (past meaning) to compromise their SLAs just to meet the budgetary requirements. Jason Leiva: Thanks a lot, Brien. OK. So, in today's presentation, I do want to focus pretty heavily on the Veeam with the HPE hyper-converged platforms. Before I do that, though, I do want to talk about kind of where Veeam and the HPE partnership has come over the years. We've actually been working with the HPE, before it was HPE H.P. has store once to 2011 when we created a joint life taker HPE's duplicating (ph) appliance store once. From there, we moved in to version 6.5 of Veeam and we integrated with the store virtual line of the raise. Where we did, we actually leverage the storage snapshots where we cover capabilities, which I have to talk about a little bit more. In version 7, we start picking up three parts (ph) for the same kind of capabilities and expanded those. And then here, most recently, in version 9, we've actually integrated with the first product that would get a paper list in square ones (ph) I would destroy (ph) what's catalyst integration. So, we've been working with HPE for quite of some time now. We're very happy to see when they came out with HC 250, the converged and hyper-converged lines and integration we're able to make there because of the work we've done together. So, let's talk a little about availability and challenges. So, yes, you actually did some research that have 82 percent of CIOs are not able to meet the business's needs, like having always on applications or always on I.T. I'd like to kind of get some input from Brien as to why he thinks that is. Why are people struggling to meet those challenges and meet those SLAs. You've kind of said it earlier, people a lot of time, the SLAs when they're established or being actually they did it in a group discussion they did not much agreed upon. But, Brein, I guess you have more insight on this. Brein Posey: Well, one thing we have to remember is that, this is presentably based on a survey result and personally, I think that the number is probably higher than what's even reflected. Let's just assume that it's not correct. That survey result would reflect to how people feel about their own environment. So, part of that could tie back into the budgetary issues and the decision of being made without the involvement of I.T. that I talked about earlier. But part of it too can also be tied to the inability to effectively test because no matter how good you're testing is there's always going to be a limit to what you can do. For example,

9 you can't just go out and burn down your data center to test through fire contingency plans. That's never going to fly. So, what the survey could be reflecting is lack of confidence just because there's an X factor there, a series of availability challenges are never been encountered possibly. Jason Leiva: Right, absolutely. So, in the slide, I'm going to talk a little bit about that as well. You know, often times people don't know that they can even recover from the type of strategy they put in place, right? Because they haven't actually test to there by incredibility of their disaster recovery and the backup of practice that they put in place there. Brein Posey: Yes, exactly. There's a lot of theoretical things but we don't really know if that's going to work when the time comes. Jason Leiva: Right, absolutely. So, how does Veam and HPE address this? We really have five categories or capabilities that Veeam provides along with HPE that we'd like to talk about. We'd like to talk about high-speed recovery. So, being able recover stuff not just overall to say a whole virtual machine with an entire volumes of what you mean when you need. But also being able to have multiple copies of your data in multiple places, so at Veeam we always talk about 3,2,1, three copies of your data, we need two different types of media and you can get one of those offsite. So, we'll dive a little bit into that. But also verify recoverability. Knowing that the strategies you put in place were actually were rather in just sort of filling it over the wall or whatever backup application you have and just trusting that he's doing he's doing job everyday and meaning that there is files appearing on my storage, so I should be good, right? But they can also leverage that data. What we're talking about today is, you know, the ability to take a replicated virtual machine and yes it's there for disaster (economy) but let's talk about how we can use that for doing (sand-boxing) of applications, right, testing updates before they actually get deployed into our infrastructure. But then also, we need to have complete visibility in the entire infrastructure. Planning before thing happen. Let's face it, but, you know, it's really the best of form of a protection that maybe short things that are available is being able to forecast them for it actually happen in the issues or continues some issues in hardware. So we'll talk about that a little bit. So let's talk about high-speed recovery and I really like the statics. It's another one that is out there to say that was done, you know, but really what it's saying is that, you know, 80 percent of the time that a recovery needs to be that needs to take place is actually transactional type of recovery, only 20 percent of the time that someone need to really restore the entire server.

10 So, often times when I speak to people and they say, "OK. Well, I have amusing stories based snapshots. And I have copies of my volumes that have mini VMs on them and I have them stored somewhere else, that's great or I do have a back up but I don't really have you'll have a way to get in there and let's say, "Really, all I want is just an back and I don't want to restore my entire exchange data base." And would say, Brien this is something similar to what you hear when you talk about people just like data availability or strategy that they put in place? Brien Posey: OK. Well I've seen exactly the same thing. And really there have been products that have been in existence for decade that can do transactional level recoveries but a lot of times, those products are really cumbersome to use and it just doesn't make it very to do a quick and easy transactional recovery. Jason Leiva: Well, very good. Thanks for the insight there. And I do want to talk a little bit about, you know, the type of granularity we're talking about. So, we talk about, you know, again, not just whole volumes and maybe VMs not even an entire V.M.. So, what type of granular capabilities do we have with the Veam and the HPE hyperconverged integration here? So the ability to do individual let's say, an recovery, from a Veeam backup or from a hyper-converged snapshots, so we're talking in user's , right? Our contacts, calendar invites, we can look at this also for SharePoint. So for the SharePoint site and we can recover this site now. The individual, maybe objects from a site or documents, things such as that. Let me ask Microsoft active directory. So active directory gives you many levels of resource, so we have computer accounts, there's user accounts groups policy objects. So the idea here is to really give you that granular recovery again from active directory. One of the things I want to mention about all the restores that everything is done in agentless fashion, meaning nothing is unsolved on my active directory server to give me the ability to do this type of granular restore and the same thing holds through all these (lists). So, it's a very angulous fast restoring on just the objects you need and when you need them. So then the takeaway was with the customer who was doing the Beta of the Veeam Explorer of Microsoft active directory before it was out. And then actually have someone delete it was actually I believe the exact number is 1,200 or so computer accounts out of their active directory. And they didn't have a purchase or licensed tool to restore those list, so they try to use the Beta of Microsoft Active Directory Explorer from Veeam. And they were able to restore all 1,200 of those accounts because it does maintain passwords for the computer accounts themselves. Everything was able to authenticate as planned and operations really continue forward.

11 So the success story before this particular list was out there and has been widely used to (start that release) and actually expand in capabilities. Also added this Veeam Explorer from Microsoft SQL Servers. So that SQL server will actually have multiple levels of backup and recovery. So, when I say that, I mean, Veeam traditionally does an image level backup of all virtual machines, again, agentless approach. However, with the SQL, we also giving the ability to grab at log every SQL server and store those along sites of image of a back up. And the reason we do this is plenty of (DVAs) out there, they actually like to have the ability to have granular restores beyond just traditional backup schedules. So, maybe it do backup once a day but the (DVA) says, "Hey, I really need to be able to undo transactions at an increment level in 15 minutes for an example." So the Veeam Explorer for Microsoft SQL server gives you that capability. So, they have image double backups and log backups. You have the granular type of restore capabilities that you would need. So in version 9, we introduce this for Oracle as well. So, just like SQL, it has image double backup and also being able to grab logs and rollback transaction on top of being able to do the individual item recovery. So now, we're talking at the application level. Well, on the slide four on this presentation and naturally Veeam does cover just regular operating system files as well. We actually support 16 different files systems from Linux variations to Windows variations to be able to do that file level type of restore. Now, as I said earlier, 20 percent of the time at least from the study that was done, few people actually need to get their entire server back. Now, if the entire server is down and whole application probably isn't accessible versus just needing to get someone's file and back is just a probably a more critical time to meet the fast recovery. So if you look at the HP HC 250, is the ability to take the storage snapshot and use it as a recovery point. Well, (doing this) as you've taken the storage snapshot and if unfortunately the machine goes down, we're going to leverage the storage snapshot as a recovery point to restore that virtual machine. So instead of leveraging the storage snapshot capability of the underlying storage of the HPE HC 250 along with Veeam's ability to restore the virtual machine. So we're talking about the ability to restore entire server no matter its size within a few minutes. So, it's a very fast restore. Now, naturally I can't run the storage snapshot forever, so at this point, I would be able to leverage native hypervisor capabilities of migrating our virtual hard disk. So, for VMware we're talking storage and motion right, to be able to move to the (inaudible).

12 So we've actually take expanded the capability of those storage snapshot to give you the ability to do all levels of types of storage of Veeam. So, if you think about a regular backup schedule, you may think let's say, someone backups every night, 8:00 p.m. If anything happens after 8:00 p.m. and then you talk about 24/7 operation, right, that it need to always be running so there's always transaction happening. We need a way to have a better recovery point. So, because storage snapshot can happen frequently in the case of Store virtual (VSA) for example, which is the underlying storage of HPE HC 250, right. You could do a storage snapshot as frequent as every 30 minutes. And my example here, I must say every hour. So, this case, a customer has a RPO of every hour, so they can now look those snapshots and Veeam can do file level recoveries and VM level recoveries. Well, even all those applications that we spoke about. So exchange Oracle SQL, all directly out of the storage snapshot. We actually refer to as an intelligent for storage snapshots because traditionally store Virtual (VSA), it knows volumes that doesn't necessarily see VMs sitting on those volumes while Veeam does. So we're really adding this capability to have much granular restore capabilities from your storage snapshots. Another integrated feature of the HPE HC 250 is the ability to leverage the storage snapshot as the means of getting the backups. So, obviously, the storage snapshots themselves are the backup, right? If the storage ever had a problem, the storage snapshots will go with it. We still need the visibility to have a copy of our V.M. data that can go elsewhere. I mean, perhaps you want to back it up to store once, perhaps from there we want to go tape or Cloud. So, we have that capability but the reason we backup from storage snapshots and not just VMware snapshots, is used the commonly known issue of having VMware snapshots done. So where someone is done a VMware snapshot and they need to go get raid of it, they need to consolidate. Well, its color for application to become unreachable like I have performance issues when that's occurring. But when we back up from storage snapshots, were not having to leave the VMware snapshots, sitting out there for a long period of time. So what we're having here is a backup process that is not interested which is important. The application is suppose to keeping you align. It doesn't need it to bring you down, right? It doesn't need to take the application down. So Veeam isn't the only company our there who does this but we are 20 times faster than competing products. And the reason for this is because we do leverage VMware change for our tracking to achieve the backing up from storage snapshot. So let's talk about data loss avoidance and usually to get important for having multiple copies of data. So let first talk about Veeam virtual machine replication. So we talked

13 about back ups, we talked about storage snapshots. Well, let's think about the entire site failures, what do we do there? Yes, this is (the own) recovery is fast. We can do that. However, doing that for many virtual machines becomes somewhere of the manual process. We like to avoid manual process to do as much as we can. So Veeam replication actually takes the virtual machines and can replicate them to host hardware there somewhere else. So it can either be your organization hardware to own near our site. It could be a Cloud Connect partner so Veeam has a network of partners that actually provide infrastructure. I think they replicate your Veeam's too. So if you don't what to host your own (D.R.) side, they take that very available to you. So when a disaster occurs, you simple have the ability to do failover plan as we call it. And when failover plan is, is you're saying "OK, I want this Veeam number one to power on. You know about, I want VM number two to wait 60 second." A use case here will be domain controller for example before you bring on when exchange server, you want to come online do what their become monitor specific order for your application. At that point he was going to power on, those virtual machines if there's different subnets, if their I.P. address (inmost) that will be an automotive process as well. Windows base operating systems. So the example shows here. I may have on my primary side but then I have one on my (P.R.) site. So between the I.P. address is automatically for you. Now a lot of people say, well I can't do the vast to recovery because my bandwidth is minimal. I just -- I was very busy. There's a lot of traffic going back and forth over the land connection to this others site that I have. So Veeam does give the ability and do some of the Cloud Connect partners to deploy when accelerators. Doing when accelerator is, is a global cache of data blocks that have been sent from side A to side B. Just like any cache that means it now while to go continue to run these V.M. replicas. I can look at this cache and then intelligently send only you need the data. Data is common or has been sent already. I will retrieve from the cache and use that to complete my replication job or task, to makes those happened. So this is all integrate into the same product being, you know, the Veeam Availability Suite along slide the HPE 250. Now, how about in back up soft side, so again V.M. replications are great but we also need archive data. We need somewhere to get the backup for compliance purposes, a lot times that's what people need to do, data to be in multiple copies, again 321 is what we would like to achieve. So we can look at (usually) backing up to an HPE go once and taking those off site, you know, to another store ones device. Or we can also use Cloud Connect here. I talk about there a Cloud Connect network of partners that give you infrastructure. There's also Cloud Connect network that will give you back up with your resources or back up storage.

14 So again, if you don't have your own pro-location you would give the ability to license that capability or license the storage from the Cloud Connects partner then you send those back up outside the Cloud Connect. Over that the Cloud Connect is important to mention is, the ease of use. So as a Cloud Connect tenants or consumers of those services, the actual provider would simple give an I.P. address or URL to get to their site and they will give you access credentials and you will input those into Veeam and then magically either infrastructure or backup storage will appear in your (V console). And it simple became to target for you. Very easy and secure. It's a single SSL connection out to that partner to be able to do the transfer of data. And take support, you know, a lot of people as speak they say when they get away from tape and that's go throw once and become immoral path finding another (inaudible) storage technologies but for many people tape is a requirement. They have to do it. Its something they they get the cheapest medium for storing stuff for a long period of time. So that the way that that would look is we're doing our back ups from HPE 250 to store once, or other disc play storage and then those back ups are simply being copied to tape. So it is direct the tape, it is achieve the tape. So verified recover ability. I will talk about this today specifically on those V.M. replicas, that's I spoke about earlier for disaster recovery location, so we have them there, where we know you've created them but we need to verify them that they're going to work. So what Veeam give you the capability do? Is actually power them on in automated fashion, so what we do is we isolate them. So when we power under V.M., they get a cash to a network adaptor that isn't going anywhere, it's by itself. And they are able to communicate with themselves and Veeam is able to communicate into inside of them and actually a series of test. We're going to be able to test for heartbeat, pin, script, the scripts are actually based on the type of the application. You can create your own as well. So, for an example that's (active) directory server when checking for specific ports to confirm that there was the applications listening who can get in to it. Now, you can also leverage this virtual lab as on demand sandbox, those things earlier, what's leverages this data? Especially on that the outside, instead of majority of the time and master the disasters just sitting there, you're using. And if you're doing Cloud Connector, you're paying for those capabilities or for (ping) be able to use or to have the replicas is there, so we can power them on the virtual lab and then the user can get accept into this virtual lab. So perhaps, when Microsoft comes out with the new update for Windows, a new update for certain applications, those can be tested against the replicas that are on read only state and verified that did those well have a negative impact when they deployed their production.

15 So very capable help the capability to ensure against replicas work but also to ensure the any updates, that are made to these virtual machines will have a negative consequences. So we actually have extended this capability to store snapshot as well on version nine? So you talked about really the recovering from storage snapshots. But imagine if we could take the snapshot on premises we're not talking replicas here, and we can use it to do our same kind of testing one on premises. So again, the snapshot, they're going to be a read only state here, we're going to power them on virtual lab again virtual lab meaning the copy of these Veeams can't see their production counter parts. And we can get in there and do all the same testing to make sure they are getting issues with updates in such. But what I said earlier really it's important to have complete visibility into the infrastructure, it's a really be a predict issues before they occur. So in Veeam Availability Suite along with Veeam back up in replication, we have what's called Veeam ONE. And again, together they make the Veeam Availability Suite. What Veeam ONE is going to you visibility into your virtual infrastructure, OK? That's going to give you the ability to looking at your back up resources, give you an idea of, "Hey, when we're run out of back up storage with my current change rate?" So Veeam is actually the change rate. He's going to able to predict how, you know, when it is you made to add more resources same thing with the other Veeam back up components. But also in the virtual infracture side, hey, I want to add a new host, you know, or let's say the host is fail even that can my cluster sustain the host failure. Or maybe be I want to add three more SQL Servers that are like SQL 01 and may infrastructure, can I do that? And if I do that, can I still loose my host and keep things running? So be able to plan ahead before issues occur.. But of course there's also monitoring and alerting built into that sweeter (ph) products. So that is 106 years and so if we can figure alarms based on VMware and Microsoft best practices if we're talking how to be, to ensure that, you know, your infrastructures performing in its best. Now, if you're someone who has Microsoft system center, you've already adopted that as framework monitoring and allowing to a infrastructure then you can also add the Veeam measure back. Which actually add all the capabilities, whether you have the Veeam Availability Suite and back up from replication, then ability to go and monitor alert inside of system center? And then naturally any other events and perhaps the HPE may have, you can drag those in there. So now you really do have a frameworks solution where everything is visible, they kind a single plain (ph) or grass.

16 All right so thanks for everybody for being on the webinar today. If you would like some more information, you can go over to veeam.com on the solution's tab. And if you drill down under HPE you'll be able to learn more about the Veeam and HPE partnership and different documents since solutions we have together. A couple that we have specific the HPE and Hyper Convergence. We have actually two documents out there that you can go grab and touch really more about which you combined components. And for additional information from there, you can HPE and veeam.com. If you need help finding a reseller, you can contact (Ken) HPE at veeam.com as well. So you'll be able to point you on the right direction to make sure you can get all the information that you need. All right, we're going ahead and kick it back over to Mike. Mike Perkowski: Right. Thank you Jason, you too Brien, appreciate that you're covering a lot of ground on our presentation today. We do have a few minutes for our couple of questions from our audience. So Jason, I'm going to turn to you for our first question here. First, we want to know if special Veeam licensing required to intergrade with HPE storage? Jason Leiva: Actually. So the certain features are included in all versions of Veeam back up replication or Veeam Availability Suite actually., if you'd like to have the ability to back up and storage snapshots into perform all your restores as well from the storage snapshots, you would need to look at doing to Veeam enterprise plus addition. However, even down to the Veeam standard and you do get basic stored capabilities from the storage snapshots as well. Mike Perkowski: OK, very good. I think he touched on this next one, but I'm going to ask it so that everybody can hear it again. Which hypervisor does Veeam support? Jason Leiva: So today, we support Hyper-V and support VMware the two hypervisor we support today where, that does mean we never support more but it's really all about, you know, the number of costumers who come and ask, you know, for more, you know, that's all based on demand actually,so. Mike Perkowski: OK, very good and so from the virtual world let's go on the physical world, how does Veeam handle physical servers? Jason Leiva: Yes, absolutely so, into today Veeam does not have a physical back up solution. We have introduce recently a product called Veeam Endpoint protection so in the name, you can have and get that fact that it's not for server but it is for endpoints, so laptops, desktops. However, we have had a handful of costumers who have because they have one or two physical servers they've use this product to back up those servers as well. I mean actually

17 can point those back ups out to a Veeam back up and application repository. So for example, if you're using store one (ph) you can say, "OK, I want where Veeam Endpoint is installed to point now being back up to server. I will send back ups there. Now, we have already announced coming later the year that we will have Linux back up as well coming from Veeam. So that something to be on look out for. And you never know, one day we may have a full blown we'll quote the name but Veeam back up or traditional servers or something. Or maybe we'll get there eventually. Mike Perkowski: OK, very good. That concludes are program for today, I want to thank our experts speakers Brien Posey and Jason Leiva for taking time to cover a lot of ground for answering some of the questions, we do appreciate you taking time with us today gentlemen. I also want to once again acknowledge and thank our sponsors for today's program, Veeam and Hewlett-Packard Enterprise. We really appreciate your support. Last and certainly not least we want to thank all of you and the audience who participated on this program, we do appreciate your taking time out of your busy day. And we hope that you'll join us for a future web seminar brought to you by TechTarget and its partners. So on behalf of TechTarget I'm Mike Perkowski, thank you once again for joining us. We hope you're all have a great day.