Demo of Veeam Backup and Replication Version 11 (v11)

there we go how about that there we go okay all right i think we'll go ahead and get started here so as i said uh veeam backup replication v11v11 that's obviously the theme of today's discussion um brandon and i did this uh webinar i think it was about two weeks ago um kind of really discussing about the things that we felt were important and useful in b11 um and today the goal is to kind of circle back around we'll kind of hit those again at a high level but brandon spent some time actually doing some demos today uh and showing some of the stuff that we've been talking about and also we'd like to really encourage people you know certainly ask questions during the um presentation heidi's online she'll check the questions she'll certainly uh funnel them out to us and the things that you'd like to specifically uh see within the demo or ask questions about don't don't hesitate okay sounds good okay okay just real quickly again uh we store com um even you know in the management movement protection data for uh two decades now we are veeam cloud service provider we have uh our own msp practice multiple data centers in the midwest um and we are focused on providing uh best and breed solutions uh veeam um and our experience uh around disaster recovery and business continuity um and that's kind of how how we you know came to be working with you work with many technologies over the years and really um come to uh see all the benefits of this platform and watch it grow as a technology and i think brandon uh you can speak to a little bit of your experience also with me yeah absolutely oops uh yeah so i've been this is brandon mccoy senior system engineer at veeam software and i'm in atlanta georgia uh working exclusively with our veeam service providers and so i've been here a little over four years and definitely as well seen the platform grow from just you know virtual backups to now physical sas cloud offerings and a lot of the features and cool things that we're going to demo today so i'm happy to happy to be here and happy to show this david do we want to go through um these sizes again as well or do we just want to kind of jump into the um just high level i was just going to hit this which is basically the whole foundation why we're doing demos and so forth is basically the challenges around ransomware um cloud mobility and uh better data protection is really what's focused uh i think a lot of what the features that we've been talking about in veeam version 11. um we're going to get into these a lot it's a lot more detail so i don't think we really spent too much time on the slide but i think that's just you know these challenges really would draw wallace again you know there's 200 plus enhancements here we're obviously not getting into all these um we're trying to hit what we think are the most important certainly we can have conversations with anybody around specifics afterwards if there's things that you'd like to learn more about yeah and david i think that we kind of talked about this last time right we took these 200 enhanced missing features and we're going to show some of the core ones but we kind of boiled it down into three main themes security cloud mobility and recoverability and i'm definitely going to be demoing some of these is there anything you kind of want to highlight here um no i mean i think we you know we talk real quickly uh about um i think you know seeing a demo and understanding from a data immunoability standpoint i had just a number of questions recently about this more and more and we you know at storecom ourselves we are now leveraging these uh mean hardened uh repositories uh leveraging linux xfs file systems but i've given more and more questions about what does that really mean and and how does that help and where where does object storage fit into this so i think this is a good segue to you kind of diving into the interface and really not just talking about but understanding what does that really mean what how's that and there was actually a point to that too there's there was a great question on the last one about uh you know configuration of things like a hardened repository and immutability around you know well if i made a mistake and i said something a certain way i didn't mean to be you know what is that what does that do to the system can i can i make changes to that you know no um but i think being able to see that today would be useful so people can understand that's the whole point of this is that your data once it's set in this mode cannot be altered which is really what is driving a lot of this from standpoint of compliance and ransomware protection yeah absolutely david so what i'm going to do i got a lot of different labs open because we're showing a lot of different cool products so bear with me as we uh you know skim through them but uh what i wanted to do is kind of take you guys through each each of these so we're going to start with security we're going to talk about linux and object storage harden repository that object storage is how we're going to piggyback into cloud mobility so this is where we're getting into not only using object storage as a repository in the public cloud but also being able to backup cloud workloads we're going to look at veeam backup for azure and we're going to talk about a few of the other veeam backup for uh you know fill in your public cloud and then from there we're going to talk about recoverability as well because being able to you know back up and restore in and out of the clouds also kind of leads us into that third category so we're going to take a look at cdp one of the newest and biggest features of veeam version 11. that's continuous data protection and expanded instant vm recovery so we'll talk about some of the new features instant recovery has been around for a long time but we've really expanded upon that and so hopefully that'll give you an idea of kind of where veeam's headed and uh some of these three big themes with some of those features so uh if there's nothing else from you david i'll jump right into the first demo let's go for it all right so again i'm in uh got a lot of stuff on here so there would be oops okay so we're going to start with the security piece so this is going to be immutability for both linux and object storage it's also going to be a mutability i'm sorry hardening the repository so there is a difference in immutability between linux and a public cloud and that's the hardening of your on-prem repository and i'll show you what i mean here so in my veeam this is veeam backup and replication for those who maybe don't know and we're on version 11 and i've got these scale out repositories and just at a very high level scale out repositories allow you to combine multiple veeam repositories into one and that is how we hook up to object storage as a repository we land on a disk first from there we can copy and or move backups to an object storage in azure uh google and a few others as well so from these repositories i've got one that has linux immutability on it so we're gonna start there so what i'm doing here is i'm adding my linux repository as a target so that i can send my backup jobs to it and we've supported linux for a very long time in version 11 excuse me we've got the hardening the immutability and the xfs and so i'll talk about all those a little bit here just take a moment to verify this so we are using the first thing i want to talk about is the the hardening of this repository so before we can go into linux and make things immutable um we need to enter in some credentials i got to go back for it to uh prompt me on that so these are the credentials that we're using and this is a demo lab it's not um you know anything too highly uh vulnerable or valuable so we're just using regular root credentials and this is how we did it before you would need root credentials in order to attach a linux repository and write to that with and those those credentials are stored in the veeam server so if somebody were to attack and get access to that database they could possibly extract uh the linux administrator keys and then go into linux and just uncheck the immutability um so it would kind of defeat the purpose of making these backups ransomware proof so now in version 11 when we add our credentials to the linux server we have these single use credentials so this is going to be single sign-on one-time password we're not going to store these keys here and that way you know you're you're protected so first before we even get into ransomware proofing the data we have to harden the repository by not storing uh these credentials here once we've done that i'm going to go back to the uh i have to run through some of these bear with me we're going to go back to the repository and i'll show you the immutability uh the immutability is very simple it's a it's a simple checkbox and and i'll kind of explain what it does and by the way a great great time while we're waiting here if you guys do have questions feel free to put those in the chat and you know heidi can we can try to answer those in real time if you'd like or we can answer them towards the end okay so here's my repository uh i've got the xfs like david mentioned so if you see here it says xfs fast clone um so if you're familiar with refs and these are just file formats for windows and linux disk and veeam has been able to integrate with those kinds of repositories for a long time with the refs and it uses internal windows dedupe so when full backups need to be created uh synthetically we can use the internal dedupe to say hey those blocks are already in the repository because a synthetic full backup so for instance with veeam you know your weeklies monthlies year these are gfs those are all backups that are being created from existing restore points in the repository or existing blocks so rather than having to create another full for say a weekly or monthly we can just look for the blocks that are already there and update the metadata of those blocks and it'll save you a lot of space for those long term backups also any kind of merge operations so when the oldest backup has fallen off and we need to move the delta into the next block and move the backup up with uh with our afs that merge operation is significantly improved i think anywhere from minutes to hours depending on the size of the data and so xfs is just the linux version of that and we now in version 11 integrate with xfs as well so not only here are we talking about immutability and security which is the main point but i did want to point out that that xfs also makes things more efficient and saves a lot of space not to knock on microsoft but we're seeing about a 25 performance and increase between xfs over the power line so there are some other benefits there leveraging the linux system yeah that's um that's very interesting you know on the demos and calls that i've had i'm i'm hearing xfs a lot more linux is something that i've always kind of you know in the background yeah i've got a linux repository or i'm backing up a linux server but with the uh improvements that we've done with veeam integration and the xfs some other things uh we're seeing that a lot more uh common now so um what's cool is that what being done here is i mean it's really not that difficult to set up i mean yes you do have to have a linux machine um you have some basic linux understanding um but but after that i mean what what veeam is doing here is basically it's doing all the back end integration to turn on these flags within the file system so you don't really have to know anything about linux file systems to build a matters this meme is doing that it's just taking care of that process for you yep that's that's absolutely right uh like i said i don't have a whole lot of experience with linux so it's good to know that you know you can easily take advantage of these by just uh leveraging veeam here and um so that's a great point david and that's what we're doing here so you know i've got the linux repo repository hardened i've added it in without say storing my root credentials now i'm going to make my backups immutable and so immutable just means never changing right and so from a technical tech software perspective that means these backups cannot be deleted and they can't be modified so ransomware cannot encrypt they can't write to them because they're read only and you know if a malicious employee tries to delete the backups or maybe they want to get sneaky and they they change this to one day that doesn't affect backups that are already there so um and that was kind of to the point you're making earlier david with uh the great question we got on our last um webinar was what if excuse me what if i made a mistake here well unfortunately you're just going to have to keep that data for you know that additional amount of time right but it does make it great that that it's available yeah instead of 30 days whatevs if you fat fingered it made it 300 days wow right he's staying there for 300 days there's no there's no way to get around that but that's the whole that's the whole purpose of this because you know even the msp being obviously you know you know we shouldn't live without anything malicious to our own customers but i mean even if we had a rogue employee they can't delete it either nobody nobody can make these changes once this has been set it cannot be changed and as you pointed out with one time usage keys the key after that once the credentials are set there that's it there's no access that that you know making those changes again yep and uh that goes as well for the retention policy i remember when immutability first came out with veeam like in version 10 and uh there were some interesting questions that i would get asked and i had to research and find out like well what if you know i set my immutability for seven days but i set the job for two days well the immutability still trumps they won't even let veeam delete its own backups right so and that can be a great thing for a lot of obvious reasons okay so um i'm gonna show an actual kind of what would happen if somebody did try to delete but i'm going to do that from the object storage just so we can see how that's set up as well it follows the same principle these backups are you know untouchable so that's the linux piece i'm going to skip over to the object storage and i'm actually going to use a different one so just a little disclaimer we integrate with a lot of different object stores public cloud not all of them offer immutability and that's just because they don't offer immutability at the block level a lot of what veeam is doing here from linux and for the object storage is just using their technology and we're creating apis to make that easy so that your veeam backups take advantage of whatever those are um so aws uh uh there's a couple others that aren't coming to my head right now but aws is the one i'm going to use for this aws does support immutability and they are an integrated object storage provider of ours so i've got this aws immutable backup and this is also part of our um expanded object storage support for glacier and deep archive with azure so you know your backups can go to a traditional s3 and then it can go to a deeper archive like glacier or azure deep archive and it's a lot cheaper it costs it can cost a lot of money to restore your data especially if you do it too early but it's great for like hipaa compliance and things like that so figured i'd mention that as well while we're while we're on the object storage topic so i'm right now i'm adding in uh an s3 bucket um which is you know just uh it's a for those who aren't familiar object storage it's just a pay as you go unlimited capacity and it's best referred to as a bucket because you just store things there you dump it there and you pay for what you use and it's very cheap compared to disk based so i'm just adding in that bucket and then i have this right here which is making backups immutable for x number of days now we don't have to do any kind of repository hardening or anything like that with object storage just because it works in a different way you know you've got an aws storage account that is completely separate uh from here and and even if i were to get into that account we're locking versions down of the on the bucket level so you can't make changes even if you do have uh the passwords and permissions to do so so it's even easier and so i can say make my backups immutable for 30 days just like we saw on the linux okay it's just set up at this bucket level here so what i'm going to do now i've got you know both linux and object storage hardened repositories i'm going to choose one and i'm going to go with the object store and this is a veeam backup it's got 20 restore points on it right maybe some super critical data and i'm a malicious employee or just you know maybe not the brightest and i'm going to delete my backups from the disk or in this case the object storage okay and it's warning me hey are you sure because you're going to delete all of your backups and so that's what i'm doing i'm doing we're going to give this a second it should fail pretty much right away now that you're taking a little bit of a break we have a question and that is is immutability a veeam feature or a property of the target linux or aws yeah great question so so it is a feature of the object store or the linux the repository that we're writing to like i said veeam and a lot of these cases are leveraging whatever the underlying capabilities of these storage platforms are and you know we're hooking into those to keep the veeam data safe yeah that's right so you know veeam is basically take that through that gui it's basically changing the flags on the file system so you don't have to understand how to do that at the end underlying at the file system it's just like if anybody's familiar with the old you know dos attributes of read write it's basically there's another flag on there for immune ability and when that thing has been triggered it cannot be deleted based upon the retention that's all it is is a flag on the file system and beam is basically you know the apis to understand how to write to xfs or to objects and i'm you know i would expect that refs eventually will have some something similar to this um rfs is not as has not been around as long as xfs has um so um that would be so i think as you were saying ram right here you can see where it failed to delete it right and the continuation of that question is can you choose a local linux target and use immutability if so what versions of linux is supported as a target yep so um you can absolutely use a local linux repository and um it's supported linux os's i'd have to get i have a list of the disneys i'll try to look them up you can google it uh just linux immutability system requirements and it'll pull up but i'll try to find it here in a moment after the demos and give you a list of those okay yeah great questions cool so um david anything else on this security piece before we transition into the uh cloud mobility no i don't think you hit the obviously the the main benefits and we just saw there is how you were not able to delete this and and uh whether you delete the job or whatever it is you tried to delete at the end of the day that the lead update is not going to get deleted or overwritten by any type of malicious activity and obviously with object storage um there is one level so so the immutable copy i mean basically the only way that data could ever get destroyed you could you could in theory on an immutable copy volume you could in theory destroy the entire volume um that's obviously the bigger difference between block storage being immutable an immutable copy on block storage on the linux fx xfs file system versus object storage but object storage you can't even believe the volume because they don't object charge doesn't work in that format um it's different than blocks so it that does provide even a higher level of protection because um there's no way to delete even the underlying volume where the with the file system was written to yeah absolutely that's a great great point um that actually was something i experienced when getting used to this and uh creating my first um aws uh immutability and i said it for a little longer than i wanted to and uh i had to pretty much wait i wasn't able to i figured if i were logged in as the root user i could just delete the bucket or but nope once it's locked it's locked another question and that is how are synthetic backup changes addressed with immutable volumes that's a good good question that so one of the things what so the synthetic i mean it's still it's still a change so you're writing those additional changes but you can't recover the blocks that have been you know that are you in theory you're gonna use more storage because you are whatever that time limit that's been set for those blocks to become available they're not gonna become available to rewrite over um until that time until that time brings me that but if it's if it's you're just talking about a synthetic backup with incremental changes it's not really any different because incremental changes are always written to a new location anyway so from that standpoint it's not really using any more storage i don't know if that helps answer that question and i don't know brandon you have anything to add to that yeah because this confused me too when i first heard about this i thought veeam would never be able to continue writing to the chain but it's not the chain per se that's locked it's the individual block files like the veeam backup veeam full backup as a vpk the veeam incremental is a vib those are locked down and if we needed to create a synthetic full where we take the vips that are already there and recreate those into a full backup we can do that because the backups are read only and that's all we need to do we need to be able to read those blocks and then rewrite those to a new vbk file right so so the the the if if you set the retention if you if you set a retention policy to 30 days whether you're using a mutable copy or not it's still set to 30 days and after 30 days uh those blocks will become available um even an immutable even with the universal copy turned uh turned on those blocks would then become available because the retention policies were not it all mutable abilities really doing enforcing that retention policy that there's no way it can possibly be altered yep yeah great questions all right so um like i said i wanted to kind of use the piggyback approach here so we went from security with linux and object storage and so with that object storage comes this cloud mobility so being able to back up to object storage um this big one has been around since version 10. in version 11 we've added this support for tiering off to different uh levels of object storage from standard s3 to a deeper archive and then we also came out with three different products uh and we've released these in different um times and so they're different maturities so we've got veeam backup for google which is on version one so veeam backup for google you know you've got instances workloads running in google that you would like to back up um and keep for a certain amount of time so protecting workloads already in there that is on version one veeam backup for azure is on version two that's what we're gonna jump to here in just a moment and that supports application aware processing backing up to you know a blob bucket keeping those backups for a certain amount of time based on snapshots and then just real quick while we're on it veeam backup for aws is on version 3. that's the most mature product it backs up application aware and it also does database backups and virtual private clouds so being able to backup those different cloud workloads and you know i would assume that as the other veeam backup for x uh improves it'll you'll see those same kinds of um services being added so that's where we're gonna go all right so this is my veeam backup for azure uh instance this is running on a machine in azure uh that veeam has spun up for us so in the azure marketplace you search for you know veeam backup for azure and you choose an ami instance we've got some some specs for you know we have this general recommended size for you to use you can pick a different size if you need and kind of help you with with how much that's going to cost to spin up but this machine is going to be running in your azure account uh if there's any csps who are using lighthouse we also work with azure lighthouse azure and aws are very different in terms of how we can protect the different accounts so with azure lighthouse you can have a csp who has an azure active directory and then sub accounts under them and they want to let customers have their own azure resources under a higher tier or a high uh you know a higher level of ownership and so we can back up those as well by using azure lighthouse so for csps who have multiple azure accounts with different customers but um here i've added in my azure account and i'm going to go i'm going to take a step back actually um to the configuration here and there's a couple of things in terms of getting started so you're going to have the account that you've added in it says here you can only add one azure account and then the repositories and the workers so the repositories are going to be azure blob buckets uh not deep archive is not supported this is just your standard hot uh azure blob and you're able to take snapshots of the azure instances and then we use that snapshot to create a backup uh of those machines kept for a certain amount of time and i'll get into you know kind of the block changes and the policies in the moment but this is where we're storing the backups in these blobs the workers so these are going to be machines that get uh powered on when you need to do the backup so the workers are data movers um if you're familiar with other veeam terminology a proxy for like image-based backups on-prem this is similar to that with the workers and these are just machines within your azure resources so within your v-net within your resource group that you're going to have access to your storage accounts that can back up your azure instances and send those to that blob bucket once we've got that initial configuration set we're gonna see the instances that we have so these are all the machines that are in my subscription or my account uh i can always separate things like maybe i've got multiple regions and i only want you know machines from this region to show here i can do that but i've got these policies and so this is where we're going to set up an actual job and i'll kind of walk you through what it looks like okay so the first was grab the source uh like i said from this account maybe i only want to select you know one or two regions or back up some specific machines by tags i can exclude some machines that i don't care about don't want to back up once i've got the target of what i'd like to back up application and we're processing you know for vss if it's a non linux or non microsoft application like my sequel postgres you can always put in some scripts to do some pre-freeze post thaw operations and the targets that they're going to be going to so uh the snapshots that we have um we can put some tags on those so that we can copy specific ones we want uh and then i'm enabling backup so what this means is so the way we do backups is we take a snapshot so that snapshot is an image of the machine at that point in time and then we use that snapshot to then take a backup now backups are going to be one full and then the incrementals snapshots are always a full image of the machine but the great thing about this is is that when i want to take a backup so you'll notice here if i schedule let me just remove all these for a second i'm sorry my mouse is giving me some issues um okay so these snapshots and these backups if i take a backup at a certain time you'll notice that it automatically assigns a snapshot because we have to have a snap to do a backup and you might ask because i did well if backups are fools and then incrementals so i'm not getting charged as much because it's just the changes doesn't that kind of negate everything when a snapshot is the whole machine every time well luckily public clouds like azure and aws don't care about that they only care about change blocks so even though the snapshot is the same size every time azure and aws are only keeping track and charging you for blocks that have changed in between those snaps so you're still going to get the same and who cares if it's taking up more space it's not our space as long as we don't have to pay for it right and so these are for your daily retentions you know how often would you like to take a snapshot and then how often would you like to take a backup of that snapshot and your retention so i want to back up every hour i want to keep them for three days for the snapshots and the backups maybe keep them for different frequencies as well as different retention uh policies and you know which repository are these going to go to and then it's the same thing for weeklies monthlies yearlies you know this is just going to be your gfs kind of settings so take my my dailies and keep them keep them for one week and keep my weeklies for one month and et cetera okay um what's really nice here is you'll get a cost estimation a nice breakdown now this is not the cost for running this that's a different thing and we'll give you that when you first build it as well but this is saying based on the machines you're backing up the size of those and the daily change rates here's what it's going to cost you and then it's just next and finish so i'm gonna get into what restores as well but i'll pause for a moment um david anything here before i jump into your restore no i think this is uh i don't know i think i think you're covering a lot of them and again as you said i mean conceptually across the platforms there are some differences but a lot of similarities um one thing i'd the one thing i was going to ask is you know maybe you know one of the things we've seen is obviously in a multi-cloud you know approach uh you know how something like this uh might be able to be used when you know uh backing up your azure environment and doing business continuity to an msp uh you know cloud solution provider like a store-com or someone else but you know where you don't want to have all your data or have the capability to know that you know you could spin up environments outside of azure you know using this technology yeah that's absolutely a great point and uh that's something i'm glad you reminded me because i want to touch on some specifics around that um using a cloud provider as an additional location to send those backups to restore into because you know these public clouds they're they're pretty pretty big giants right but things do go down um you know entire data centers and and regions i mean this i t things happen so um it's good to have multiple strategies so we'll talk about that and as we do it'll kind of lead us in but let's um let's talk about restore capability so i'm going to start with what you can do from here and then i'm going to show you what you can do when you integrate this with theme backup and replication and that'll lead us into kind of doing like a multi-cloud approach so from the console itself i can click on one of my machines that have a backup and i can click restore and i can restore the machine or i can restore one of the volumes of that machine okay i can also do a file level recovery and i can restore um or i'm sorry i can i can download uh the file to the instance that i'm accessing this this azure machine from right and through those individual files so from the console itself full machine disk and individual file and we're gonna we're gonna say bye to backup for azure and we're gonna go into the veeam console here and so this is kind of to your point david and and it's it's going into cloud mobility and then it'll lead us into recoverability as well so this is a veeam backup and replication server and i've actually got this connected to my veeam backup for azure and my veeam backup for aws that integration is not currently available with the google cloud backup because we're on it is the newest of our products but i imagine it will at some time because none of these integrated with veeam backup and replication in version one but they did buy version two so i've got my inventory here or maybe it's under backup infrastructure and i've got the veeam backup for aws appliance and the veeam backup for azure appliance so what does that mean well first of all it means that the backup jobs that i did there can be seen from here now i can't really edit and control the jobs from here if i click this it's going to bring me back to the url for that azure instance but it's really cool because it still does give you like the shortcut to get there i can push a start action job from there so yeah it's just bringing me back to that same that same instance um but let me show you some cooler things in just a second when this stops freezing on me so your windows open yeah yep and uh just lost my connection okay um i think we're in the right place right yeah and um while while i'm uh waiting for this to unfall i think we have another question uh heidi in the chat i heard a ding um there was a question that asked whether or not you can back up to uh storcom for dr purposes but i think you guys just answered that i think somebody asks here is uh v managing console client server-based or web-based i think in in there's the console that brandon's in right now is uh client-based um and when he was up in azure that is a web-based and then there's something called then there's there's an enterprise reporting manager that that's that's also using a web server um that gives you visibility from reporting server reporting standpoint into this yeah that's that's correct and so the yeah all veeam is only software we don't offer any kind of web-based solutions per se but what we do is like that veeam backup for azure that i was um on a moment ago and then i tried to get back to just now that is an azure instance running in your azure environment um and you're accessing it over a url but it's not something that veeam is hosting okay hope that helps um so yeah so what i was trying to get at here is you know yeah it's cool to see the jobs here and it's cool to have a shortcut but it's just gonna take me back to the you know veeam azure so what's really the purpose of having a machine running this um well you can do a backup copy job so if i come to my backup infrastructure you'll see this external repository and this this was a lot of confusion for people because they thought this was how you back up two s3 buckets from like your on-prem but this was a feature that hadn't been released yet when we put this into the into the console gui but the reason this external repository is here these are for those repositories that we just backed up our azure workloads and our aws workloads into and we can now use those repositories and uh do a backup copy job to say storecomm so i'm backing up my azure instances natively from azure into an azure blob bucket that bucket is talking to my veeam server here and i can tell my veeam server to take that data that backup file and send it to my service provider storcom and then now they're going to have that data in their location that they could always you know do whatever you needed if you you know had to give them a call in case you need to restore so um the last thing i want to touch on here and this will kind of lead us into the recoverability is um in version 11 we came out with instant vm recovery of any veeam backup to hyper-v in version 10 it was vmware so what that means is if you want to instantly recover a machine from a backup file you can do that and then before it was if it was vmware you had to do vmware if it was hyper-v it was hyper-v if it was you know physical to virtual was very limited now you can pretty much take any veeam backup and restore it to vmware or hyper-v and azure backup is one of those so i've got some backups here and i can do instant recovery i can uh you know do the files and stuff that i could from there before but this instant recovery will allow me to restore to a hypervisor so maybe i have the backups in azure um and you know for whatever reason i don't want to spend those up in azure maybe i'm migrating out of azure right i could use the veeam server to to do kind of a public cloud native machine and turn it into an on-prem virtual machine and that gets us into the final stretch here of uh recoverability so there we go so the um the expanded instant vm recovery so instant vm recovery is a great way to be able to restore very quickly you know those recovery time objectives i don't know why the resolution is so small here uh but it's uh and it's all from a backup file so with cdp with replication you have to have more resources you have to have two uh vmware hosts um or for replication maybe two hyper v hosts but those are uh you know full copies of the vms that are sitting on another data store um you know taking up more space than if you were to just crunch about a bunch of vms into a backup file and have that low overhead so with instant vm recovery you can now restore multiple machines at the same time you can do like i said vmware to hyper-v hyper-v to vmware physical to virtual and instantly recover it the reason that you may not want to use instant vm recovery however is because you need the full i o stack so think of instant vm recovery as a spare tire you can get back on the road very very quickly but you can't go 100 miles an hour on that tire and you can't drive on it forever either it's a temporary solution until you you know can take care of your business so replication we'll talk about that first that's been around but just to compare it to cdp replication is using snapshots to replicate a virtual machine disk to another host or cluster or data center and now you have a copy of your machines powered off ready to come on in a moment's notice do a complete failover plan so still from a recovery time objective that's very good you can be up and running in minutes and now you've got your full i o stack you've got that full tire it's not a spare and you can you know fail over and fail back but there's also the problem of recovery point objectives so how long in between data protection um is there a gap right and so when we're doing replication replication is based on snapshots and so people say well how often can i replicate you say well as quickly as you can do a snapshot so you can set replication to continuous on the schedule but that's not the same as continuous data protection continuous means is when i'm done i'll do it again so you may have 15 30 45 minutes or longer in between how often you can take a snapshot because of that process so in version 11 we released cdp and i've got a job here now cdp is only available for vmware and it's not supported with cloud connect so it's going to be host to host so if you have two you know private vmware hosts this is perfect when you're worried not only about very quickly recovering your whole data center or tier one applications but also when you can't afford to wait 10 minutes every time you know in between whatever blocks have changed so i'm going to come in here and i'm going to walk you through a job and kind of show you some um [Music] some options here so this is my cdp policy right and i'm going to pick the virtual machines that i would like to do the uh cdp i want to call it replication but i guess it's not what it is uh and the destination um the resources that i'm going to use so this is most of the stuff so far is exactly like replication if any of you have been have seen that and been familiar with it you've got proxies uh the proxies are a little different so with veeam and traditional replication proxies are windows machines taking a snapshot the proxies here are actually called cdp proxies and these are deployed uh directly onto the vmware stack itself using something called vaio and this is how we're able to capture blocks a lot faster and and bypass using snapshots so in the scheduling here i'm going to explain two things and kind of how it works at just a high level so i've got my recovery point objective so cdp continuous data protection does not mean that every change that is made i'm immediately journaling that and copying that what it means is i'm going to set an rpo of 60 seconds okay because every 60 seconds i need to see whatever i can't afford to lose more than 60 seconds worth of data change right and so every 60 seconds the target side cdp for my dr is going to come and check at the source side and say hey what's changed in the last 60 seconds oh i see blocks a b and c have let me go ahead and journal those okay and i'm going to keep those and add those to the blocks on the replicated uh side then i have my short term retention so how long do you want to keep those 60 second changes for and this says here the bigger the interval is the more disk space is required because keep in mind not only are we changing blocks every 60 seconds but we have to keep track of those 60 second increments for a period of four hours right so this is for you know the more short term and then if you want you can also do long term as well and kind of let go of some of that you know hourly or you know four hours whatever and do like say eight hours and um dailies as well for how what you know in what uh state we keep your replica machines yeah anything to add there david that i'm missing well i've got a couple questions for you guys uh the first one is can you put bandwidth limits for replication jobs you sure can um in the backup settings here what you can do is uh you can set your network traffic rules and you can throttle during specific times of the day bond specific ip ranges as well and the second question is when restoring vms across platforms like vmware hyper-v should one be concerned about any issues booting the virtual machines where tools need to be used to fix mbr on the disk um i'm not sure what mbr is uh david yes it's all about master boot record issues i mean no that that because you're doing a direct image so that really is a function of the source source side issues um there are a lot of ways to fix that stuff and whether it's a replica or cdp um that's more of a function of kind of handling the business continuity side of things and and troubleshooting those types of issues and that's a great question um we see that you know kind of i wouldn't say all the time but we certainly see that pop up um i mean you know it's garbaging garbage out to a certain extent i mean if you've got a bad vm on the source side you're gonna have a bad vm on the on the target side so we have to keep keep that in mind um so that that would be kind of the the answer to that question is that we need to evaluate you know what what's going on with the mbr or if there's changes that are needed to be made to the mbr to to address that problem um one thing i was going to bring up uh is there any more questions nope um so i mean i think what's what's important i brought this up last time don't understand um you know is the difference between cdp and replication and really understanding where one hits versus the other now you know you it may not be you may not need to do cdp for every system in the in in your entire stack um oh but the most kind of important place to think about this is um that replication beam replication vmware replication i mean any anybody who's using quote unquote replication via the vmware snapshot process which is what has been using up to this point is that you're using a vmware snapshot and a vmware snapshot has a process where during the cleanup after the snapshot was taken which is called stunning there is a pause and i o and that pause and i o potentially can cause problems in highly transactional uh database environments so this is where for us this is you know this is the probably the one of the most exciting features because we've had to use other products to get around this in the past now those products may be things that are inherent to sql itself um we're certainly not saying that's not still a good option uh steeple always on availability groups but there are other there are other outside products that do this too um cdp has its place because of that one reason so there's um you know there's the very very low recovery time and recovery point objective there's no doubt that there's benefits there but there's also this other glaring issue which is we've consistently had to use you know other types of cdp technologies for environments where they have databases and they're an oil lltp environment um because of the timeouts that occur so now we're excited because we're going to be able to use and leverage one product to handle all this because we have clients who literally you know for ninety percent of their of their of their systems beam replication works great um they don't need cdp for all this but there's that small percentage of machines which again typically are databases that they do um and that's where this gets tied into and those are the places where they're you know that leveraging a a kind of a a whole mixed bag approach of between replication and backup copies you come up with a full business continuity plan based upon what the customer's needs are um and they meet that without obviously affecting production because the the main thing the main thing really here again to reiterate is with cdp the way the cdp solution works is you are not touching the actual vm itself you're splitting the data using that vio process which is vmware basically apis you're you're splitting the rights into a into a journal versus leveraging a snapshot so along with the answer to your long-winded comment there but i just want to drive that point home which is why this is you know so important yeah no that's a great point david it is more than just the the rpos it's it's also some of those yeah those specific use cases of applications like you mentioned great point well that's all i've got on the demo front um and it looks like we're about nine minutes at the top of the hour so if there's anything else from anyone in the game or if there's any other questions out there uh happy to discuss those because i know just back to the cloud mobility and i know this is a separate topic but i just want to kind of point this out um in case anybody you know is even thinking about this because i noticed this on your desktop but you have a cast and k10 demo which i think would mean you're going to try to do something on that uh in the future here but you know for for for people that are starting to look at things like kubernetes in the cloud and how to protect that data um it's definitely again at the forefront um that's not a b11 feature but there it is a it is part of the you know will be part of the suite it's a product that they're that they're working with um and that might be something that you know some people may be starting to look at um because that's gonna become you know backing up instances in the cloud is really what we've been focusing on today well when you start to look at cloud native applications and you're looking at you know kubernetes type database structures uh you know all of the everything that makes up the cloud native platform you know becoming backing up containers you know is a different completely different process than what we think of when we're dealing with vms um and that's going to be a big part of cloud mobility moving forward so i just want to i just want to point out that veeam is still continuing to to go down that path and we're going to see a lot of exciting stuff coming up here probably the next year yep absolutely all right i don't have anything else i don't think any other questions no other questions right now okay well thank you brandon appreciate great job doing all these demos and appreciate all your insight yeah i appreciate you guys anybody has questions feel free we'll uh we're here to talk to you at any time and love the conversation okay all right have a going thanks a lot everyone take care

Channel: Storcom, Inc.

Views: 5,570

Keywords: Veeam, Veeam v11, Veeam version 11, Veeam Backup and Replication, Veeam demo, Veeam v11 demo, Veeam version 11 demo, v11 demo, Veeam 11 demo, Veeam Backup and Replication v11 demo, Veeam Backup demo, Veeam replication demo, Veeam CDP demo, Veeam object storage demo, Veeam CDP, Veeam object storage, Veeam Backup and Replication v11, Veeam Backup and Replication version 11, Veeam webinar, Veeam v11 deep dive, Veeam Backup and Replication 11, Veeam 11

Id: t7bNg-0V6U4

Length: 52min 7sec (3127 seconds)

Published: Thu Apr 08 2021