If the write operation creates a new blob, then the resulting blob is the current version of the blob. Write operations include Put Blob, Put Block List, Copy Blob, and Set Blob Metadata. When blob versioning is turned on, each write operation to a blob creates a new version. The version ID remains the same for the lifetime of the version. This header contains the version ID for the current version of the blob that was created by the write operation. When you call a write operation to create or modify a blob, Azure Storage returns the x-ms-version-id header in the response. If you omit the version ID, the operation acts against the current version. You can perform read or delete operations on a specific version of a blob by providing its version ID. The version ID is assigned at the time that the version is created. The value of the version ID is the timestamp at which the blob was updated. Version IDĮach blob version is identified by a unique version ID. For more information on locking a storage account, see Apply an Azure Resource Manager lock to a storage account. To prevent accidental deletion of the storage account, configure a lock on the storage account resource. Version and higher of the Azure Storage REST API supports blob versioning.īlob versioning cannot help you to recover from the accidental deletion of a storage account or container. Storage accounts with a hierarchical namespace enabled for use with Azure Data Lake Storage Gen2 aren't currently supported. For more information about lifecycle management, see Optimize costs by automating Azure Blob Storage access tiers.īlob versioning is available for standard general-purpose v2, premium block blob, and legacy Blob storage accounts. You can use lifecycle management to automatically delete old versions. Microsoft recommends maintaining fewer than 1000 versions per blob. Having a large number of versions per blob can increase the latency for blob listing operations. You can't modify the content or metadata of an existing blob version. The following diagram shows how versions are created on write operations, and how a previous version may be promoted to be the current version:īlob versions are immutable. Any previous versions of the blob persist. When you delete a blob, the current version of the blob becomes a previous version, and there's no longer a current version. A new version is created to capture the updated state, and that new version is the current version. When you modify an existing blob, the current version becomes a previous version. When you create a new blob, a single version exists, and that version is the current version. A blob can have only one current version at a time. When blob versioning is enabled for a storage account, Azure Storage automatically creates a new version with a unique ID when a blob is first created and each time that the blob is subsequently modified.Ī version ID can identify the current version or a previous version. Each version is identified with a version ID. How blob versioning worksĪ version captures the state of a blob at a given point in time. For more information about lifecycle management, see Optimize costs by automating Azure Blob Storage access tiers. To minimize costs, use a lifecycle management policy to automatically delete old versions. For this reason, enabling blob versioning may result in additional costs. To learn more about Microsoft's recommendations for data protection, see Data protection overview.Īfter you enable blob versioning for a storage account, every write operation to a blob in that account results in the creation of a new version. To learn how to enable blob soft delete, see Enable and manage soft delete for blobs. Blob soft delete, to restore a blob, snapshot, or version that has been deleted.To learn how to enable container soft delete, see Enable and manage soft delete for containers. Container soft delete, to restore a container that has been deleted.To learn how to enable blob versioning, see Enable and manage blob versioning. When blob versioning is enabled, you can restore an earlier version of a blob to recover your data if it's erroneously modified or deleted. Blob versioning, to automatically maintain previous versions of a blob.For optimal protection for your blob data, Microsoft recommends enabling all of the following data protection features: Recommended data protection configurationīlob versioning is part of a comprehensive data protection strategy for blob data. When blob versioning is enabled, you can access earlier versions of a blob to recover your data if it's modified or deleted. You can enable Blob storage versioning to automatically maintain previous versions of an object.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |