Category: Snapshot Management
One of the main advantages of the Amazon Web Services cloud infrastructure is that it is readily available across the globe. The widespread network of AWS data centers are divided into regions and availability zones, and this helps in achieving high availability and disaster recovery capabilities.
So, we are excited to announce an enhancement to our CloudRanger AWS automated backup and scheduling solution, by allowing CloudRanger users to easily copy snapshots across AWS regions to support disaster recovery requirements.
While searching online for a solution to help with their AWS EBS snapshot management, VOKKE found CloudRanger. It became quickly apparent that CloudRanger offered the solution VOKKE were looking for by streamlining and simplifying their backup activities. VOKKE now use CloudRanger to automatically snapshot and rotate their EBS volumes by tag, as well as terminate servers at night when workloads are low.
Let’s be honest, we are all busy people and where possible, we want to automate tasks. We want to be able to set something up and then forget about it, safe in the knowledge that it’s being taken care of in the background.
Although AWS allow you to take snapshots of your EBS volumes, it still requires some manual effort and is subject to human error. In this blog post, we will look in more detail at the benefits of AWS snapshot and backup automation.
At this year’s AWS Summit in New York, Amazon Web Services announced, the very welcome news, that they are lowering the cost of snapshots of volumes of data stored in the Elastic Block Store (EBS) service by 47 percent!
Amazon Elastic Block Store (EBS) is an AWS block storage system that is designed for storing persistent data. If you want to backup the data that is on your EBS volume it is possible with snapshots. It’s even possible to instruct EBS to make snapshots when data on EBS gets updated. EBS volumes are typically attached to applications running inside AWS EC2 virtual machine instances and persist even after EC2 instances are terminated, unlike local EC2 instance storage.
Why do we need a simpler way to launch a new EC2 instance, does AWS not already tell us how simple this process is and how quick and easy it is to set up? This is all true, however, as more organisations migrate to the cloud AWS continually, strive to meet their customer’s demands and develop with them new ways to meet their organisation requirements or giving the customer the right tools for the right job. So let’s compare, What’s involved in creating an AMI and how does it work, compared to creating an EBS volume Snapshot?
The traditional backup procedure associated with data sets would potentially throw up several issues along the way, like version skew which could result in data corruption. Also, the resources required to carry out the task, and the time it would take to complete could present significant problems. This is where snapshot automation technology can be of great benefit. A snapshot, in basic terms, is a copy of a data set at a particular moment in time, in other words, you don’t need to back up your entire data set to get full data protection which may be essential for mission critical businesses. In this blog post, we will look in more detail at the benefits of AWS snapshot and backup automation.
By default, Amazon Web Services(AWS) do not keep backups. It is the responsibility of the end-user to provision backups. However, AWS offers a wide range of backup and recovery solution for enterprise architecture, backup architecture, and IT administrators who are responsible for protecting data in their enterprise. While AWS offer solutions for backup and recovery, identifying and designing your business requirements, are fundamental in selecting the correct service that best meets your demands.
Earlier this week, Amazon Web Services announced that you can now copy encrypted Amazon EBS snapshots between accounts, a capability previously supported only for unencrypted snapshots. Now you can easily copy encrypted snapshots between your development, test and production environments or between different departments and project accounts. This will now also make it easier for you to follow AWS security best practices which include copying encrypted snapshots to separately managed accounts, in the same or other regions, to provide an extra level of account isolation.
Although AWS makes it easy to take snapshots of your EBS volumes, it still requires some manual effort and is therefore, subject to human error. Let’s be honest, we are all busy people and where possible, we all love to automate tasks. We want to be able to set something up and then forget about it, safe in the knowledge that our tasks are being carried out in the background.
The feedback we get regularly get from our customers is that they are looking for an easy way to automate snapshots of an EC2 instance and related EBS volumes on a regular basis, without the hassle of coding of scripts and their ongoing upkeep.