Azure Blob "versioning" with suffix on archive tier

hello all, attempting to do a copy to azure blob store - a newer version of a file that's already on archive tier. I know that archive tier files must be deleted to overwrite - however (it's been a while since I used it) wouldn't something like

--suffix 04-04-2022 --suffix-keep-extension

create a new copy with 04-04-2022 and same extension ? it's been a long while since I used the suffix stuff

EDIT: looking at the docs again I guess this is supposed to move the older version to --backup-dir ? (which I did not specify) and something that archive tier can't do - anybody come up with a way to do this with azure blobs ?

thanks

rclone v1.58.0

  • os/version: Microsoft Windows Server 2019 Standard 1809 (64 bit)
  • os/kernel: 10.0.17763.2300 (x86_64)
  • os/type: windows
  • os/arch: amd64
  • go/version: go1.17.8
  • go/linking: dynamic
  • go/tags: cmount

022-04-04 23:58:10 ERROR : git-log5.txt: Failed to copy: -> github.com/Azure/azure-storage-blob-go/azblob.newStorageError, github.com/Azure/azure-storage-blob-go@v0.14.0/azblob/zc_storage_error.go:42
===== RESPONSE ERROR (ServiceCode=BlobArchived) =====
Description=This operation is not permitted on an archived blob.
RequestId:6d795cbf-201e-001d-2da1-48fd3a000000
Time:2022-04-05T03:58:10.5702900Z, Details:
Code: BlobArchived
PUT https://rclonearchivetest.blob.core.windows.net/XXXXXX?timeout=31536001
Authorization: REDACTED
User-Agent: [rclone/v1.58.0]
X-Ms-Client-Request-Id: [41a23766-2573-42a8-583a-cb0560e3ee8b]
X-Ms-Copy-Source: [XXXX]
X-Ms-Date: [Tue, 05 Apr 2022 03:58:10 GMT]
X-Ms-Version: [2020-04-08]

RESPONSE Status: 409 This operation is not permitted on an archived blob.
Content-Length: [233]
Content-Type: [application/xml]
Date: [Tue, 05 Apr 2022 03:58:10 GMT]
Server: [Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0]
X-Ms-Client-Request-Id: [41a23766-2573-42a8-583a-cb0560e3ee8b]
X-Ms-Error-Code: [BlobArchived]
X-Ms-Request-Id: [6d795cbf-201e-001d-2da1-48fd3a000000]
X-Ms-Version: [2020-04-08]

hello,

--suffix can be used without --backup-dir

with a file with aws s3 glacier storage class, cannot copy/move the file
first need to restore the file to standard storage class, then can copy/move/etc...
and based on the rclone docs, looks the same behavior for azure.

if you need more help, then run a command that tries to copy a single file and post the full debug log.

debug log confirms this, I guess the question is - is there a method to have the newer file take the suffix or something comparable to avoid this scenario ? or perhaps it's a feature request?

Depending in what you aim to achieve, one alternative approach could be to enable versioning on the blobs in azure and allow rclone to overwrite them (ie delete first).

Can’t enable versioning on archive tier - have to delete - basically thinking about the LATEST version have a suffix - basically rclone knows enough to compare files with archive tier because of it’s metadata

Basically - if archive upload with suffix or something

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.