How to set Automated backups of your ec2 and rds

hello everyone today I'm going to show you how to create automated backups for your ec2 instances and also for the RDS so let's get started backup is a very important thing because in interpreters there are a lot of options available and a lot of things that you wanted to experiment and you I always encourage people to have a backup policy otherwise if there's anything goes wrong and then you cannot revert back to your successful or stable state so we like to do experiments and also need to stay a stable version where we can say that this is very stable so your ec2 instances they have volumes and we need to ensure that these volumes have proper Packer policies so for the easy to automated backups let's go to ec2 area I see I have very one running instance so I'm going to add a tag here okay this is a dagger vetted now I want to create a backup policy so that this instance is automated automatically a backup is created and we keep a backup of last seven days and after that we will automatically delete those backups so let's go here in the left panel you will see elastic block store EBS and here you will see lifecycle manager a lifecycle manager is a place where you set your backup policies how you are going to create backups and how many days you want to keep those backups in your AWS infrastructure and how many what is the interval of daily or 24 hours or 12 hours all these informations you can sit over there so let's create a backup policy may give a name backup lost today's select resource type it can be volume or instance I can choose instance I have created a tag on the instance level so that's easier for me then I give the tag name I created the tag with project backup so I just select here and the value is test so what this means that any instance which has these tags will be now in our backup policy so let's move further and we wanted to give a name non-policy we can run it on a 24-hour automation to our three four six 24 anything we want so let's stick to 12 hours starting from zero zero then a number of snapshots that will be retained that means number of snapshots some floaties here's your one of your backup that's will be stored and networkers so how many snapshots you want to keep so we have twice a day and seven days I say 14 then copy tag from volume that's true then I also added take here because when you taking me so using these tags I can easily find among those snapshots I enrolled at default one policy summary I'm okay so my policy has been created and it will take effect from as we have where setup UTC zero zero so the first backup will be created on tomorrow early early in the morning you need to see time zero zero we will have lost 14 snapshots and this is my policy ID if I click here and if I go to snapshots here I will see my automated backups over created here and as this moment there is none because it's still not started yet but if I see tomorrow then I will see the backups are pushing up here and each day twice and 14 will be available in after seven days after seven days the oldest one oldest backup will be automatically deleted and we don't need to worry about this it's an automatic process of enterprise so we can enjoy the benefits of it of less automation so I hope this gives you a brief idea of how you can do your ec2 backups so let's go to RTS one as well so I'm going to create a new RTS at this point I don't have any separate entities which is my squirrel and Staley in 50 years next my school 5.7 this I choose within three years so that's due to micro level storage what was scaling it's fine and give your name as a reason man mr. postman unless we have to use a strong password again generally strong password generator Oh and go to next opening the excessiveness yeah there's the important part so here I choose as you can see we can't we have enough also an option in ideas to have an automated backup of your database and it must select the number of days retention period it can be with zero days that means more backups one day that means you only have one back up and say on this means last seven days a backup will be stored each day one and that means number of seven backups will be stored over there so for this example I chose seven this policy monitoring non log sport none I'd keep everything as it is you do those okay my dad a visit created so I just created the backup database with automated backup policy of seven days when this policy will run after checking tomorrow or day after tomorrow I can see the snapshots created here so that's that's the basic bathing of how automatic backups can be created in a database infrastructure I highly recommend you make a Beckham policy for your ec2 RTS and s3 as well this is a this will help you get trust on your experiments so that something goes wrong you can revert back so I hope this X this tutorial helps you to make automated backups if you like my videos and wants to support me you can subscribe to my channel I will thanks for your help thank you and have a nice day

Channel: AWS With Atiq

Views: 3,721

Keywords: aws, ec2, rds, backups, tutorial, beginner, devops, sysops, failover, disastar-recovery, lamp, linux

Id: quTV4kO_a7E

Length: 10min 38sec (638 seconds)

Published: Sun Jul 21 2019