Differences

This shows you the differences between two versions of the page.

--- azure:az-104_2024:azure_storage [2024/10/11 12:55] – [☝️ Redundancy/Replication] mmuze
+++ azure:az-104_2024:azure_storage [2024/10/16 19:34] (current) – [☝️ Redundancy/Replication] mmuze
@@ Line 21: / Line 21: @@
   * Premium Page Blobs
-  * Premium performance storage accounts use solid-state drives (SSDs) for low latency and high throughput.
+  * <color :#fff200>Premium</color> performance storage accounts use solid-state drives (SSDs) for low latency and high throughput.
 ====== Data Protection ======
@@ Line 34: / Line 34: @@
 ====== ☝️ Redundancy/Replication ======
   * **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 :#fff200>synchronously</color> three times within a single physical location in the primary region
     * LRS protects your data against server rack and drive failures.
+      * Data is replicated to different racks/drives than the primary storage.
   * **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 :#fff200>synchronously</color> three times within a single physical location in the primary region using LRS. It then copies your data <color :#fff200>asynchronously</color> to a single physical location in the secondary region. Within the secondary region, your data is copied synchronously three times using LRS
     * <color :#fff200>Stated another way, GRS stores data using LRS in two different regions.</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.
@@ Line 48: / Line 49: @@
 Azure Files does not support read-access geo-redundant storage (RA-GRS) or read-access geo-zone-redundant storage (RA-GZRS).
 </callout>
+  * 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://learn.microsoft.com/en-us/azure/storage/common/redundancy-migration]]
 ====== Access Tiers ======
   * [[https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview]]
   * <color :#fff200>Access Tiers only apply to block blobs.</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.
 <callout type="warning">
-This is kind of counterintuitive, as of 2024-10-11 blobs in General Purpose V2 (GPV2) storage account can be set to Hot/Cool/Archive, but data stored in a premium block blob storage account cannot be tiered. Microsoft is working on supporting tiers for premium blob storage in the future.
+This is kind of counterintuitive, as of 2024-10-11, blobs in General Purpose V2 (GPV2) storage account can be set to Hot/Cool/Archive, but data stored in a premium block blob storage account cannot be tiered. Microsoft is working on supporting tiers for premium blob storage in the future.
 </callout>
 ===== Tiers =====
+  * [[https://learn.microsoft.com/en-us/azure/storage/blobs/access-tiers-overview]]
   * Hot
   * Cool
@@ Line 66: / Line 73: @@
 ====== Lifecycle Management ======
   * 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/Export ======
+>Azure Import/Export service is used to securely import large amounts of data to Azure Blob storage and Azure Files by shipping disk drives to an Azure datacenter. This service can also be used to transfer data from Azure Blob storage to disk drives and ship to your on-premises sites. Data from one or more disk drives can be imported either to Azure Blob storage or Azure Files.
-====== Import/Export ======
   * [[https://learn.microsoft.com/en-us/azure/backup/backup-azure-restore-files-from-vm]]
   * Exporting data from an Azure storage account is only supported for //blob// storage.
@@ Line 75: / Line 83: @@
 ====== Object Replication ======
   * [[https://learn.microsoft.com/en-us/azure/storage/blobs/object-replication-overview]]
+  * Object level replication is distinct from storage account level replication.
+  * Object replication is supported for general-purpose v2 storage accounts and premium block blob accounts.
+  * Both the source and destination accounts must be either general-purpose v2 or premium block blob accounts.
+  * Object replication supports block blobs only; append blobs and page blobs aren't supported.
+  * Change Feed and Blob Versioning must be enabled to support replication.
+<callout type="warning">
+Because block blob data is replicated asynchronously, the source account and destination account are not immediately in sync. There's currently no SLA on how long it takes to replicate data to the destination account.
+</callout>
 ====== Disk Encryption ======
   * <color :#fff200>There are several types of encryption available for your managed disks, including Azure Disk Encryption (ADE), Server-Side Encryption (SSE), and encryption at host.</color>