In this guest blog post, W. Curtis Preston (aka “ Mr Backup”) poses the question ‘Do you need to backup EC2 VMs?’. W. Curtis Preston is an expert in backup & recovery systems; a space he has been working in since 1993. He has written three books on the subject, Backup & Recovery, Using SANs and NAS, and Unix Backup & Recovery. As well as being the Chief Technical Architect at Druva, Mr. Preston is also an independent consultant and writer and has spoken at over 300 seminars and conferences around the world.
Category: Backup Policy
As a company that specializes in simplifying and demystifying Amazon Web Services (AWS), we here at CloudRanger are constantly answering questions about the AWS platform and its various features. And despite the diverse nature of our client base, one question seems to pop up on a regular basis: Where are my Amazon EBS snapshots stored?
As such, we decided to give this frequently-asked question its very own blog post. In the following article, we’ll explain in detail how and where AWS EBS snapshots are stored, and explain why the answer to this question isn’t quite as straightforward as it may seem at first glance. We’ll also explain how using CloudRanger can greatly simplify the EBS snapshot backup process.
Thanks to cloud-based platforms like Amazon Web Services (AWS), backing up your company’s critical data has never been easier. But as we’ve stated in previous blogs, during an actual crisis, backups may prove useless in the absence of a comprehensive disaster recovery (DR) plan. And while there are many factors that must go into crafting the right DR plan to meet your company’s specific needs, the two most important are the recovery time objective (RTO) and the recovery point objective (RPO). In the following article, we’ll break down what these terms mean and how they differ. We’ll also explain why determining the RTO and RPO is so important, and how CloudRanger can help enact an AWS DR plan once it’s been crafted.
Since they were first introduced in 2008, Elastic Block Store (EBS) volumes, specifically EBS snapshots, have become one of the most popular storage methods offered by Amazon Web Services (AWS). Not only are they generally cheaper than traditional Amazon Machine Images (AMIs), but the snapshot’s ability to capture incremental block-level changes also eliminates the need to continuously backup entire volumes. However, another popular EBS attribute is the ability to quickly and easily copy a snapshot to another region, a feature that may prove useful to your business for a variety of reasons. In the following article, we’ll discuss some of those reasons, as well as how third-party vendors like CloudRanger can help simplify the process.
In theory, Amazon Web Services’ (AWS) has the potential to save your business a significant amount of time and money. But in practice, the complicated AWS interface prevents many would-be users from taking full advantage of the cloud-computing platform. However, thanks to the newest version of the award-winning CloudRanger system and its easy-to-use dashboard, streamlining your business’ AWS backups, disaster recovery and server control has never been easier.
In the following article, we’ll highlight some of the key features found in the newly updated CloudRanger, and explain how they can save your business both time and money on your AWS bill. We’ll also fill you in on how your business can take advantage of a free 14-day trial and experience first-hand how CloudRanger can automate and simplify your routine AWS tasks.