New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sync cannot overwrite files if they are archived already #1688
Comments
Hi @SzabKel ! I am unable to reproduce your issue. Could you please run your command with --log-level=DEBUG and share with us the logs? |
Hello @siminsavani-msft ! I used the newest version (10.14.0) for this, my command: Logs for one file that failed:
|
Hi @SzabKel ! I was able to repro your issues successfully! Thank you for sharing the logs. Unfortunately, archived blobs cannot be read or modified unless it is rehydrated (https://docs.microsoft.com/en-us/azure/storage/blobs/archive-blob?tabs=azure-portal) which is why your file is failing to overwrite. I would recommend rehydrating the blobs in question, if possible! Let me know if you have any questions! |
@siminsavani-msft Thank you for trying this out. You mention the same thing I referred to when posting the issue. I knew azure storage does not allow overwrite for existing archived blobs. That is why I asked for an option to allow deleting the file before upload in such a case (maybe it could even work by waiting for this server response and do it then?). Because you can delete an archive tier file (for an extra fee though) and upload the new version again. |
@SzabKel This is a really good suggestion! I will bring this up to the team and inform them of this. Thank you! |
@siminsavani-msft Any update on this? |
Hi @SzabKel ! Not at the moment, sorry :( I will update this thread when we pick it up. Thanks for your patience! |
following |
@siminsavani-msft I tried it out with the newest version (v10.18.1) and the issue still persist. Can't force a file delete or rehydrate when syncing. I manually have to delete the files looking at the logs. |
Hi there! Sorry for the inconvenience! We have not been able to pick this up yet. I will make sure to update this thread accordingly when we are able to pick it up. |
Is there atleast a way to ignore archived files when copying? |
I am using azcopy to backup a file share to blob storage. The files rarely change and are archived immediately after being uploaded by a lifecycle rule.
Which version of the AzCopy was used? AzCopy 10.13.0
Which platform are you using? (ex: Windows, Mac, Linux)
Windows
What command did you run?
sync "D:..\Share" "https://......blob.core.windows.net/...." --recursive=true --delete-destination=true
What problem was encountered?
409 This operation is not permitted on an archived blob.. When Uploading blob.
How can we reproduce the problem in the simplest way?
Previous issue: #993
Have you found a mitigation/solution?
Yes. There should be a flag (something like "--allow-delete-before") to allow deletion of the file before uploading the new version. A delete and a new upload should work according to the docs.
Similarly to this: rclone/rclone#4819
The text was updated successfully, but these errors were encountered: