Refine data recovery section in README for clarity and conciseness
This commit is contained in:
@@ -65,16 +65,11 @@ This example provides quick rollback using storage-account level protection (`so
|
|||||||
|
|
||||||
## Data Recovery
|
## Data Recovery
|
||||||
|
|
||||||
### Operational recovery (Azure Blobs)
|
Short-term recovery from accidental deletion or modification can be achieved using the built-in Azure Storage Account data protection features enabled in this module.
|
||||||
|
|
||||||
For Azure Blobs, this module enables the storage-account level protection features used for operational recovery: blob soft delete, container soft delete, blob versioning, change feed, and point-in-time restore. This is intended for short-term rollback and fast recovery after accidental delete, overwrite, or data corruption events.
|
|
||||||
|
|
||||||
In this module, Azure Blobs operational recovery is configured through the Blob Data Protection inputs (`enable_blob_soft_delete`, `enable_blob_versioning`, `enable_blob_change_feed`, and `enable_point_in_time_restore_for_containers`) in the main storage-account example above.
|
|
||||||
|
|
||||||
### Azure Backup recovery (vaulted)
|
### Azure Backup recovery (vaulted)
|
||||||
|
|
||||||
To add the vaulted recovery option, the `backup-vault` module is required.
|
To add a long-term vaulted recovery option, the `backup-vault` module is required. After creating the vault, configure Azure Backup (policy and backup instance) to protect the storage account for vaulted retention and restore workflows.
|
||||||
After creating the vault, configure Azure Backup (policy and backup instance) to protect the storage account for vaulted retention and restore workflows.
|
|
||||||
|
|
||||||
```hcl
|
```hcl
|
||||||
module "state_storage" {
|
module "state_storage" {
|
||||||
|
|||||||
Reference in New Issue
Block a user