Feb 27 2019 10:15 AM
Feb 27 2019 10:15 AM
I have a disk with some files (About 1 TB) that will probably never be needed. However they might be needed so I have to keep them somewhere. I thought that the archive storage tier would be the perfect place.
My plan was to detach the VHD from the VM and change the storage tier from hot to archive. If I ever needed the data again I would change from archive back to hot and attach the VHD to a VM. However, after detaching the disk, when I tried to change the tier I got the message "Changing the access tier is only allowed on block blobs that do not have snapshots in an active state." I then realized that the VHD is a page blob and it appears you can't change the tier on a page blob.
I can't be the only one who wants to archive a drive (Or an entire VM) so I suspect I am missing a simple solution.
Feb 28 2019 10:41 AM
I'm spit balling here, but have you considered using AZcopy? You can use it transfer data to/from different storage types.
You can set up another Azure storage account and copy the data from your page blob to a drive you can store cold.
Feb 28 2019 10:53 AM
I had read somewhere that with azcopy if it came from a page blob the new copy would still be a page blob and that there wasn't a switch in azcopy to change from page to block blob or vice versa.
However, I didn't verify that so I may have to test it
Feb 28 2019 11:32 AM
It may be possible to perform the following using AZcopy v10:
...you can sync a Blob container down to a local file system:
# If you're using Azure Active Directory authentication the sastoken is not required .\azcopy sync "https://account.blob.core.windows.net/mycontainer1" "C:\local\path" --recursive=true
Mar 04 2019 09:59 AM
Good suggestion but that didn't work.
The Azcopy documentation says "AzCopy v10 by default uploads data into block blobs. However, if a source file has vhd extension, AzCopy v10 will by default upload it to a page blob."
The documentation doesn't seem to be correct. I removed the vhd extension and used Azcopy but it kept it as a page blob.
May 01 2019 02:46 PM
Not really a good one. I thought the best thing to do was to copy the files to a container in a storage account in Azure and then change the container to the archive tier. It is not as simple a process as I wanted. There are more steps and more chances for error.
I have been on vacation so I haven't moved our archive yet. We are still using our normal backup process.
Sep 26 2019 11:40 AM
This is how I have implemented a similar scenario.
Copy vhd file from one subscription to another and in the destination subscription the vhd file must be placed in the archive tier.
- VHD file is supposed to be page blob.
- Archive tier is supported for block blobs (page blob cannot be changed to Archive tier) and at the object level only.
- We want to Archive the vhd file in the destination subscription, so we have to copy the vhd file as block blob and then change the tier to Archive.
- However in case we ever need to restore the vhd file which was copied as block blob, we have to convert the vhd file back to page blob first and then mount it as a disk (because we cannot mount a vhd file block blob as a disk to a VM).
1) First I have copied the vhd file from source subscription to destination subscription as block blob (parameter --blob-type=blockblob) with AzCopy v10.
For details on how to manage the Azure Blob storage lifecycle check this:
3) In case we need to restore the vhd file which was copied as block blob, these are the steps:
- Change the tier from Archive to Hot for example.
- Convert the vhd file back to page blob with below command (parameter --blob-type=pageblob).
- Mount it as a disk to a VM.
azcopy copy "https://<source-storage-account-name>.blob.core.windows.net/<container-name>/<blob-path>?<source-storage-account-SAS-token>" "https://<destination-storage-account-name>.blob.core.windows.net/<container-name>/<blob-path>?<destination-storage-account-SAS-token>" --blob-type=pageblob
Sep 27 2019 07:57 PM
When rehydrating a blob from archive tier to the hot or cool tier, how will I know when rehydration is complete?
During rehydration, you may use the get blob properties operation to poll the Archive Status attribute to confirm when the tier change is complete. The status reads "rehydrate-pending-to-hot" or "rehydrate-pending-to-cool" depending on the destination tier. Upon completion, the archive status property is removed, and the Access Tier blob property reflects the new hot or cool tier.