![]() To enable this, take periodic backups of your system. Here, the best course of action is to revert to the earlier version of the application and the data. ![]() A new version of your application had a software bug that incorrectly computed the pricing and corrupted the existing commerce data served by the platform. Consider an application that computes, maintains, and serves critical commercial data, such as pricing information. IaaS application data issues are another possibility. In this case, taking backups less often would reduce your cost. So you have a higher level of tolerance for losing part of the data on the reporting server. In this case, you don’t really experience data loss, even if the reporting server is hit with a disaster. However, it's possible to regenerate the output by rerunning the reporting process. The loss of this VM or disks could lead to the loss of the reports. For example, if the application runs daily and modifies data, then the backup should be taken hourly.Īnother common scenario involves a reporting server that pulls data from other sources and generates aggregated reports. Backup frequency should be based on the nature of the VM workload. In this case, it's important to make sure you take backups regularly. It could be a web server or file server holding content and other resources of a site, or a custom-built business application running on a VM that stored its data, resources, and application state on the VM disks. In this scenario, you have an application with a typical production workload running on an Azure VM (IaaS application workload). However, to protect the workload from a regional-level failure, consider spreading the cluster across two regions or making periodic backups to another region. This type of architecture already provides a high level of redundancy within that region. ![]() In this scenario, you have a workload handled by a cluster of VMs that provide redundancy and load balancing, like a Cassandra cluster deployed in a region. The replicas for high availability are used. NoSQL databases, like MongoDB, also support replicas for redundancy. For SQL Server, use SQL Server Always On Availability Groups for high availability. Relational databases, such as SQL Server and Oracle, provide various options for replication. (Optional) A replica of the database in a different region as backupĭepending on your requirements for server availability and data recovery, solutions could range from an active-active or active-passive replica site to periodic offline backups of the data.The data must be protected and recoverable.The disaster recovery plan for this system should include the following requirements: Critical production applications and users depend on this database. In this scenario, you have a production database server (such as SQL Server and Oracle) that supports high availability. ![]() Let’s look at a few examples of application workload scenarios and things to consider when planning for backup and disaster recovery. For more information, see Disaster Recovery for Azure Applications. This ensures your backups aren’t affected by the same events that affected your other resources. To protect IaaS workloads from regional disasters, create backups in a different geographic location than your primary site. To protect your IaaS workloads from outages, plan for redundancy, and create regular backups. Reverting to a good state requires regular backups. When these happen, you might want to revert the application and the data to a prior version that contains the last known good state. In addition to platform failures, problems with an application or data can also occur (such as accidental deletes and ransomware attack). However, major disasters (such as earthquakes, fires, or hurricanes) can result in outages or inaccessibility of large-scale storage servers, sometimes impacting a whole data center or zone (impacting LRS disks), or an entire region (impacting ZRS disks). Zone-redundant storage (ZRS) provides synchronous replication of data across zones in a region, enabling disks to tolerate zonal failures that may occur due to natural disasters or hardware issues.LRS protects your data against server rack and drive failures. Locally redundant storage (LRS) replicates your data three times within a single data center in a particular region.Azure built-in redundancy optionsĪzure managed disks have two built-in redundancy options to protect your data against failures: Finally, it compares each backup and disaster recovery option for Azure managed disks. After that, it covers typical backup and disaster recovery scenarios. It introduces Azure built-in redundancy and some common failure types. This article explains how to plan for backup and disaster recovery for Azure managed disks. Applies to: ✔️ Linux VMs ✔️ Windows VMs ✔️ Flexible scale sets
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |