Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| azure:az-104_2024:azure_storage [2024/10/11 15:38] – [Object Replication] mmuze | azure:az-104_2024:azure_storage [2024/10/16 19:34] (current) – [☝️ Redundancy/Replication] mmuze | ||
|---|---|---|---|
| Line 34: | Line 34: | ||
| ====== ☝️ Redundancy/ | ====== ☝️ Redundancy/ | ||
| * **Locally-redundant storage (LRS)**: storage is redundant in the same location (AZ) as the primary storage | * **Locally-redundant storage (LRS)**: storage is redundant in the same location (AZ) as the primary storage | ||
| - | * //LRS// copies your data synchronously three times within a single physical location in the primary region | + | * //LRS// copies your data <color :# |
| * LRS protects your data against server rack and drive failures. | * LRS protects your data against server rack and drive failures. | ||
| * Data is replicated to different racks/ | * Data is replicated to different racks/ | ||
| * **Zone-redundant storage (ZRS)**: storage is redundant across multiple availability zones in a single region | * **Zone-redundant storage (ZRS)**: storage is redundant across multiple availability zones in a single region | ||
| - | * **Geo-redundant storage (GRS)**: copies your data synchronously three times within a single physical location in the primary region using LRS. It then copies your data asynchronously to a single physical location in the secondary region. Within the secondary region, your data is copied synchronously three times using LRS | + | * **Geo-redundant storage (GRS)**: copies your data <color :# |
| * <color :# | * <color :# | ||
| * **Geo-zone-redundant storage (GZRS)**: this is a combination of GRS and ZRS; data is replicated across three AZ's in the primary region and in one location in the secondary region. | * **Geo-zone-redundant storage (GZRS)**: this is a combination of GRS and ZRS; data is replicated across three AZ's in the primary region and in one location in the secondary region. | ||
| Line 51: | Line 51: | ||
| * You can convert from one type of replication to another, but converting to/from LRS is a special case that requires more than just toggling the option in the portal. | * You can convert from one type of replication to another, but converting to/from LRS is a special case that requires more than just toggling the option in the portal. | ||
| + | * [[https:// | ||
| ====== Access Tiers ====== | ====== Access Tiers ====== | ||
| * [[https:// | * [[https:// | ||
| * <color :# | * <color :# | ||
| + | * For blob storage access tiers can be specified at the blob level. | ||
| + | * For file shares the access tier is specified at the share level. | ||
| * The different tiers vary in the storage costs, access costs and retrieval time. | * The different tiers vary in the storage costs, access costs and retrieval time. | ||
| <callout type=" | <callout type=" | ||
| Line 70: | Line 73: | ||
| ====== Lifecycle Management ====== | ====== Lifecycle Management ====== | ||
| * Lifecycle management policies are supported for block blobs and append blobs in general-purpose v2, premium block blob, and Blob Storage accounts. | * Lifecycle management policies are supported for block blobs and append blobs in general-purpose v2, premium block blob, and Blob Storage accounts. | ||
| + | * Before you configure a lifecycle management policy, you can choose to enable blob access time tracking. When access time tracking is enabled, a lifecycle management policy can include an action based on the time that the blob was last accessed with a read or write operation. | ||
| + | ====== Import/ | ||
| + | >Azure Import/ | ||
| - | |||
| - | ====== Import/ | ||
| * [[https:// | * [[https:// | ||
| * Exporting data from an Azure storage account is only supported for //blob// storage. | * Exporting data from an Azure storage account is only supported for //blob// storage. | ||