Azure Recovery Vault Geo-Redundant Downgrade
Geo-redundant backup storage costs more than locally-redundant because it replicates to a paired region, which only matters if you would restore across regions.
Free to start. No card. The playground just needs your work email.
Azure
Found, explained, fixed.
Findings with a dollar figure attached, idle, oversized, orphaned, unscheduled and undiscounted spend.
Detect
ZopNight checks this automatically across Azure, with read-only access to the account.
Explain
Every finding says exactly what to change: Move the non-production vault to locally redundant storage. Where the saving can be proven it is priced; where it cannot, the finding says so.
Fix
After a guided review, where you confirm the change, ZopNight applies a lifecycle policy, then checks the change took.
- Applies to
- Recovery Vaults on Azure
- The fix, by hand
- Confirm this Recovery Services vault backs only non-production workloads and a second-region copy is not a business requirement.
- Recovery Services vault → the resource → Properties → Backup Configuration.
- If cross-region restore is enabled, disable it first. Azure blocks the replication change while CRR is on.
- Change Storage replication type to LocallyRedundant (LRS).
- Azure applies the change only while the vault holds no protected items. If items exist, stop protection with retain-data first, switch replication, then restore protection.
- Save the configuration and verify the new replication type on the Properties blade.
ZopNight does this for you after a guided review.
- Category
- Rightsizing. Resources sized for headroom they never use. A smaller size runs the same workload for less.
- Where it appears
- The Savings tab of Recommendations, with every affected resource listed.
- Rule ID
RC-1393- Full reference
Related checks
See the oversized resources in your account.
Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.
Prefer to talk it through first? Book 20 minutes with the team.
- $30M+annualised cloud spend under management
- 550K+resources tracked since launch
- 20-60%off the bill in the first month
- SOC 2Type II report, plus ISO 27001
Figures published on zop.dev.