> ## Documentation Index
> Fetch the complete documentation index at: https://help.nops.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Locally Redundant Storage for Non-Production Backup Vaults

> Back up non-production workloads to a locally redundant (LRS) vault instead of a geo-redundant one.

Recovery Services and Backup vaults use geo-redundant storage (GRS) by default, which copies every backup to a paired region at a higher price per GB. Backups of development and test systems rarely need that second copy. nOps finds non-production vaults paying for geo-redundant backup storage and estimates the saving from using locally redundant storage (LRS) instead.

| | |
| - | - |
| **Cloud** | Microsoft Azure |
| **Category** | Storage |
| **Service** | Azure Backup |
| **Action** | Modify |
| **Effort** | Medium |
| **Restart needed** | No |
| **Can be rolled back** | Yes |
| **Analysis window** | Last 7 days |
| **Source** | nOps |

## Why it matters

Backup storage grows with every recovery point you keep, and non-production vaults often copy the production vault settings, including geo-redundancy.

## How nOps finds it

nOps reads your pay-as-you-go Azure Backup billing for Standard tier GRS and RA-GRS storage. A vault is flagged when that storage was billed on at least 7 of the last 14 complete days and the vault is non-production. A vault counts as non-production when a word in its resource ID (resource group or resource name) marks it as non-production, such as dev, test, qa, staging, uat, sandbox, demo or poc, and no word marks it as production (prod, production, prd, live, main or master). The saving is the geo-redundant storage cost over the last 7 days, scaled to a month, times the difference between the LRS and current list prices for Azure Backup in the same region. Archive tier recovery points are not counted. It must be at least \$5 a month.

## Before you start

Confirmation that the backups do not need a copy in another region, and permission to create a vault and configure backup.

## How to implement

1. Confirm the protected items are non-production and do not need Cross Region Restore.
2. A vault's storage redundancy can only be changed before any item is protected. Create a new vault and set **Properties → Backup Configuration → Storage replication type** to **Locally-redundant** before protecting anything.
3. Stop protection for each item in the old vault, choosing **Retain backup data** if you need its recovery points, and configure backup for it in the new vault.
4. Delete the old recovery points once they are no longer needed, or let them expire. They keep billing until then.

## Risks and considerations

* LRS backups have no copy in the paired region, and Cross Region Restore is not available.
* The saving arrives gradually, because old recovery points keep billing at the geo-redundant price until they are deleted or expire.
* nOps decides a vault is non-production from its name. Check the classification before changing anything.

## FAQs

> [accordion] Can I change the existing vault to LRS?
>
> Only if no item has been protected in it yet. Otherwise create a new LRS vault and move protection to it.

## Related

* [Switch Non-Production Storage Accounts to Locally Redundant Storage](https://help.nops.io/inform/supported-recommendations/switch-non-production-storage-accounts-to-locally-redundant-storage)
* [Use Zone-Redundant Backup Storage for Azure SQL](https://help.nops.io/inform/supported-recommendations/use-zone-redundant-backup-storage-for-azure-sql)
* [Supported recommendations](https://help.nops.io/inform/supported-recommendations.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.