Every organization has unique data recovery requirements. Learn how to set goals based on your organization's requirements.
- [Instructor] There's more to performing backups than simply installing backup software and telling it to back everything up. There is a significant amount of planning that's required in order to adequately protect your data. So I wanted to talk about a few of the more important considerations. Now, this list is by no means all-inclusive, but these are some of the more important things that you need to consider. One of the first things that you should consider is your recovery point objective. The recovery point objective refers to how often backups are occurring. Back in the old days when we used to perform a nightly tape backup, the recovery point objective was once every 24 hours. More modern backup solutions perform backups far more frequently. You can have backups every 30 seconds, for example. The reason why the recovery point objective is so important is because it determines how much data could potentially be lost if you end up having to restore a backup, if you've got a recovery point objective of 24 hours, for example, then if you have a data loss event and you lose everything that's accumulated since your last backup, you could potentially lose up to 24 hours worth of data. On the other hand, if you've got a 30-second recovery point objective, then you could potentially lose up to 30 seconds worth of data. So the recovery point objective is extremely important. Now, another important consideration is the recovery time objective. The recovery time objective determines how long it's going to take to restore a backup. Back in the old days when we used to write everything to tape, it could take hours or, in some cases, even days to perform a full-blown restoration. By today's standards, that's largely unacceptable. In many cases, it's possible today to perform an instant restoration, thanks to the instant recovery feature in some of the more modern backup applications. So be sure to consider your recovery time objectives because it's going to determine how long your data sets are going to be unavailable during a restoration. Another consideration is what is the volume of data that needs to be protected? In other words, you have to scale your backup solution so that it's large enough to accommodate the data that has to be backed up. And then finally, where should the backup reside? Are you going to back up your data to an on premises solution? Are you going to back it up to the cloud or perhaps some combination of the two? Are you going to use tape backup or disk backup? These are all the types of things that you need to be thinking about. Now, just as there are planning considerations for backups, there are also planning considerations for disaster recovery, so I want to talk about a few of those. One of the first things that you need to think about is which workloads need disaster recovery capabilities because sometimes it can be expensive to implement disaster recovery capabilities, so you want to be sure to use your IT budget where it counts and protect the most critical workloads first. Another thing to think about is where do those workloads currently reside? Because you're going to have to use a different method for protecting on premises workloads than you might use to protect a cloud native workload. Another thing to think about is how long can the workloads be offline during a failover situation? There are various types of disaster recovery solutions. Some of these solutions will allow an instantaneous failover. Others take a few minutes to failover. But generally, the solutions that will perform an instant failover tend to be more expensive and more complex than the ones that take several minutes to perform a failover. So it's important to think about how long the workload can be offline during a failure situation because that's going to determine which type of solution you need to use. And then finally, you need to be thinking about what types of risk you need to protect against because those risks are going to weigh into your disaster recovery architecture. If one of your big risks that you've identified is your data center being wiped out by a hurricane, then you want to design a disaster recovery solution that will allow everything in your local data center to failover to an alternate data center or maybe to the cloud or something like that because the data center as a whole is a potential source of failure because that data center could get wiped out by a hurricane. So those are just a few of the things that you need to be thinking about with regard to backup and disaster recovery planning.
- DR in the public cloud
- Defining recovery requirements
- Configuring AWS Storage Gateway
- Configuring a backup app
- Creating and managing EC2 VM snapshots
- Four types of failover
- Performing a cold failover
- Pilot light recovery
- Warm standby recovery