Locally Redundant Storage
Definition
Locally Redundant Storage in Azure maintains three synchronous copies of data within a single data center, ensuring high availability and durability.
Use Cases
- Microsoft: Storing Azure platform diagnostic logs and temporary operational data where durability within a datacenter is sufficient and cross-region disaster recovery is handled separately. — Uses Azure Storage accounts configured with LRS for certain internal telemetry/log pipelines, relying on application-level retention and separate DR strategies rather than geo-replication for every dataset. (Lower storage cost for high-volume, lower-criticality data while maintaining protection against individual disk/node failures inside a datacenter.)
- Stack Overflow: Non-critical artifacts and transient data (e.g., intermediate build outputs or cache-like blobs) where a full datacenter outage can be tolerated because the data can be regenerated. — Stores regenerable objects in Azure Blob Storage using LRS and keeps source-of-truth data in more resilient systems and backups. (Reduced storage spend for large volumes of data that does not require regional disaster recovery, while keeping critical data protected via other mechanisms.)
Provider Equivalents
- AWS: Amazon S3 Standard (single-Region) + S3 Replication Time Control not applicable; closest concept is single-Region storage without cross-Region replication
- Azure: Azure Storage Locally Redundant Storage (LRS)
- GCP: Google Cloud Storage Regional (single-region) or Dual-region (not equivalent); closest is Regional within one region
- OCI: OCI Object Storage (standard) within a region; closest concept is storing data in a single region without cross-region replication
Frequently Asked Questions
- What's the difference between Locally Redundant Storage (LRS) and Zone-Redundant Storage (ZRS)?
- LRS copies your data three times inside a single datacenter, protecting against local hardware failures. ZRS replicates data across multiple availability zones in the same region, so it can keep serving data even if one datacenter/zone goes down. ZRS generally costs more than LRS but provides higher availability and resilience within the region.
- When should I use Locally Redundant Storage (LRS)?
- Use LRS when you want the lowest-cost redundancy and your workload can tolerate losing a whole datacenter (or you have another recovery plan). Common fits include dev/test data, temporary files, caches, easily re-creatable datasets, and backups that are also copied elsewhere. Avoid LRS for mission-critical data that must survive a datacenter outage without manual recovery.
- How much does Locally Redundant Storage (LRS) cost?
- LRS is typically the lowest-cost Azure Storage redundancy option. Pricing depends on the storage service (Blob, Files, Disks), performance tier (Standard vs Premium), access tier (Hot/Cool/Archive for Blob), region, capacity stored (GB/TB), and transactions/egress. For exact numbers, compare the 'LRS' price line items to ZRS/GRS/GZRS in the Azure Storage pricing page for your region and service.
Category: data
Difficulty: intermediate
Related Terms
See Also