jak119 / hassio-backup-azure-blob Goto Github PK

Hitting some isses when trying to copy new files to Azure blob:
`22:40:17] INFO: === Starting copy ===
ERROR: The specified blob already exists.
RequestId:f9301787-901e-0019-47fc-4a1a99000000
Time:2023-02-27T22:41:21.6601902Z
ErrorCode:BlobAlreadyExists
If you want to overwrite the existing one, please add --overwrite in your command.'

Backup to Azure Blob
Current version: 1.1.4

Hi,

I can't push my backup on azure blob. Connection string and container name are ok but :
7500dd72.tar
96845faf.tar
=== Starting copy ===
ERROR: Client-Request-ID=b97ef5a2-b25a-11eb-974c-0242ac1e2105 Retry policy did not allow for a retry: , HTTP status code=Unknown, Exception=('Connection aborted.', timeout('The write operation timed out')).
ERROR: ('Connection aborted.', timeout('The write operation timed out'))
ERROR: Client-Request-ID=b9816e04-b25a-11eb-a890-0242ac1e2105 Retry policy did not allow for a retry: , HTTP status code=Unknown, Exception=('Connection aborted.', timeout('The write operation timed out')).
ERROR: Client-Request-ID=0a4546eb-b25b-11eb-9731-0242ac1e2105 Retry policy did not allow for a retry: , HTTP status code=Unknown, Exception=('Connection aborted.', timeout('The write operation timed out')).
ERROR: Client-Request-ID=0ef4bf79-b25b-11eb-8fac-0242ac1e2105 Retry policy did not allow for a retry: , HTTP status code=Unknown, Exception=('Connection aborted.', timeout('The write operation timed out')).

I can see put blob activity so i think my configuration is ok

any idea ?

After installation and basic configuration I'm unable to start the addon.
Only one error in log:

s6-overlay-suexec: fatal: can only run as pid 1

First of all, thanks a ton for the Addon!! Awesome work!

For long term usability, I'd like to use a service principal and client secret to authenticate azcopy.

Currently the SAS token generator only supports SAS token validity upto 7 days.

Also, using Azure Active Directory (Service Principal) is recommended over SAS token in general.

Possible Implementation:

# config.yaml
tenant_id: [TENANT-ID]
storage_url: https://[account].blob.core.windows.net/[container]/[path/to/virtual/dir]
principal_id: [PRINCIPAL-ID]
client_secret: [!secret]
delete: false

According to azcopy login documentation: we can use the cmd below to login with service principal and secret:

# Export AZCOPY_SPA_CLIENT_SECRET with the secret, then run
azcopy login --service-principal --application-id <your service principal's application ID>

To help with reviewing logs, output the current date at the start of the script