4/5/2023 0 Comments Birdfont delete point![]() Microsoft recommends enabling container soft delete and blob versioning together with blob soft delete to ensure complete protection for blob data. To restore a container and its contents, container soft delete must also be enabled for the storage account. You can use blob soft delete only to restore an individual blob, snapshot, directory (in a hierarchical namespace) or version. Version and higher of the Azure Storage REST API support blob soft delete. Storage accounts with a hierarchical namespace aren't currently supported. If you disable blob soft delete, you can continue to access and recover soft-deleted objects in your storage account until the soft delete retention period has elapsed.īlob versioning is available for general-purpose v2, block blob, and Blob storage accounts. Any data that was deleted before the retention period was changed is subject to the retention period that was in effect when it was deleted.Īttempting to delete a soft-deleted object doesn't affect its expiry time. An updated retention period applies only to data that was deleted after the retention period was changed. You can change the soft delete retention period at any time. The following diagram shows how a deleted object can be restored when blob soft delete is enabled: ![]() While the retention period is active, you can restore a deleted blob, together with its snapshots, or a deleted version by calling the Undelete Blob operation. The clock starts on the retention period as soon as an object is deleted or overwritten. The retention period indicates how long the data remains available after it's deleted or overwritten. When you enable blob soft delete for a storage account, you specify a retention period for deleted objects of between 1 and 365 days. 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 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.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.For optimal protection for your blob data, Microsoft recommends enabling all of the following data protection features: Recommended data protection configurationīlob soft delete is part of a comprehensive data protection strategy for blob data. After the retention period has expired, the object is permanently deleted. During the retention period, you can restore a soft-deleted object to its state at the time it was deleted. ![]() Blob soft delete protects an individual blob, snapshot, or version from accidental deletes or overwrites by maintaining the deleted data in the system for a specified period of time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |