= Azure/BackupBlob =
 * Azure storage
   1. Storage account with public url
   2. Containers in storage account
   3. Blob (Binary Large OBj)
     1. Blob block 4TiB obj (Hot, Cold, Arch)
     1. Blob page 8TiB disk (Hot, Cold)
     1. Blob Append

 * VM backup to Block blob Archive 
   * https://azurealan.ie/2022/01/31/how-to-save-your-old-virtual-machines-to-low-cost-archive-storage/

== Cost effective long term storage ==
 * Problem: 2922 Azure Recovery Services does not support moving backups to archive tier (Azure limitation)
    * [[https://learn.microsoft.com/en-us/answers/questions/671368/can-i-move-data-backed-up-by-azure-backup-agent-to.html|Ref]]
 * Goal: Move one copy from "Azure Recovery Services" to BlocBlob(Archive) 10x saving.
 * Steps:
   1. Copy disks to .vhd images
   2. Upload to Azure Block blob(Archive)
   3. Delete Azure Recovery copies.

== Fast in cloud VM disk move to blob ==
 * This also works if the blob is in a different tenanat, does depend on having the AccessKey to the blob

 1. Create container in Blob where we can upload data to.
    * Create Blob SAS {{{
export AZURE_STORAGE_KEY="zC....3A=="
export AZURE_STORAGE_ACCOUNT_NAME="<account>". # + ".blob.core.windows.net"
export AZURE_STORAGE_CONTAINER="us-remote-vms"
az storage container create --name ${AZURE_STORAGE_CONTAINER} --account-name ${AZURE_STORAGE_ACCOUNT_NAME}
az storage container generate-sas --account-name ${AZURE_STORAGE_ACCOUNT_NAME} --expiry 2024-04-10 --name ${AZURE_STORAGE_CONTAINER} --permissions dlrw --account-key "${AZURE_STORAGE_KEY}"
}}}

 2. Create a SAS token that has access to the new container that we can append to url's for upload authorization
 3. Stop VM and get Export url for each disk
 4. Use azcopy $SRC $DST , to upload the disk url to the blob url+sas
    * Ran into bug where azcopy 10.24.0 would just get stuck at 0% for BlobPage, fixed by using older version [[https://azcopyvnext.azureedge.net/release20230530/azcopy_windows_amd64_10.19.0.zip|10.19.0]]