MISC Questions Flashcards
Backup and Restore
Description:
Use Case:
Recovery Time Objective:
Description: This is the simplest and most cost-effective strategy. It involves taking regular backups of your data and storing them in a secure location.
Use Case: Suitable for non-critical applications where downtime is acceptable.
Recovery Time Objective (RTO): Hours to days, depending on the amount of data and the complexity of the environment.
Pilot Light
Description:
Use Case:
RTO:
Description: This strategy involves maintaining a minimal version of your environment in the cloud. Critical components are always running, but at a minimal scale. In the event of a disaster, you can quickly scale up these components to handle production traffic.
Use Case: Suitable for critical applications that require a faster recovery time but where cost is still a concern.
RTO: Minutes to hours.
Example: Keep a small database instance running and replicate data continuously. In a disaster, scale up the database and launch the necessary application servers.
Warm Stanby
Description:
Use Case:
RTO:
Description: A scaled-down version of a fully functional environment is always running in the cloud. It can handle some traffic but needs to be scaled up to handle full production loads.
Use Case: Suitable for applications that need a balance between cost and recovery time.
RTO: Minutes.
Example: Run a smaller version of your application in another region. In a disaster, increase the instance sizes and number of instances to handle the full load.
Multi-Site (Active/Active)
Description:
Use Case:
RTO:
Description: This strategy involves running your application simultaneously in multiple locations. Both sites are active and can handle traffic.
Use Case: Suitable for mission-critical applications that require near-zero downtime.
RTO: Near zero.
Example: Deploy your application in multiple AWS regions. Use Route 53 for DNS failover to route traffic to the healthy region in case of a disaster.
Active /Passive
Description:
Use Case:
RTO:
Description: Similar to Multi-Site, but only one site is active at a time. The passive site becomes active only during a failover.
Use Case: Suitable for applications that need high availability but can tolerate a short downtime.
RTO: Minutes to hours.
Example: Use AWS Elastic Load Balancing to direct traffic to the active site. In a disaster, manually or automatically switch to the passive site.
