Data restore scenarios for Azure Storage service
This article describes the data restore scenarios for Azure Storage service.
Original product version: Blob Storage
Original KB number: 4012226
After the storage account or blob container is deleted, it is queued to be recycled and collected by the garbage collector. The system can then free up space for reuse. The deleted storage account or blob container may be restored if the garbage collector has not yet run and the storage space is not yet cleaned up.
The time at which the garbage collector is run varies depending on many factors, such as workloads on the storage scale unit, the number of available storage spaces, and so on. On average, the garbage collection of storage accounts occurs 14 days after deletion. However, this time to restore is not guaranteed.
Data restore scenarios
The following resources can be restored if they have not been collected by the garbage collector:
- Storage account
- Blob container in geo-redundant storage, zone-redundant storage, or read-access geo-redundant storage
A new Shared Access Signature (SAS) token is required for restoring.
Restoring the Blob container in the Local redundant storage is not supported.
Azure supports only the storage account level or Blob container level restoring. Therefore, the following data restore scenarios are not supported:
- Restoring Queue
- Restoring blob data (individual blob) in the storage account
- Restoring partial data in the storage account, such as files inside of a blob
- Restoring partial data in Table or Queue