Transcript
being a skills and you can create a home lab. So, we are the leader. So, Kira, do you want to present yourself? Yes, of course. Thank you, Blanca. So, for those that don't know me yet, my name is Kira. I'm one of the leaders of the Women in Allies in Tech group. I have been with the group from the beginning. Let me know if you can hear me well. If not, I will change. I'm using my Wi-Fi. If not, I will switch to hotspot because I just had a warning that I might have not the best, okay, great connection. So, yeah, I have been with the group, I would say, from the beginning. And the group is actually also quite relatively new, so it started, it was launched last year. So, how did I end up joining it? I actually met Madalina on one of the Veeam user group events because at the time, I was working at another company which is called Object First, which is, who was an alliance of Veeam, and as of January this year, it was acquired by Veeam as well. So, now it's part of Veeam. And prior to that, I have been working at Veeam, so it kind of makes sense. I was, I spent six years at Veeam, then two years at Object First, and now I'm pursuing, sorry, other things, but I still, I would still like to stay within the Veeam community and specifically in this Wave group. Thank you, Kira. Well, my name is Blanca Navarro. I work for AWS, and I am the new leader. I am joined to the community around one or two months ago. So, for me, it's a pleasure to be part of this community. I'm located in Costa Rica, so it's a pleasure to be here, and now I will give you the, to introduce Leah. Go ahead. Hi, I'm Leah. I am UK-based. I do tech for a job and tech for a hobby, so that keeps me very busy. I do a lot of Veeam stuff in terms of implementing solutions for customers, making sure it works properly, troubleshooting, all that kind of stuff. I also joined the Vanguard program from 2026, so that was something I was quite happy and proud of this year, so it's been very good. I joined the Wave group from about summerish, late summer last year, so sort of about a similar time as Kira. It's just something that we're kind of continuing to build on. I hope we do some good stuff. Thank you, Leah. So, I have a question for the people who joined us today. Have you heard about Women and Allies in Technology before? You can type in the chat if you have heard about it. If not, oh, great. If you have not joined to that community, you can scan the QR code and join about what we are doing, and also if you know Women and Allies that they can be part of that community, you also can share that information with them. The goal of our community is to have a place to relate to professional growth, technology, and events, and also to have posts with conversationals that can share different topics. So, now let's start, and now I will stop sharing my screen, and Leah, you can continue. Magic of technology. Righty-ho. We should all hopefully see a very nice Windows-y standard background. Can't share your screen. We apologise for having difficulties with video conference. That is really unhelpful. Today of all days. Thank you. That is not what I wanted. Pretty, please. Hey! Second time's the charm! Put the fear of God into tech at some point. It will continue to work. So, where are we starting today? We're going to be doing a few bits with Veeam. Kira will have a look at object first. Blanca is going to do a bunch of stuff with the AWS and cloud-based things which she's very good at. I throw on if you know anything about me and rubbish for cloud stuff. We will have to let her take over for that bit. As for myself, we ended part one with our kind of base platform set up, but we never really touched on the how to install Veeam back up and replication. So, that's kind of where we're going to start off today, right? It's how do we actually get Veeam back up and replication installed? Now, if you're doing this in a corporate environment, you guys will have a Veeam login. You can go and download that from my.veeam.com. You can grab the community edition if you want to go ahead and use the free version. I will be providing an NFR licence for this, just because some of the features we're going to use later do not work with the community edition, but you can definitely play about with quite a few bits off the back of the community edition. Now, I've kind of pre-downloaded this ahead of time, as it's like a 20 gig file and it's quite large. Now, the one we're going to be having a look at today is going to be Veeam 13. We kind of did start by looking at going down Veeam 12 beforehand with the part one things. Then Veeam have released to us the glorious version 13, which has a lot of really nice improvements. So, we've kind of shifted over and going to start having a look at getting that installed today. Yes, we're going for Windows. The reason why we're going for Windows, as opposed to the Linux appliance, is so that you can apply some of this sort of stuff into your own stuff with the community edition. The community edition, unfortunately, is not available as the Linux appliance requires some form of either NFR licence or paid subscription. So, that's kind of why we're looking at Windows today. So, it just kind of gives us a bit of a wider audience, if you will. As for installing it on Windows, it really is as simple as mounting that disk image that we downloaded, double-clicking the setup.exe at the bottom of that, and then sort of clicking the install button. We'll be presented with a few options. So, we've got the choice of VBR, Veeam Backup Replication. We've got Veeam Enterprise Manager, and then the console. So, the console we can ignore because we'll get that as part of VBR. We're going to actually install the backup server. So, that's what we're going to go with. Enterprise Manager is quite nice if you have multiple Veeam instances in a much bigger scale environment. So, that's kind of what that is. So, we'll select what we want to try and install. That wizard will go and initialise. Anybody in here done Veeam installs before? Or is everybody quite new to this? There we go. Once that kind of – oh, yes, David, I can see you've got your hand up. Oh, I managed to answer my question, but that's fine. Yeah, I did one a few weeks ago. We'll first get asked about licensing. So, we need to make sure we accept the license agreement. So, we can just kind of click accept on here. Now, with the Community Edition, you can just click next and not provide a licence if you want to go down that route. You can log in with your Veeam account, or you can browse to a local licence file. So, in my case, I've pre-downloaded my NFR key. So, we can go ahead and select however we want to licence this and click next. What the system will do is it will then run a configuration check, and as part of that, it will check if there's any software or other dependencies that the system doesn't have that it will in fact need. And what it will go and do is it will kind of enable all of those as sort of part of this. This can take quite a few minutes. So, there we go. You can see it's kicked in with the enabled missing features. So, that just goes and downloads various different packages in the background, puts those on the machine, and then gets everything prepped and ready for Veeam to get installed. So, system spec-wise, actually, we didn't cover that. Specs for this machine, it's nothing massive. So, I've just kind of opted for four virtual cores on this virtual machine and 16 gigs of RAM. You can absolutely run this on a lot less. If you're going to put this in a work environment, I wouldn't go lower than the spec for Veeam backup and replication, but it will definitely squeeze on something like two cores and six gigs of RAM. It definitely works on. So, if you're testing this in a lab environment, you definitely don't need anything particularly massive to run it. For work, I would suggest kind of going with this kind of minimum spec because it just gives plenty of headroom, depending on how you grow. Yes, Nico, I do have quite a lot of deployment guides on my website, which I will pop a link to. There's various all sorts of Veeam bits in there. If you want a lot more details on bits, you can throw in. I'm hoping to expand some of the bits up to the webinars, do some more of the free lab bits and try and sort of do this in a slightly different form. So, hopefully that will help other people. And everybody kind of learns differently, right? Some people are quite good with videos. Some people are quite good with text-based stuff. So, once everything's been pre-installed, it will kind of pre-populate everything that we need from here. So, it's going to opt for using a local Postgres database engine. Yes, you can use Microsoft SQL, but this was kind of, I don't want to say deprecated because it is a totally supported method, but it's kind of been replaced by Postgres. It just sort of works fine, doesn't have any licensing requirements. So, we can pretty much just leave this on all the default ports and all the default configuration. There's not really any need to change any of this stuff. And then we can just hit install. This will probably take about a good hour, hour and a half to install. This can take quite a while, but it really is as simple as just going next, next, next through the GUI and it will just kind of sort that out. Important other things to note, this virtual machine or any Veeam server that you do have is kept strictly off the Active Directory domain. Should not domain join a Veeam machine. Increases your security sort of footprint by quite a lot. So, I really wouldn't recommend doing that. And then by movie magic for this webinar, I have another server over here that I've got them pre-installed from so that we can kind of see what it looks like when it's done and we're not sort of sat waiting upwards of an hour for this machine to install. So, once it's done, we'll get the Veeam console on the desktop. We can just double click that to get it open. Since we're logging on the Veeam machine, we can just use local host. We've installed this console remotely. So, remember that installer had multiple options, right? One of those was to just install the console. So, we might install this on a different machine if you're kind of adhering to all the security best practices, which we will get into at a much later point in a different webinar. But for now, for this machine, we can just connect to our local host, as opposed to specifying something remote. You can acknowledge a certificate thumbprint. That's fine. And then we can just sign in. So, we didn't specify any accounts during the sign in. So, this is just going to be whatever account we're signed in with. And given that this is off domain, we're just going to go with the off domain default account, which is administrator. And that gets logged in. Now, Veeam 13 does have a web GUI. So, you can access that same kind of logins just through HTTPS and then sort of throwing your Veeam name into a web browser, and you can get to it. Really good. Lots of new stuff in there. It's definitely missing some of the features. So, this is kind of the thing that Veeam are working on expanding out over version 13. So, it's still very much in its infancy. So, there's quite a few things you can do there, but there's also quite a few things you can't do. So, for the moment, you're kind of always going to need the console, no matter what you sort of do with it. We do get dark mode as a new feature. You can enable this from the little three line settings and then go to color theme and set that to midnight green. I can't do that by default, because who likes light mode, right? We all work in IT. We've all got some form of an IT background. And then from here, we've got access to our Veeam backup server. So, what about adding stuff, right? At the moment, we don't actually have anything that we want to backup with. So, we could go ahead and throw in, let's say, a VMware environment. So, we're going to use VMware, just because that's what I use at home in my environment. So, for VMware, it's really simple. We just point this at the vCenter itself. So, that's our vCenter's fully qualified domain name. We then need some credentials. So, ideally, this needs to be administrator level privileges on the vCenter that we're adding. So, we don't have any at the moment. So, we'll click add. And then we will go ahead and add our credentials in. So, I would absolutely recommend using a dedicated service account for things like this. That means, at least, when anything gets enacted on your hypervisor, you know what account is actually doing it. And you know that it's a service account that's doing it. And you know it's Veeam. You can kind of pinpoint it. If you just use, say, the default administrator account for everything, then you sort of lose track of, you know, that kind of audit trail of, you know, who's actually doing what on a system. So, we can throw our vSphere credentials in. And that will automatically select it. The default port is 443. We've got no reason to change that. Your vCenter should be on port 443 anyway. That's just standard HTTPS. And click apply. And so, give us a warning about the certificate. Just because we're using self-signed certificates, it's generally easy. They're not quote insecure, but generally they are fine. So, we'll acknowledge this and we'll hit continue. So, just give the server a little bit of a check over. Make sure it can connect up okay. Hopefully, there we go. And that'll go ahead and get our hypervisor added into Veeam. So, once this has gotten added and it's collected all of this data, we'll then have a list of virtual machines. And this is when we can start kind of getting into things like doing jobs. Once we've got repositories added in. Any repositories you should add should absolutely be Linux and Mutable repositories. Please don't use Windows repositories in 2026. And once we've got repositories and stuff added and places we can store the data, then we can start actually getting our stuff backed up and go from there. Anybody got any questions on what we've had a quick look at so far? I will take silence as golden. Looks very clear to me so far. Yeah, same for me. I've got to wait for this box to go finish through now. Otherwise, it kind of locks my entire Veeam UI, but we'll wait and see how long it takes to gather disks and other info. But I would say so far we're going pretty fast. I think we will be even able to cover it all. Yes, I'm going to pass over to you shortly. And by that I mean sort of imminently, if you are ready. I am ready. Would you like me to log in now? I won't kick you out? Yeah, no, go for it. You can log in. It won't kick me out of anything. All right. And actually, I didn't check because we had a call today when we pre-configured some things. Is this the VBR VM? Then I log in to the console, there will be an icon or not? Yes. I want to say before you log in, I'm positive I've... Yeah, so what I've done is I've just dropped the Veeam Backup and Replication console on that machine. Oh, yes, I'm seeing it. I'm seeing it. All right. That's perfect. That's perfect. So this will be the same VBR that I'm interacting with at the moment? But I will drop my screen share and I will pass over to you, Kira. That's perfect. Thank you very much. All right. I will turn my camera on and I'll start sharing the screen. And I think maybe one little thing before I start, so for those who probably aren't familiar with what Object First is, so it is an on-premises-based object storage, S3 immutable storage, which is now part of Veeam portfolio. So for those who don't know it, it is available so as a physical appliance. Otherwise, you can also contact an Object First representative and they can also give you a VSA. So it's also a free version. The license is valid for, I think, six months or three months. You can actually ask for either three or six. And you can deploy from one to up to three nodes. So you can actually create a cluster and it gives you one terabyte of storage space per cluster. Then you will be able to deploy it as a virtual template on Veeamware. I know it also works on Proxmox. It might work on other platforms as well. So the configuration of the VSA itself, I will not be showing today. So it's something that we actually have pre-installed before joining this call. But I will drop a link. I will drop a link to one of the blogs that has been written by one of the person in the community. His name is Christian. So he is a Veeam, I think, Collegiate or Vanguard. I'm not sure if he had any changes of statuses. And he is also an Object First ace. So he created, he wrote this guide on how to install Object First appliance. It's not the only article which is available. It's just, I would say, the first one that came up. I just searched for it during the call by typing Object First installation. And then I found that. So the installation, we decided not to cover the installation of the VSA during the call because we were not sure that we will actually be able to cover it all. And we wanted to do installation of the application, creation of the job, adding vSphere, adding two repositories. So we would like to add an on-premises S3 repository. And our third leader, Vlanka, she works at AWS. So we wanted also to add the backend at AWS. And we needed to fit it all within one hour. So that's why I will only show the part once the VSA has been installed. So I would say today, once we figured out all the permissions issues that we had along the way, I would say the installation itself probably took 10 minutes. But I think more. All right. So now I can start sharing my screen. And I will choose this. So I have installed my VSA for Object First. It is a tiny VM. It only requires two cores. And I think two or four CPUs. So it doesn't need much for a one terabyte VM. And after that, we are connecting through the IP address of the cluster. So very, very, very simple. You can join the guide, which has been written by Adrian. And you will see that is something that is quite easy to do, specifically for lab purposes. And it's for free. So why not? All right. Okay. Looks good. So as you can see, I have just installed it. I didn't even put the license in. So without the license, it will work for three days. I have a license. I just didn't install it yet. So what is the first thing that we need to do? Sorry, my screen is not huge. I don't have a second screen on me right now. So I'm doing it without a mouse and just on my PC. So the first thing, first thing first, I need to go down to here. Okay. I need to go down to here. Create new S3 keys. Create key. So what do I need to do? I need to add my password when creating a key. And it's done. So one thing to note, we will be able to see those keys only one time. I would say it's pretty much a standard. It's a standard practice for S3 storage. Not a problem at all. If the keys are lost or whatsoever, you can create a new pair of keys and they will work for the buckets that you have already used. So by default, when we're creating a key just by clicking one time create key, they will work for all buckets. Otherwise, of course, we can create keys per bucket or per folder or per user and so on so forth. And when I say per user, meaning who can use them. So since I will only be able to see them once, I would like to go and add it right away. So I'll click here, add back a repository. So as we can see, there is already a Windows one which is installed. It's something that always happens. Vim prints gives the role of repository to the volume where it's installed. So we're choosing S3. Here we're choosing S3 compatible system. One more time, S3 compatible. And let's say object first I can add a description if I would like to. Otherwise, maybe the purpose of this call, I won't be adding it. So service point, what is the service point? It's our IP address. If I'm not mistaken, it was this one. I think for the region, it doesn't really matter which region we're adding. So I will just leave it as is. So this part is only important when we're talking about cloud-based S3. For on-premises, it doesn't affect it so much. Oh, one thing I'm not seeing. Maybe I should copy those keys somewhere. Yeah, because I cannot now go back. Let me maybe copy them somewhere else. Yeah, if you throw a notepad over, I think the window is so large that it's blocking out the task. Exactly, yeah. I don't know if I can maybe make it smaller somewhere. The program should just scale based off whatever your screen size is. It's probably what's causing it. Okay, maybe like this. Yeah. Is it too real? No? Okay, that's better. Okay, that's better. All right. And then going back to my web interface. And here. So I put a pair of keys, access key and secret key. Okay. Then we're putting on next. The same certificate warning we're seeing as we have. So we've seen the one where we're adding this here, so it's pretty standard. By default, object first uses self-signed certificate. So we just click on continue. Here it says that configuration backup is disabled for security purposes, so we need to make sure to re-enable with encryption. Here. So now it's done and I can go back to my web interface. So here are the keys. I could have pasted them to some notebook first and then maybe added, could have added a bit later, but I just decided to go this way. To go this way. So the next thing that we need to do is to create a bucket. So a place where we will be storing our backups. So let's say, I think it doesn't like that. Diversioning is already pre-enabled, which is what is required for immutability. Here in advance, you can put a region for security purposes just to stay where it is, but it's not required there. So the only thing that we need is versioning and it's already enabled. Then we hit on create. So the bucket is created now. Going back to the Vim console, browse, and I see that I can see my bucket now. So Vim backups. It says here automatic bucket creation enabled, although it will not be enabled for a reason that we don't actually require it. So Vim, when it comes to S3 storage, they have added this feature not that long ago, maybe a year or two, I think on version 12.1 or 12.2. I'm not quite sure which version it was exactly because there could have been issues when we were placing too much data within one single bucket. So it's related to the creation of metadata, which would then slow down the bucket and decrease the performances. So by default, it's enabled for all S3 storage, although specifically for object first, it's not needed. We don't need to go there and to uncheck it. It will be done automatically. So here it will create child buckets. So folder. This is fine, I think. What else? So limit object storage consumption. I don't think we really need it here. I would say we'll just click the configuration to make backups involved. It's actually a very nice change that I liked, which happened on the version 13, because prior to that in the version 12, if you remember, we had a box here and we need to specify the number of days. And this number of days was actually a little bit tricky to understand, because it actually wasn't setting up the immutability, but it was additional immutability, which was already configured, applied, I would say, to the retention. So for example, if we have a job with a retention of 30 days, and then here in the box, we specify another 30 days, it pretty much means that our data will be immutable, not for 30, but for 30 plus 30. So it's double the time. So on the version 13, it's much more human readable. So here, we're pretty much saying that we would like to keep the data immutable for the duration of the retention. Otherwise, we can also add the minimum immutability period, in case if we would like to add some extra days. So we can also add the minimum immutability period in case if we would like to add some extra days. But I think for the retention period, I think most works perfectly for most cases. Then we can click on Next. So here, afterwards, it's pretty standard. So mount server for restores, Linux or Windows. The components already exist, because it's the BBR server itself. Apply. And that's about it. So yeah, we decided to play it safe and not show you how the OVA was deployed. But yeah, it was actually quite simple. Maybe 10 minutes it took us. But anyway, so the guide is available in the chat. So as we can see, there is one warning that it's giving us. It says that unable to enable automatic bucket creation. It's not supported by S3 integrated object storage system that implement load balancing at the smart entity level. So it gives a reason why. So why did you decide to clarify is because sometimes it raises questions when we're seeing a warning, we're thinking maybe something didn't go through. To the contrary, it's a pretty good thing. It's not something that we need. There is already load balancing, which is put into place. And we don't really need to create child buckets. Next. And finish. So that is it. And I think maybe I can give the floor perhaps to Leah. And Leah will probably back up one little VM. And we'll see what's going to happen. I don't know what I think of. It's something if it's something that we want to do, or we can you've got a bit of time. And I think if you log out of the remote session, we can get Blanca because it gives her a bit of time to get logged in. Make sure you delete the session. Otherwise, it'll throw a wobble. Super. So my screen's being shared over. The one other thing that's worth having a look at now that we have an immutable backup source, and it should have given Kira the prompt and it did, but it's always worth trouble checking. You click the little three lines. And you go to the configuration backup tab. What you want to do is you want to make sure that this is enabled. I thought this did give us the warning. I guess it didn't. Always worthwhile checking. Make sure you enable the configuration backup. Make sure it goes to immutable storage. 10 daily backups is fine. Throw in some password for the immutability encryption. Want to make sure those config backups are encrypted. Okay. Two reasons you want your config backups encrypted. Firstly, it stops somebody else from being able to tamper with them because they're encrypted. But secondly, if you don't encrypt your config backups, all of your passwords don't actually get stored in the backup. So if you don't encrypt it, you have to manually punch in all of your passwords in a restore scenario. So it's always worth making sure that your config backup is configured. It's on immutable storage. If your VBR is on fire in a DR scenario, you want to be able to get hold of that config backup, get restored, get back up and running. As for creating backup jobs, we can just simply create a backup job, and then we get a whole plethora of different things we can do with it. There is a lot of different things we can backup. In this case, we're going to be opting for a virtual machine. Now, this will just create a VM backup job, and this will automatically choose the type of VMware VM in our case, because we only have one hypervisor platform added. If you have multiple hypervisor platforms, we'll get the option to specify what I want to use. So we'll go ahead and throw in a name. Watch my horrible capitalization. Okay. We can select our VMs. Again, loads of different ways you can do this. You can select folders, you can select resource groups, you can do tagging in the VMware world. You can also just straight up select virtual machines. So if we go and hunt down, let's go and find my Unify controller for all of my Wi-Fi and switching needs. So if we go and select that and say, I actually want to go and back this up. This is nice and small. Backup proxy, we can leave on automatic selection. We haven't actually added any proxies at this point in time. So we can kind of just leave this as it is for the moment. Make sure our repository is correct and set to be a useful repository. Set some retention. This will kind of be in line with whatever your company RPOs are. That's your recovery point objective. That's how much data you can afford to lose in a DR scenario measured in time. So if I have an RPO of 24 hours in a DR scenario, I expect to lose up to 24 hours of data. Basically being done backing up every 24 hours. You can use GFS policies for archival backups. So that includes things like weekly, monthly, and yearly backups for X number of weeks, months, and years. On immutable repositories, it's worth noting that we have a retention policy of 14 days. So we'll get immutability for that 14 days. GFS backups get their own unique immutability set irrelevant of what the repository is. If you specify a number of days on an immutable repo, the GFS is always overridden. So it's worth noting. I literally had a customer the other day try and set, they wanted seven years of retention. So they set their backup as immutability period of 2,500 days. As a shock to nobody, that repository overfilled and completely crashed. So this is kind of the reason why you would use GFS and sort of why it has different immutability points. S3, I'm sorry, if you enable GFS anyway, it will make you do that. Advanced job settings actually is always worth coming in and just making sure that storage level corruption guard is on. You can optionally do active full backups periodically. I always like this as it just gets a fresh set of the data. But as long as you've got that storage level corruption guard to make sure your backups aren't corrupted, you should generally be fine. We can click next from here. We can do application aware backup if we need it. So that's for things like Active Directory, Exchange, SQL, those kind of things that need the operating system to kind of say to the application, hey, we're going to back you up in a moment. Could you put yourself in a state where you're ready? Otherwise, the backups don't kind of take this into account. And if you get database transaction logs that are midway through, you don't always get a clean restore. In the case of a lot of things, you generally, I don't think, need application aware processing, but it is worth noting the places when you would need it. But we can just click next here. We can set our schedule. So again, if I set this daily at 10 o'clock, this is my kind of RPO of 24 hours. If I did this periodically every six hours, that would align with a six hour RPO. It's kind of how you would set this. And we can hit apply. And then we can run the job when I click finish. And what that will do is that will go ahead and start backing up this particular virtual machine over to that immutable storage for us straight from the VMware environment. Anybody got any questions? I will definitely take silence as golden. Blanka, how are you getting on? Yes. Do you want me to share my screen to explain how to? Yeah. Okay. Yeah. I will pause the stage. Thank you, Liam. Can you see now my screen? Okay. So, how we can work with BIM at AWS? So, my recommendation always is go to the marketplace. Here, you can discover different products related to BIM. So, you can type here, BIM, and you will see the different products that you can test and buy in AWS. For today, as we were discussing, we're working with backup and replication. So, what you can do there is, well, I already have this product, but here you can purchase this. So, since I already have this, so you will see here that I have active my subscription of BIM replication. So, the next step is to launch an EC2 instance. So, you have two methods to do. One is if you don't want to complicate your life and you want a quick deployment with minimal configuration of the requirements, you can go here, select the version that you want to work with. The last one is this one, but you also can see previous versions. Here, you already have the instance that you recommend, which is the VPC that you can use. Also, you can create a new one, the same related to the subnet, related also to the configuration of the... Something important that I need to mention is remember that when you select the subnet, it needs to be public and related to the security group. I already have a security group, but it is important that you configure all the traffic that you want to have related to the EC2. And, of course, to define the key pair that it is required for the access. This is one option. As I mentioned, this is the quick deployment that you can do, but also, you have the option to do by yourself one per one. Here, if you select this option, you can select the different instance. Something important that you also can see here is that you can configure step-by-step the network settings. For example, you need to select here what will be the subnet that you need for this configuration. Also, you need to validate what will be the availability zone. Something that I need to mention is you can work with free tier. I will put in the chat the link of the free tier. You have 200 credits that you can use. Also, you can add a security group. In this case, I have already built a security group, so I can select the security group if I want. Also, you can add the size of the storage that you need. Well, for today, since we have a limitation of the timing, I already have two instances. I will share with you the two instances that I already deployed. If you go to the EC2, you will see here that I create two instances, one that was deployed with the quick deployment and other one with the free tier that you can see here the size. If you want to know, okay, what is the size of the VM or which type is S3 micro or the MCI, you can go here and see the size of each of them. You can select, for example, in this for today, if you work with T3 micro, you will see that it is an instance or VM with two virtual CPUs and one gigabyte of memory. If you go to the other one, the M6I, you also will see that in this case, it is a bigger one that is a virtual CPUs with 32 memory. If you want to see one question that always people say, since when we are working AWS is pay-as-you-go, you also can add here details. For example, if you want to know the price on demand, you can add here. For example, in this case, I am working with Windows, so you can add it what is the cost per hour. Now, I have two instances I mentioned. Okay, let me log in in this one. Let me know also if you have any questions. So, this is an instance that already has everything installed. So, in the case of when you select that quick deployment, as Leah showed, all that installation is already installed. Leah showed all that installation is already, so you just need to connect. In this case, I will select assign as a current user. It will start logging here. It will take a couple of time. For example, things that you can do as Kira also shared, if you want to add a repository, in the case of the S3 bucket for AWS, you select object, for AWS, you select object, then you select a hyperscaler, you select Amazon S3, you select Amazon S3 again, and here you can add a name. Let's put test one. Also, you can add a description. I won't add anything here. I already have credentials, but you also can configure in the credentials. You can select if it is a global region or it is a government or it is for China, then you can select next. Here, you need to select the data center. I am working in North Virginia, so you can select North Virginia, and then you can select the buckets. I have different buckets here. I will work with what I call the backup. I select this, and also I need to select the folder. If I don't have a folder, I can create. Let's put also test one, and then I can select okay. Same as was mentioned by Kira, you can make the backup immutable. That is one of the recommendations. Well, in this case, okay, well, in this bucket that I select, it doesn't have, so I won't select this one at the moment. Also, I can select where I can mount the server. I can select next, and then apply. I'm going to start doing that configuration. As you see, it's the same process that we saw before with Leah and Kira. Then, we can select finish, and you can see here the diastereo bucket. Leah, I don't know if you have any comments, questions, or anything additional you want to mention here, or Kira. Oh, looks really good. And I also have, you also can do the same if you want to do the installation from scratch. The, in this case, I showed this one, but you can also do the same if you want to install everything from scratch with that free tier. I will, I've only got a few minutes left within kind of that hour's block, but just kind of heading back into the lab that we had before, so our lovely server that was installing at the start has finished. Finishing the install is pretty dead simple. You just simply click finish. It will then tell you it needs a reboot. So, you reboot the box. It comes back up, and then it's in the state that we picked up on the second box for. Other things that are worth noting, now that we have an additional repository, we can bin off the inbuilt Windows repository. You always get that. It doesn't matter what server you do. If you do the Linux hardened appliance, you'll get an immutable kind of default backup repository. Generally speaking, you don't want to use this, so we can just remove the repository. Nothing's using it, right? Our backups are pointing into our new immutable bucket. Our config's been changed over, so we can get rid of that just to make sure that nobody does back anything up to anything that's not immutable, not best practices. We could take the same kind of approach with disabling the onboard proxy, which I would recommend that you do if you go and add additional proxy resources to the server. We didn't really have time to go through that today, so that's something that I haven't touched too much on, but something that you certainly can do, and then once our backup has run, we can see the job. It says it ran successfully. It's transferred the data over, and then we'll get this lovely little backups folder. This populates depending on what it is, so if it's disk-based, you'll see a disk add-on. If it's VeeamZip, you'll see it as exported. If it's on tape, you'll see it as tape, and then we get our job name that's bolted into it, and then we can start doing things like restore functions, pulling files off the virtual machines, or in the case of Active Directory, we can even go very granular and restore individual objects into the actual AD forest if we particularly wanted to, so there's lots of scope that you can do. I'm conscious that we've got about five minutes left, so I will open the floor back up to everybody else and ask if anybody else has any questions or anything else they wanted to ask after the backup stuff today. It looks like everything was clear. I think probably everyone already knows Veeam Backup Replication, Object First, AWS. Is there maybe someone on the call who hasn't deployed yet new Backup Replication in a lab or in production? All right, so it seems like we have a very experienced crowd on the call. Well, in this case, I would say thank you everyone for attending. Hopefully, you might have learned something new and not just seeing what you have already known. Maybe learned a few things or two about AWS or Object First or maybe even Veeam, for example, how the imputability is now applied on the version 13, that it's different. No, actually, it's applied the same way, but the UI that's changed in the repository settings when we're specifying the imputability period. Also, it would be nice if people tell us which other topics they would like that we discuss next time. That would be great. Also, you can share topics or ideas that we can discuss in the future. Just to answer Tommy's question, yes, it will be. So, it will be recorded, and then I think we just need to create. It will be recorded, and the post will be probably created automatically. I'm not sure. Or we'll create a post. Yeah. Yes, just to answer Tommy's question, it is recorded. It will be available on Veeam YouTube in the community playlist, and one of the girls is going to just take the link. We're going to share it with them, and then they're going to post a brief overview, if anything, of the wait group. So, it's going to be available there for you guys that attended, and you want to re-watch it, and for everyone else that were not able to attend, and, you know, they just want to learn something. So, so far, our project has been a lot of fun. We've had a lot of our plan, so we did so far two sessions, and they were both technical. They were both about home labs. I think maybe for the next one, we will step back from the lab, and we will probably invite other ladies that can share their experience in IT, so we have a couple of names in mind. So, yes, we're mostly thinking to invite other people, other ladies, maybe the I think that was probably that was what we have done on our very, very first call, so pretty much when we explained how did we end up being here, so we're thinking of inviting more people just to so that they can also share the experience. Okay, Sure Backup, Keith is asking. I actually love Sure Backup. It was one of my most favourite features at Veeam, still is, yes, I still like Sure Backup. I like the cases when I was working back at Veeam support regarding Sure Backup. So, yes, maybe to do something, yes, yes, so the point is taken, so Sure Backup for one of the ... I need to set Sure Backup back up in my Veeam lab, trying to say that. It's like a tongue-twister. So, I don't know, maybe that's a session at some point, just working through that, then it depends what people want to do. Sounds good. All right, I think we are on time. Thank you so much for joining us today, and see you next time. Thank you very much for having me. Thank you, Kira. Thank you, Leah. All right.
