Shulou(Shulou.com)05/31 Report--

This article introduces how to use Pilot Light to recover quickly in AWS. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

Today we begin to introduce the second of the four DR strategies-- using Pilot Light for fast recovery in AWS.

Quick recovery using Pilot Light--

The term "Pilot Light" is often used to describe DR scenarios, meaning that your business has a minimized version of the environment that is always running in the cloud. Pilot Light's idea is an analogy from a gas heater, in which a small flame that is always on can quickly light an entire stove to heat a house.

Pilot Light allows you to configure and run the most critical core components of your system in AWS, so that in the event of disaster recovery, you can quickly scale the configuration into a complete production environment around the key core components maintained by Pilot Light in AWS.

The infrastructure composition of Pilot Light typically consists of your database servers that replicate data to Amazon EC2 or Amazon RDS (automatically synchronizing your core data to the Pilot Light core components maintained by AWS). Depending on the business system, there may be other critical data outside the database that needs to be replicated to the AWS. This is the key core of the system (Pilot Light), and all other infrastructure components in the AWS (the rest of the furnace) can be quickly configured to quickly scale and quickly restore the entire system.

In a simple summary, establish a minimized environment for your business in AWS, and then synchronize some of your core data (such as databases) to AWS's RDS or other services in real time. In the event of a disaster, quickly expand the Pilot Light minimized environment maintained by AWS to your generation environment through the services provided by AWS, so as to quickly restore your business.

So in order to quickly extend the core components of the Pilot Light minimization environment maintained by AWS to restore critical business services, in addition to synchronizing the core data, what else need to be done to rapidly scale to the scale of the production environment?

For computing resources, some preconfigured servers are usually made into Amazon Machine Images (AMI), which can be started at any time. At the beginning of disaster recovery, instances from these AMI start quickly and use their predefined roles (for example, Web or App Server) in the deployment around the Pilot Light.

For slave network resources, you have two main options to prepare:

Using Elastic IP addresses, it can pre-allocate and associate them with your instance. Note that for software licenses based on MAC addresses, you can use the resilient Network Interface (ENI), which has an MAC address, or can be pre-assigned to configure the license. You can associate these with instances, just as you would with elastic IP addresses.

Use Elastic Load Balancing (ELB) to distribute traffic to multiple instances.

Finally, to bring the previously extended resources online to the production environment, you may update the DNS record to point to your Amazon EC2 instance or use CNAME to point to your load balancer.

For systems that are not updated frequently, you can ensure that all installation packages and configuration information are provided in AWS, for example, in the form of Amazon EBS snapshots. This accelerates application server setup because you can quickly create multiple volumes in multiple availability zones to attach to Amazon EC2 instances. You can then install and configure accordingly by using backup and recovery methods.

The Pilot Light policy provides faster recovery time than the backup and restore strategy introduced last time, because the core of the system is already running and constantly updated. AWS automates the configuration of infrastructure resources, which saves time and helps prevent human errors. However, there are still some installation and configuration tasks that need to be performed to fully restore the application.

Preparation stage

The following figure shows the preparation phase, where you need to copy the periodically changed data to Pilot Light, and this small core will start the entire environment during the recovery phase. Data that you update infrequently, such as operating systems and applications, can be updated periodically and stored as AMI.

Key steps in the preparation phase:

Set up an Amazon EC2 instance or RDS to replicate or mirror core data.

Make sure you have all the supporting custom packages available in AWS.

Create and maintain AMI for critical servers that require quick recovery.

Run these servers regularly, test them, and apply any software updates and configuration changes.

Consider automatically configuring AWS resources.

Recovery phase

To restore the rest of the underlying environment around Pilot Light, you can boot the system from AMI in minutes on the appropriate instance type. For dynamic data servers, you can resize them or increase their capacity accordingly according to your business needs.

Horizontal scaling is usually the most cost-effective and scalable way to increase system capacity. For example, you can add more Web servers during peak hours. However, you can also choose a larger Amazon EC2 instance type to scale applications (such as relational databases) vertically.

From a network perspective, any required DNS updates can be done at the same time.

In addition, after disaster recovery, ensure that redundancy is restored as soon as possible. Continue to back up the system regularly and consider the additional redundancy of the data layer.

The following figure shows the recovery phase of the Pilot Light scenario.

Key steps for recovery:

Start the application Amazon EC2 instance from a custom AMI.

Resize existing database / data storage instances to handle increased traffic.

Add additional database / database instances to ensure the resilience of the DR site at the data layer; if you are using Amazon RDS, enable multiple availability zones to improve availability and persistence.

Change the DNS to point to the Amazon EC2 server.

Install and configure any non-AMI-based system, preferably in an automated manner.

On how to use Pilot Light fast recovery in AWS to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.