View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

Release Management/Backup and availability strategy

Release Management/Internal

Index


Contents

Introduction

The Release Management team primarily uses Amazon EC2/S3 for their servers and storage. This is a plan to make sure nothing is lost and to improve the recovery plan in case of disasters of various severities.

Objectives

Backups:

Availability. We must be able to recover any instance in the following cases:

Persistent storage

We can divide the files of our Linux systems into 2 groups:

The static part is covered is usually in the root partition. Earlier this root partition was temporal (instance store). Now with ebs boot we have persistence for root partition as well. Taking regular snapshot is the best way to backup.

The integration between the root partition and the EBS volumes should be seamless. That is, a reboot should not affect it at all. And even starting anew instance of the AMI should mount all the EBS volumes, if they've been attached to the AMI previously.


Goals: move all the dynamic critical data to EBS. And make the reboot a new instance creation automatic.

Continuous monitoring

The first thing you need to recover a machine is to know that it needs to be recovered. So we need to continuously monitor all the critical services or our machines.

We first need to define what we need to monitor in each machine. Then we can select the most appropriate tool for this task (Nagios, Monit).

Ideally this machine should be placed in another data center other than Amazon EC2, to provide a more realistic monitoring.


Goals: monitor all the services, define what needs be monitored per machine, set it up in a different data center.

Instance recovery

We must be able to recover a machine when a disaster happens. There are different levels or problems, namely:

Requirements for this to happen:


Off-site backups

As we do not want to depend on EC2/S3 entirely, we will do backups into another data center. The selected options are:

Both offer nearly unlimited storage at reasonable prices (DiomedeStorage is cheaper), open source APIs, . The advantage of Rackspace is that it also is a cloud hosting solution, so we cloud have our monitoring machine in this server. And also, it's known by it's excellent customer support.

Physical backups

We do not want to depend on any data center entirely, so we prefer to have physical backups available locally on the Openbravo headquarters from time to time. Amazon AWS offers this option in the Import/Export service.

Deliverables

These are the proposed steps to be taken:

What next in amazon aws

Retrieved from "http://wiki.openbravo.com/wiki/Release_Management/Backup_and_availability_strategy"

This page has been accessed 3,288 times. This page was last modified on 22 February 2010, at 17:49. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.