That way, in the case of a disaster, all of that data will have been seamlessly transferred to the cloud.īackup and Restore is a great option for those who are weaning themselves off of on-premise storage and hardware. AWS Storage Gateway can be configured so that all the files will be replicated onto an S3 bucket. Storage Gateway is an excellent cloud hybrid tool that allows on-premise data storage solutions access to the cloud.įor example, let's say the employees of your company commonly place information on a share drive. In addition to Amazon Snowball, Backup and Restore cannot be mentioned without bringing up AWS Storage Gateway. This is a great way to prime your system for a Backup and Recovery DR solution. After you have uploaded your data, which may be many petabytes, it is shipped off to an AWS facility and stored in S3 buckets. It is a physical hard drive that is hooked directly into a company's database. What if your company is currently on tape drives, and doesn't have any data in S3? This is where Amazon Snowball comes into play.Īmazon Snowball is a data transport service offered by AWS. If your system goes down using this method of DR, the system administrator would need to upload the data back onto the system from the S3 buckets. In other words, there is virtually no way this data will be irrecoverable. In terms of reliability, it is a safe bet to keep your most valuable data in S3 buckets, because they are designed for "eleven 9's" durability across multiple regions. However, the biggest difference is that instead of streaming data to a tape, the data would be streamed to an S3 - IA bucket or an S3 Glacier bucket. Out of all the possible DR solutions, Backup and Restore shares the most similarities with tape-backed recovery. Backup and Restoreīackup and Restore is the first - and least expensive - disaster recovery method on the list. Let's take a look at the first method, Backup and Restore. Once the analysis is complete, you will be able to accurately determine which solution is best for your company. It should answer questions such as how much money you would lose from downtime, whether or not the company's reputation would suffer, and how much capital should be invested in the system's DR operation. A Business Impact Analysis is simply a study on how important a particular system is to your day-to-day business, and how its downtime would affect the company. So, before deciding on an appropriate DR approach, it is important to conduct a Business Impact Analysis. Similar to our last example, if the business said they would accept one hour of downtime between the disaster striking and the system's disaster recovery implementation, then that would be an RTO of one hour.Īs you might expect, the shorter the RTO and the shorter the RPO, the more complex and expensive the backup system will be. RTO, on the other hand, refers to how long it should take for the backup system to become fully functional. Another way to put it would be, the business fully expects to lose all data that was produced in the last hour, but not a minute before. (For those of you vying for the AWS Solutions Architect certification, pay attention, because these will be on the exam.) An RPO refers to the optimal point of time from which you would like the data to be recoverable.įor instance, does the system require all the system's data from 10 hours ago, 10 minutes ago, or 10 seconds ago? If the business says, "In the case of a disaster, we would like to have all data recovered as recently as one hour ago." This means that your RPO is one hour. RTO refers to Recovery Time Objective and RPO refers to Recovery Point Objective.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |