I'm expanding our infrastructure into Azure and currently have everything on-premise. I've set up a decent landing zone, but now I'm working on adding some resiliency. I understand that zonal redundancy means replicating resources across three zones in a single region. For Azure Site Recovery, is replicating within the same zone sufficient, or do I really need to set up a paired region for added security? I've been seeing a lot of discussions about paired regions, and I'm curious if it's truly necessary if we use zonal redundancy in the same area.
3 Answers
It really depends on how critical your workloads are. I usually discuss this with clients to let them decide what's best for their needs. While it's rare for an entire Azure region to go down, it can happen, and communication failures are more common, which could affect availability. You should definitely weigh these factors when deciding on your redundancy strategy.
Zonal redundancy can be beneficial, especially for certain systems like Domain Controllers. It's a good practice to have them in different zones. But, if your services don’t have zonal redundancy or if you need quick recovery, you might want to look at setting up Azure Site Recovery with GRS and backup in a paired region. This way, in case of a major outage, you have a plan to restore services without a hitch.
I totally get where you're coming from! Your business requirements will dictate whether zonal redundancy is sufficient. Just to keep in mind, different subscriptions can map logical availability zones to separate physical zones, which might impact your setup depending on what you're trying to achieve.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures