How to move data from a snapshot/managed disk to an Azure storage account?

Question

How to move data from a snapshot/managed disk to an Azure storage account?

Shayne Mei 20

Goal is to move all data from a snapshot to an azure storage account. Tried running az cli from the cloud shell to move data directly from the snapshot but it complained that the data size is too big. Then I tried creating a disk, attach it to a VM, and then run azcopy, with a URL with SAS token, but I got the following error:

INFO: Scanning...
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support
failed to perform copy command due to error: cannot start job due to error: failed to scan path "...." due to stat "....": no such file or directory.

I have verified that the file path is a full path and accessible from the VM. I've also gone through a debug session with a microsoft Senior Digital Technical Specialist and wasn't able to resolve this.

Syed Aaqid Ali 580 Reputation points Microsoft External Staff Volunteer Moderator

2025-04-08T20:06:17.9633333+00:00
Hello Shayne Mei,

To move data from a managed disk to an Azure storage account, you can use the Azure CLI. Here are the general steps:

Launch Azure Cloud Shell: Open the Azure Cloud Shell, which has the necessary tools preinstalled. You can do this by selecting Try it from the upper right corner of a code block or by navigating to the Cloud Shell in your browser by going to https://shell.azure.com.

Sign in to Azure: If you need to use a different subscription, you can sign in using the following command, replacing subscriptionId with your Azure subscription ID:

subscription="subscriptionId" # Set Azure subscription ID here az account set -s $subscription # ...or use 'az login'

Run the script: You can then run the appropriate script to copy the managed disk to the storage account. The specific commands will depend on whether you are copying a snapshot or a managed disk directly.

Clean up resources: After the operation, you may want to clean up resources by deleting the resource group or any related resources using:

az group delete --name myResourceGroupName

Make sure to check the prerequisites and ensure that you have the necessary permissions and configurations set up in your Azure environment.

References:

Export/Copy a managed disk to a storage account using the Azure CLI

Copy snapshot of a managed disk to same or different subscription with CLI

Prerequisites

Please do not forget to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.
Shayne Mei 20 Reputation points

2025-04-08T20:11:42.9633333+00:00

I did try az storage blob copybut it complained that the snapshot size is too big (16G snapshot). I did some research and found azcopy handles the chunking natively, but I'm having trouble running azcopy.
Syed Aaqid Ali 580 Reputation points Microsoft External Staff Volunteer Moderator

2025-04-08T22:47:40.2466667+00:00
Shayne Mei this looks like it might be some kind of syntax issue in your command line. Have you run other AzCopy commands that were successful? If so, can you compare their command lines to the failed one, and let us know of any significant differences? Additionally, here are few steps you can take to troubleshoot this issue:

Verify the Path: Ensure that the path you are using in the command is correct and that the file or directory exists at that location.

Check Permissions: Make sure you have the necessary permissions to access the file or directory and required permissions to upload into the storage account.

Use Correct Syntax: Double-check that you are using the correct syntax for the az storage blob copy command.

Check for Hidden Files: Sometimes, files may be hidden or not visible. Make sure that the file you are trying to copy is not hidden.

Here are example commands azcopy_copy,

Upload a single file by using a SAS token: - azcopy cp "/path/to/file.txt" "https://[account].blob.core.windows.net/[container]/[path/to/blob]?[SAS]" Upload a single file by using a SAS token and piping (block blobs only): - cat "/path/to/file.txt" | azcopy cp "https://[account].blob.core.windows.net/[container]/[path/to/blob]?[SAS]" --from-to PipeBlob Upload an entire directory by using a SAS token: - azcopy cp "/path/to/dir" "https://[account].blob.core.windows.net/[container]/[path/to/directory]?[SAS]" --recursive=true or - azcopy cp "/path/to/dir" "https://[account].blob.core.windows.net/[container]/[path/to/directory]?[SAS]" --recursive=true --put-md5 Upload a set of files by using a SAS token and wildcard (*) characters: - azcopy cp "/path/*foo/*bar/*.pdf" "https://[account].blob.core.windows.net/[container]/[path/to/directory]?[SAS]"

Use single quotes in all command shells except for the Windows Command Shell (cmd.exe). If you're using a Windows Command Shell (cmd.exe), enclose path arguments with double quotes ("") instead of single quotes ('').

https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azcopy-blobs-upload
Syed Aaqid Ali 580 Reputation points Microsoft External Staff Volunteer Moderator

2025-04-09T16:09:41.99+00:00

Hi Shayne Mei, checking to see if the solution proposed helped (pointed you in the right direction) > please do not forget to “up-vote”. which might be beneficial to other community members reading this thread. And, if you have any further queries do let us know.
Shayne Mei 20 Reputation points

2025-04-09T20:14:25.5433333+00:00

Unfortunately it did not work. I get the exact same error failed to perform copy command due to error: cannot start job due to error: failed to scan path

This is the command i used:
azcopy copy '<path-to-file-on-azure-disk>' 'https://<storage-account>.blob.core.windows.net/<container>/<blob>/?<SAS>' --recursive=true

I have also verified that the file path exists, the file permission is also correctly set.

Interestingly, I tried running on another random file on the azure vm home path (not on the mounted managed disk I want to move) , and it worked. So it seems like there's something wrong with azcopy accessing the mounted disk? But I can't figure out what might be wrong since I can access everything on that mounted disk just fine.

Another thought, is there a way to run azcopy from the azure cloud shell to move a snapshot directly so we can circumvent the mounted disk issue?

Syed Aaqid Ali 580 Microsoft External Staff Volunteer Moderator

Shayne Mei, You're absolutely right in your observation, the issue is likely due to how AzCopy interacts with mounted managed disks. AzCopy is optimized to work with Azure Blob Storage paths and local file systems, but it often has trouble accessing mounted Azure managed disks, especially if they're not exposed like traditional file systems or if there are underlying permission/driver limitations in the VM OS.

That's why you’re seeing the command succeed for files in your VM’s local/home path, but fail when pointing to files on the mounted managed disk — even though you can access them normally from the shell.

For running AzCopy from the azure cloud shell, yes you can run AzCopy from the Azure Cloud Shell. Azure Cloud Shell comes with AzCopy preinstalled, allowing you to use it directly from the terminal.

#Provide the subscription Id where snapshot is created
subscriptionId="<subscriptionId>"

#Provide the name of your resource group where snapshot is created
resourceGroupName=myResourceGroupName

#Provide the snapshot name 
snapshotName=mySnapshotName

#Provide Shared Access Signature (SAS) expiry duration in seconds e.g. 3600.
#Know more about SAS here: https://docs.microsoft.com/azure/storage/storage-dotnet-shared-access-signature-part-1
sasExpiryDuration=3600

#Provide storage account name where you want to copy the snapshot. 
storageAccountName=mystorageaccountname

#Name of the storage container where the downloaded snapshot will be stored
storageContainerName=mystoragecontainername

#Provide the key of the storage account where you want to copy snapshot. 
storageAccountKey=mystorageaccountkey

#Provide the name of the VHD file to which snapshot will be copied.
destinationVHDFileName=myvhdfilename

az account set --subscription $subscriptionId

sas=$(az snapshot grant-access --resource-group $resourceGroupName --name $snapshotName --duration-in-seconds $sasExpiryDuration --query [accessSas] -o tsv)

az storage blob copy start --destination-blob $destinationVHDFileName --destination-container $storageContainerName --account-name $storageAccountName --account-key $storageAccountKey --source-uri $sas

Additionally, you can also try using PowerShell as explained here

https://github.com/Azure/azure-docs-powershell-samples/blob/master/virtual-machine/copy-managed-disks-vhd-to-storage-account/copy-managed-disks-vhd-to-storage-account.ps1

Venkatesan S 2,820 Microsoft External Staff Moderator

Hi Shayne Mei

Here is the complete process to copy data from an Azure disk to an Azure storage account.

In my environment, I have Azure disk with Size 1024GiB.

Portal: enter image description here

Make sure the disk in Unattached state to export the data from disk to azure storage.

Go to your Disk -> under Setting section-> Disk export ->Check the Enable data access authentication mode -> Click the Generate URL.

Portal: enter image description here

After clicking URL you will get the screen like below:

Portal:
enter image description here

Now you can use the azcopy tool to copy your disk to azure storage account.

Before copying, generate a SAS token for the Azure Storage account if the container is set to private access level, using the Azure portal.

Portal->Storageaccount-> shared access signature -> check the required fields -> Generate SAS-token.
enter image description here

Command and Output:

PS C:\Users\xxx> azcopy copy "https://md-kzf3q5hrncpd.z2.blob.storage.azure.net/ndjc41wbhvk3/abcd?sv=2018-03-28&sr=b&si=af3a105c-b5f3-43fd-921b-3dc19808d064&sig=redacted" "https://venkat326123.blob.core.windows.net/diskcontainer/?sv=2024-11-04&ss=bfqt&srt=sco&sp=rwdlacupiytfx&se=2025-04-10T14:58:16Z&st=2025-04-10T06:58:16Z&spr=https&sig=redacted" --recursive=true
INFO: Scanning...
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support

Job redacted has started
Log file is located at: C:\Users\xxxx\.azcopy\redacted.log

INFO: Destination could not accommodate the tier P30. Going ahead with the default tier. In case of service to service transfer, consider setting the flag --s2s-preserve-access-tier=false.
100.0 %, 1 Done, 0 Failed, 0 Pending, 0 Skipped, 1 Total, 2-sec Throughput (Mb/s): 0.002


Job redacted summary
Elapsed Time (Minutes): 0.0672
Number of File Transfers: 1
Number of Folder Property Transfers: 0
Number of Symlink Transfers: 0
Total Number of Transfers: 1
Number of File Transfers Completed: 1
Number of Folder Transfers Completed: 0
Number of File Transfers Failed: 0
Number of Folder Transfers Failed: 0
Number of File Transfers Skipped: 0
Number of Folder Transfers Skipped: 0
Total Number of Bytes Transferred: 1099511628288
Final Job Status: Completed

enter image description here

Portal:

enter image description here

If this resolves your issue, please click “up-vote" for it, which could help other community members who read this thread. And, if you have any more questions, please let us know.

Syed Aaqid Ali 580 Reputation points Microsoft External Staff Volunteer Moderator

2025-04-10T20:16:44.0433333+00:00

Thankyou Venkatesan for more step-by-step instructions, Shayne Mei Checking to see whether you have resolved the issue with the solution provided above, or if you need any further assistance, please let us know.

Shayne Mei 20

Thanks for the step-by-step guide. I've followed the instructions and successfully generated the disk export url and this time the command did run, but the job failed. I ran the commands on an azure VM. Here are the logs:

2025/04/10 23:48:09 AzcopyVersion  10.27.1
2025/04/10 23:48:09 OS-Environment  linux
2025/04/10 23:48:09 OS-Architecture  amd64
2025/04/10 23:48:09 Log times are in UTC. Local time is 10 Apr 2025 23:48:09
2025/04/10 23:48:09 ISO 8601 START TIME: to copy files that changed before or after this job started, use the parameter --include-before=2025-04-10T23:48:04Z or --include-after=2025-04-10T23:48:04Z
2025/04/10 23:48:09 ==> REQUEST/RESPONSE (Try=1/5.480856ms, OpTime=22.303796ms) -- RESPONSE SUCCESSFULLY RECEIVED
   GET https://seasaltsttdata.blob.core.windows.net/snapshot-backup?restype=container&se=2025-04-11T07%3A45%3A30Z&sig=-REDACTED-&sp=rwdlacupiytfx&spr=https&srt=sco&ss=bfqt&st=2025-04-10T23%3A45%3A30Z&sv=2024-11-04
   X-Ms-Request-Id: [6604a6bb-b01e-0043-1b73-aa101c000000]
2025/04/10 23:48:09 Any empty folders will not be processed, because source and/or destination doesn't have full folder support
2025/04/10 23:48:09 Job-Command copy https://md-hdd-tgxl40f0pr2l.z23.blob.storage.azure.net/nxxvpzcsggjh/abcd?si=72e35c60-1475-4ba3-801b-49c04e752a49&sig=-REDACTED-&sr=b&sv=2018-03-28 https://seasaltsttdata.blob.core.windows.net/snapshot-backup/?se=2025-04-11t07%3A45%3A30z&sig=-REDACTED-&sp=rwdlacupiytfx&spr=https&srt=sco&ss=bfqt&st=2025-04-10t23%3A45%3A30z&sv=2024-11-04 --recursive=true
2025/04/10 23:48:09 Number of CPUs: 2
2025/04/10 23:48:09 Max file buffer RAM 1.000 GB
2025/04/10 23:48:09 Max concurrent network operations: 32 (Based on number of CPUs. Set AZCOPY_CONCURRENCY_VALUE environment variable to override)
2025/04/10 23:48:09 Check CPU usage when dynamically tuning concurrency: true (Based on hard-coded default. Set AZCOPY_TUNE_TO_CPU environment variable to true or false override)
2025/04/10 23:48:09 Max concurrent transfer initiation routines: 64 (Based on hard-coded default. Set AZCOPY_CONCURRENT_FILES environment variable to override)
2025/04/10 23:48:09 Max enumeration routines: 16 (Based on hard-coded default. Set AZCOPY_CONCURRENT_SCAN environment variable to override)
2025/04/10 23:48:09 Parallelize getting file properties (file.Stat): false (Based on AZCOPY_PARALLEL_STAT_FILES environment variable)
2025/04/10 23:48:09 Max open files when downloading: 1048152 (auto-computed)
2025/04/10 23:48:09 Final job part has been created
2025/04/10 23:48:09 Final job part has been scheduled
2025/04/10 23:48:09 INFO: [P#0-T#0] Transfer: Source "https://md-hdd-tgxl40f0pr2l.z23.blob.storage.azure.net/nxxvpzcsggjh/abcd?si=72e35c60-1475-4ba3-801b-49c04e752a49&sig=-REDACTED-&sr=b&sv=2018-03-28" Destination "https://seasaltsttdata.blob.core.windows.net/snapshot-backup/abcd". Autodetected https://md-hdd-tgxl40f0pr2l.z23.blob.storage.azure.net/nxxvpzcsggjh/abcd blob type as PageBlob.
2025/04/10 23:48:09 INFO: [P#0-T#0] Starting transfer: Source "https://md-hdd-tgxl40f0pr2l.z23.blob.storage.azure.net/nxxvpzcsggjh/abcd" Destination "https://seasaltsttdata.blob.core.windows.net/snapshot-backup/abcd". Specified chunk size 4194304
2025/04/10 23:48:09 ==> REQUEST/RESPONSE (Try=1/3.854961ms, OpTime=16.430671ms) -- RESPONSE STATUS CODE ERROR
   PUT https://seasaltsttdata.blob.core.windows.net/snapshot-backup/abcd?se=2025-04-11T07%3A45%3A30Z&sig=-REDACTED-&sp=rwdlacupiytfx&spr=https&srt=sco&ss=bfqt&st=2025-04-10T23%3A45%3A30Z&sv=2024-11-04
   Accept: application/xml
   Content-Length: 0
   User-Agent: AzCopy/10.27.1 azsdk-go-azblob/v1.4.0 (go1.23.1; linux)
   X-Ms-Client-Request-Id: 1c6b3c8c-5721-4073-7d83-769ee99bf3d2
   x-ms-blob-content-length: 17592186044928
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-sequence-number: 0
   x-ms-blob-type: PageBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 400 The value for one of the HTTP headers is not in the correct format.
   Content-Length: 344
   Content-Type: application/xml
   Date: Thu, 10 Apr 2025 23:48:09 GMT
   Server: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0
   X-Ms-Client-Request-Id: 1c6b3c8c-5721-4073-7d83-769ee99bf3d2
   X-Ms-Error-Code: InvalidHeaderValue
   X-Ms-Request-Id: 84992547-f01e-0100-5473-aa084d000000
   X-Ms-Version: 2023-08-03
Response Details: <Code>InvalidHeaderValue</Code><Message>The value for one of the HTTP headers is not in the correct format. </Message><HeaderName>x-ms-blob-content-length</HeaderName><HeaderValue>17592186044928</HeaderValue>
2025/04/10 23:48:09 ERR: [P#0-T#0] COPYFAILED: https://md-hdd-tgxl40f0pr2l.z23.blob.storage.azure.net/nxxvpzcsggjh/abcd : 400 : 400 The value for one of the HTTP headers is not in the correct format.. When Creating blob. X-Ms-Request-Id: 84992547-f01e-0100-5473-aa084d000000
   Dst: https://seasaltsttdata.blob.core.windows.net/snapshot-backup/abcd
2025/04/10 23:48:10 INFO: [P#0-T#0] Page blob throughput tuner: Target Mbps 4006
2025/04/10 23:48:11 PERF: primary performance constraint is Unknown. States: W: 100001, F:  0, S:  0, E:  0, T: 100001, GRs: 32
2025/04/10 23:48:11 0.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
2025/04/10 23:48:11 INFO: [P#0-T#0] Page blob throughput tuner: Target Mbps 4012
2025/04/10 23:48:12 INFO: [P#0-T#0] Page blob throughput tuner: Target Mbps 4018
2025/04/10 23:48:13 INFO: [P#0-T#0] Page blob throughput tuner: Target Mbps 4024
2025/04/10 23:48:13 PERF: primary performance constraint is Unknown. States: W: 39, F:  0, S:  0, E:  0, T: 39, GRs: 32
2025/04/10 23:48:13 0.0 %, 0 Done, 0 Failed, 1 Pending, 0 Skipped, 1 Total,
2025/04/10 23:48:14 JobID=5284e45d-93a5-1d49-6cd1-d30ababccdc0, Part#=0, TransfersDone=1 of 1
2025/04/10 23:48:14 all parts of entire Job 5284e45d-93a5-1d49-6cd1-d30ababccdc0 successfully completed, cancelled or paused
2025/04/10 23:48:14 is part of Job which 1 total number of parts done
2025/04/10 23:48:15 PERF: primary performance constraint is Unknown. States: W:  0, F:  0, S:  0, E:  0, T:  0, GRs: 32
2025/04/10 23:48:15 0.0 %, 0 Done, 1 Failed, 0 Pending, 0 Skipped, 1 Total,
2025/04/10 23:48:15
Diagnostic stats:
IOPS: 0
End-to-end ms per request: 8
Network Errors: 0.00%
Server Busy: 0.00%
Job 5284e45d-93a5-1d49-6cd1-d30ababccdc0 summary
Elapsed Time (Minutes): 0.1006
Number of File Transfers: 1
Number of Folder Property Transfers: 0
Number of Symlink Transfers: 0
Total Number of Transfers: 1
Number of File Transfers Completed: 0
Number of Folder Transfers Completed: 0
Number of File Transfers Failed: 1
Number of Folder Transfers Failed: 0
Number of File Transfers Skipped: 0
Number of Folder Transfers Skipped: 0
Total Number of Bytes Transferred: 0
Final Job Status: Failed
2025/04/10 23:48:15 Closing Log

Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T03:48:40.28+00:00

Hi Shayne Mei

What is the size of azure disk?
Shayne Mei 20 Reputation points

2025-04-11T03:53:32.0766667+00:00

The disk is 16T
Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T03:58:02.71+00:00
Shayne Mei

According to this MS-Document
You can’t create a page blob larger than 8 TiB. If the original blob really is 16 TiB, it's invalid.

Use the --blob-type BlockBlob parameter explicitly if you're okay copying to a block blob instead:

azcopy copy <source-url> <destination-url> --recursive=true --blob-type BlockBlob
Shayne Mei 20 Reputation points

2025-04-11T05:09:43.9633333+00:00

In that case how do I move data from the disk to a storage account? This is required because we want to use the azure data box service. What are our other options here?
Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T05:14:05.3+00:00

@Shayne Mei

Have you tried the above command with BlockBlob type to store the vhd file?
Shayne Mei 20 Reputation points

2025-04-11T05:35:52.98+00:00

Does this affect the eligibility to utilise the azure data box service for data import/export?
Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T07:25:23.8433333+00:00

Refer this https://learn.microsoft.com/en-us/azure/databox/data-box-disk-limits regarding of azure data box limitation.
Shayne Mei 20 Reputation points

2025-04-11T07:59:45.1133333+00:00

I saw that the block blob has a max size of 7TB? Does azcopy create multiple blobs?
Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T08:44:55.97+00:00

@Shayne Mei

Are you asking azcopy split large files into multiple blobs?
Shayne Mei 20 Reputation points

2025-04-14T22:35:52.7233333+00:00

Thank you Venkatesan, BlockBlob type worked! I am also able to directly copy the snapshots instead of having to create a managed disk first.

Accepted answer

0 additional answers

Your answer

Syed Aaqid Ali 580 Reputation points Microsoft External Staff Volunteer Moderator

2025-04-08T20:06:17.9633333+00:00

Hello Shayne Mei,

To move data from a managed disk to an Azure storage account, you can use the Azure CLI. Here are the general steps:

Launch Azure Cloud Shell: Open the Azure Cloud Shell, which has the necessary tools preinstalled. You can do this by selecting Try it from the upper right corner of a code block or by navigating to the Cloud Shell in your browser by going to https://shell.azure.com.

Sign in to Azure: If you need to use a different subscription, you can sign in using the following command, replacing subscriptionId with your Azure subscription ID:

subscription="subscriptionId" # Set Azure subscription ID here az account set -s $subscription # ...or use 'az login'

Run the script: You can then run the appropriate script to copy the managed disk to the storage account. The specific commands will depend on whether you are copying a snapshot or a managed disk directly.

Clean up resources: After the operation, you may want to clean up resources by deleting the resource group or any related resources using:

az group delete --name myResourceGroupName

Make sure to check the prerequisites and ensure that you have the necessary permissions and configurations set up in your Azure environment.

References:

Export/Copy a managed disk to a storage account using the Azure CLI

Copy snapshot of a managed disk to same or different subscription with CLI

Prerequisites

Please do not forget to “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

If you have any other questions or are still running into more issues, let me know in the "comments" and I would be happy to help you.
Shayne Mei 20 Reputation points

2025-04-08T20:11:42.9633333+00:00

I did try az storage blob copybut it complained that the snapshot size is too big (16G snapshot). I did some research and found azcopy handles the chunking natively, but I'm having trouble running azcopy.
Syed Aaqid Ali 580 Reputation points Microsoft External Staff Volunteer Moderator

2025-04-09T16:09:41.99+00:00

Hi Shayne Mei, checking to see if the solution proposed helped (pointed you in the right direction) > please do not forget to “up-vote”. which might be beneficial to other community members reading this thread. And, if you have any further queries do let us know.
Shayne Mei 20 Reputation points

2025-04-09T20:14:25.5433333+00:00

Unfortunately it did not work. I get the exact same error failed to perform copy command due to error: cannot start job due to error: failed to scan path

This is the command i used:
azcopy copy '<path-to-file-on-azure-disk>' 'https://<storage-account>.blob.core.windows.net/<container>/<blob>/?<SAS>' --recursive=true

I have also verified that the file path exists, the file permission is also correctly set.

Interestingly, I tried running on another random file on the azure vm home path (not on the mounted managed disk I want to move) , and it worked. So it seems like there's something wrong with azcopy accessing the mounted disk? But I can't figure out what might be wrong since I can access everything on that mounted disk just fine.

Another thought, is there a way to run azcopy from the azure cloud shell to move a snapshot directly so we can circumvent the mounted disk issue?
Syed Aaqid Ali 580 Reputation points Microsoft External Staff Volunteer Moderator

2025-04-10T20:16:44.0433333+00:00

Thankyou Venkatesan for more step-by-step instructions, Shayne Mei Checking to see whether you have resolved the issue with the solution provided above, or if you need any further assistance, please let us know.
Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T03:48:40.28+00:00

Hi Shayne Mei

What is the size of azure disk?
Shayne Mei 20 Reputation points

2025-04-11T03:53:32.0766667+00:00

The disk is 16T
Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T03:58:02.71+00:00

Shayne Mei

According to this MS-Document
You can’t create a page blob larger than 8 TiB. If the original blob really is 16 TiB, it's invalid.

Use the --blob-type BlockBlob parameter explicitly if you're okay copying to a block blob instead:

azcopy copy <source-url> <destination-url> --recursive=true --blob-type BlockBlob
Shayne Mei 20 Reputation points

2025-04-11T05:09:43.9633333+00:00

In that case how do I move data from the disk to a storage account? This is required because we want to use the azure data box service. What are our other options here?
Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T05:14:05.3+00:00

@Shayne Mei

Have you tried the above command with BlockBlob type to store the vhd file?
Shayne Mei 20 Reputation points

2025-04-11T05:35:52.98+00:00

Does this affect the eligibility to utilise the azure data box service for data import/export?
Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T07:25:23.8433333+00:00

Refer this https://learn.microsoft.com/en-us/azure/databox/data-box-disk-limits regarding of azure data box limitation.
Shayne Mei 20 Reputation points

2025-04-11T07:59:45.1133333+00:00

I saw that the block blob has a max size of 7TB? Does azcopy create multiple blobs?
Venkatesan S 2,820 Reputation points Microsoft External Staff Moderator

2025-04-11T08:44:55.97+00:00

@Shayne Mei

Are you asking azcopy split large files into multiple blobs?
Shayne Mei 20 Reputation points

2025-04-14T22:35:52.7233333+00:00

Thank you Venkatesan, BlockBlob type worked! I am also able to directly copy the snapshots instead of having to create a managed disk first.

Answer 1

Hi Shayne Mei

As per discussion in comments, Posting as answer.

According to this MS-Document, you can’t create a page blob larger than 8 TiB.

If you need to copy a 16 TiB blob, you can explicitly use the -=Blob-type BlockBlob parameter, provided you're okay with copying it as a block blob.

Command:

azcopy copy <source-url+?SAS token> <destination-url+?SAS token> --recursive=true --blob-type BlockBlob

The above command will directly copy the snapshots to your Azure Storage account.

Hope this answer helps! please let us know if you have any further queries. I’m happy to assist you further.

Please do not forget to "Accept the answer” and "Yes" for was this answer helpful. this can be beneficial to other community members.

Share via

How to move data from a snapshot/managed disk to an Azure storage account?

0 additional answers

Your answer