Move azure table and queue storage to another region

Siva Sankararao Arudra 61 Reputation points
2022-02-17T12:31:03.663+00:00

Hi Team,

I've followed the below article and moved my storage account to another region and transferred all blob and file storage data to the target storage account successfully using the AzCopy tool.

https://video2.skills-academy.com/en-us/azure/storage/common/storage-account-move?tabs=azure-portal

now, I can't transfer data for table and queue storage, is there any possible way to do this?

Please assist me. thanks in advance

Azure Table Storage
Azure Table Storage
An Azure service that stores structured NoSQL data in the cloud.
170 questions
Azure Queue Storage
Azure Queue Storage
An Azure service that provides messaging queues in the cloud.
105 questions
Accepted answer
  1. sadomovalex 3,631 Reputation points
    2022-03-08T15:11:52.1+00:00

    for moving table storage you may use https://github.com/Luminis-Arnhem/AzureStorageBackup: with this library you may backup table storage data first and then restore it on target resource group. Important moment is that it uses AzCopy 7.3 internally because later versions don't support backup of tables:

    AzCopy 7.3 is used to create the backups, later version don't support table storage.

    For queues I agree that it is quite rare scenario: usually message live in queue short time until processed and then removed. But if you need to copy queues you probably need to create custom app which will do that like it was suggested above.

    0 comments

1 additional answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. GeethaThatipatri-MSFT 29,387 Reputation points Microsoft Employee
    2022-02-22T14:59:40.63+00:00

    Hi, @Siva Sankararao Arudra Thanks for your patience,
    Storage queues are similar to service bus queue. the messages are not designed to store permanent like blobs/files. once the receiver processes the messages, they would be deleted. I don't think you can move any data from the queue only thing that would make sense is to create queues with the same names and point your applications to a new storage endpoint however, for table storage you can refer Copy data to and from Azure Table storage by using Azure Data Factory

    a workaround can be done using a custom application.

    1. List all queues from the source
    2. create queues with the same names in the destination
    3. Read every message from the source and write them to the destination

    Please let us know if this information helps.

    Regards
    Geetha

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.