The key difference is that a copy operation avoids the early deletion fee that is assessed if you change the tier of a blob from the Archive tier before the required 180-day period elapses.
It also prevents the blob from potentially moving back due to lifecycle policies. Its supported between different storage accounts, on same regions. -and for the same storage account.
I'm not sure how to accomplish this with rclone as a copy from the archive is rejected as explained in the documentation. Setting the tier will rehydrate with fees.
Attempting to copy the blob from an archived backend to an online backend does not work. Currently I use the az tool to initiate the copy, but it would be optimal to do it with rclone.
- os/version: arch (64 bit)
- os/kernel: 6.1.53-1-lts (x86_64)
- os/type: linux
- os/arch: amd64
- go/version: go1.20.6
- go/linking: dynamic
- go/tags: none
Thanks in advance