Unable to access the container since a point in time restore on a single container in Azure Blob Storage

Bidass 26 Reputation points
2022-03-02T17:04:42.2+00:00

Here is the issue :
8 hours ago, I have made a PITR restore of a single container on my Blob Storage Account (There is a few files, it's not big). Since I have made this operation I am not able to retrieve the container in the storage explorer (even using the REST API). In the Blob Storage setting panel storage explorer I am having the following message when typing the name of the restored container :
179307-image.png

If I try to edit some settings in the resource, I am having the following issue :
179391-image.png

It seems like the PITR is stuck somewhere... For a single container, it might not take so long.

Azure Storage Explorer
Azure Storage Explorer
An Azure tool that is used to manage cloud storage resources on Windows, macOS, and Linux.
240 questions
Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,874 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,578 questions
0 comments
Accepted answer
  1. deherman-MSFT 35,011 Reputation points Microsoft Employee
    2022-03-02T23:36:03.57+00:00

    @bidass-2692
    I understand you have performed a point-in-time restore and are getting the above error when trying to view your container. Please correct me if I am misunderstanding.

    When you perform a restore operation, Azure Storage blocks data operations on the blobs in the ranges being restored for the duration of the operation. Read, write, and delete operations are blocked in the primary location. For this reason, operations such as listing containers in the Azure portal may not perform as expected while the restore operation is underway.

    The time that it takes to restore a set of data is based on the number of write and delete operations made during the restore period after up to one hour for the restore job to be picked up. For example, an account with one million objects with 3,000 objects added per day and 1,000 objects deleted per day will require approximately two-three hours to restore to a point 30 days in the past. A restore with a small number of changes would require up to one hour to restore. A retention period and restoration more than 90 days in the past would not be recommended for an account with this rate of change.

    If you are still seeing this restore not complete and are still facing the above error, we recommend creating a support ticket. If you do not have a support plan please let me know and I can work with you directly to assist.

    Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest