Why Azure site recovery may not meet RPO?

All we need is an easy explanation of the problem, so here it is.

While Azure Site Recovery may meet RTO, it may not meet RPO since it
is not accounting for where data is inside SQL Server.

I am looking for an example for what it means by "is not accounting for where data is inside SQL Server".

How to solve :

I know you bored from this bug, So we are here to help you! Take a deep breath and look at the explanation of your problem. We have many solutions to this problem, But we recommend you to use the first method because it is tested & true method that will 100% work for you.

Method 1

Looking at Microsoft’s “About Azure Recovery”, we can see this:

RTO and RPO targets
Keep recovery time objectives (RTO) and recovery point objectives (RPO) within organizational limits. Site Recovery provides continuous replication for Azure VMs and VMware VMs, and replication frequency as low as 30 seconds for Hyper-V. You can reduce RTO further by integrating with Azure Traffic Manager.

Data “inside SQL Server” would be data that has not yet been replicated elsewhere, be it Azure, a replication distributor, or a local mirror. Losing 30 seconds of data for most organizations is a tolerable amount of failure, but any company that requires real-time loading and querying will be chomping at the bit about that 30-second gap between the time the primary instance went down and the replicated secondary in Azure picked up 🤐

Note: Use and implement method 1 because this method fully tested our system.
Thank you 🙂

All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

Leave a Reply