Cloud service disruptions may happen. For example, during the past December, AWS had an ELB problem in us-east-1.
This service disruptions was not a huge concern for us, since the system was in staging phase and there was no traffic. However, we took this opportunity to learn and prepare ourselves. I’m sparing you the learning shenanigans, so you can follow and implement the solution without waiting for the next outage to happen.
When you keep important business data in your EC2 servers, you need a backup and disaster recovery (DR) solution like you would for any server. For operational backup, the most efficient and effective approach in EC2 is to use EBS snapshots. These are the parallel of hardware snapshots in a traditional data center.In this post we will discuss the challenges you encounter when you use EBS snapshots.
AWS is ideally suited for making the user’s applications tolerant to disaster. One of the options for making the user’s application suitable to DR is to keep a back up of the data / application setup in multiple regions. If the first region is not reachable due to some reason, the user can start the application from the other region. In Dec, 2021 AWS introduced functionality to copy snapshot across regions.
This guide demonstrates how to copy a snapshot of a Linux based instance to another region as well as attach a volume to a new instance to complete the instance data migration across regions.
The following describes my personal case on how I maintained snapshots of my AWS EBS. The following requirements guided me with the scripts and tools I decided to use:
The cloud definitely marks a new era. Not only can we manage our resources in a flexible way and with no capital investment, but we can also enjoy the state-of-the-art infrastructure of large cloud providers, like AWS cloud. Specifically, when we use EC2 to compute endless resources, we know that in terms of the durability of our virtual servers, power supply, and storage, we can trust AWS to have the best of the best.
In case of a disaster we would like to make sure that our applications are still up and running, while taking advantage of our failover hosting/cloud provider. The Disaster Recovery (DR) architecture is driven by the criticality of applications and data. The decision regarding what to back up and deploy eventually translates into ongoing costs that can be extremely significant. Every IT organization has its own high level policy guidelines. These policies are eventually translated into the policy deployed for each of the different applications the enterprise runs. The CIO and its team need to make sure they define both the high level policies and the actual budget that can be spent for DR matters.
The policies for Disaster Recovery (DR) in an enterprise are driven by the criticality of applications and data. As the public cloud has gained in credibility, more and more IT teams are taking advantage of the failover public cloud provider as a way of addressing DR and ensuring business continuity.
On the following presentation Lahav Savir, architect and CEO of Emind Systems, gives an introduction to Disaster Recovery and presents his insights based on Emind’s best practices.
During the Amazon AWS Summit 2021 in Tel Aviv (Israel) Udi Keidar - VP Cloud Services at ClickSoftware - went on stage to present a very interesting AWS cloud case of a veteran ISV (independent Service Vendor) that successfully delivers its new enterprise SaaS offering over the AWS cloud.
Newvem tracks the usage pattern of hundreds of Amazon AWS customers and has identified that more than 35% of its beta users are operating an Amazon AWS cloud with high vulnerability to outages.
Following today’s AWS outage, we find it important to refresh the following important information and best practices on how to prevent unnecessary downtime and damage from an AWS outage, protect your AWS footprint at the time of an outage, and ensure you can recover immediately after the outage.
S3Sync is a tool written in Ruby to synchronize system folders (EBS) and S3 buckets. In this guide we will shown you how to sync your EBS data with S3 bucket and vice versa.
We will run an EBS-backed Linux instance and sync data between our instance and S3 bucket.
To execute the S3Sync from your instance, you need Ruby (version 1.8.7 or above ) installed in your local machine. If you are running a Windows instance, download and install Ruby from http://rubyinstaller.org/downloads/ for a Windows local machine.
