If you tell someone that your computer crashed, the first question you usually hear in response is “Did you back up your files?”
That’s the right question to ask if you’re talking only about personal data or a single computer. When your PC crashes, having a data backup available is usually all you need to restore your normal routine.
But if it comes to a company, backing up data is not enough. When a company’s infrastructure is damaged or data is lost, a full disaster recovery operation needs to take place to restore operations without causing critical disruptions to the company. Disaster recovery requires much more than simply backing up files.
To understand why, you need to appreciate the difference between backup and disaster recovery, which this article explains.
It might seem that we are talking obvious things here, however, in the article you will find a couple of numbers about backup and disaster recovery.
RTO and RPO (recovery time objective and recovery point objective) are two key metrics that organizations must consider in order to develop an appropriate disaster recovery plan that can maintain business continuity after an unexpected event.
Although only one letter separates RTO from RPO, it’s important not to confuse or conflate these two metrics. Both help to determine maximum tolerable hours for data recovery, how often data backups should occur and what your recovery process should be. Both need to be considered when creating a disaster recovery plan.
Backup and archive are terms that you might hear used interchangeably. In reality, however, they are not at all the same thing. There are important differences between data backups and data archives.
Understanding these differences is crucial in order to ensure that your data processes meet your needs. Doing data backups when you instead require a data archive, or vice versa, can have very negative results when it comes time to retrieve data.
This article defines data backups and data archives and explains the differences between them.Continue reading →
Optimizing costs can be difficult because AWS offers several different types of pricing models. In order to make sure that you are paying the least amount possible while still obtaining the level of resource availability that your applications require, you need to understand Amazon EC2’s pricing options and identify which type of pricing is best for each workload that you host.
This article explains how pricing works on EC2 and offers suggestions for optimizing EC2 costs.Continue reading →
AWS offers nearly fifty different types of EC2 instances. It also provides a number of different categories of images, each tailored for different use cases.
Choice is a good thing, and having so many EC2 instance options and categories is a benefit to users. But with so many possibilities, deciding which EC2 instance is the best fit for your needs can be a challenge.
If you’re struggling to decide which EC2 instance to use, this article is for you. It outlines the major EC2 instance types and categories and makes recommendations about which instances are the best fit for certain types of situations.
We won’t discuss every individual instance type. That would be unfeasible, because Amazon currently offers forty-nine distinct EC2 instances. But we’ll cover the most important ones, and discuss the differences between the major categories of EC2 instances.
Amazon EC2 instances can be backed up in more than one way. The approach you take to EC2 backups should reflect your needs: Whether you require an automated backup solution, how quickly you need to be able to restore an instance during an emergency and how much data you can store and transfer.
This article identifies the different methods for backing up EC2 instances and discusses the pros and cons of each approach.Continue reading →