Can't create new snapshot (Response code 400 (Bad Request)) about hassio-nextcloud-backup

[nicknol]

it seems to be related to the backup functionality.
The supervisor log shows:

24-02-28 19:29:00 ERROR (MainThread) [supervisor.backups.manager] Backup 25b7e633 error
Traceback (most recent call last):
  File "/usr/src/supervisor/supervisor/backups/manager.py", line 261, in dobackup
    async with backup:
  File "/usr/src/supervisor/supervisor/backups/backup.py", line 363, in __aexit
    self.outersecuretarfile.exit(
  File "/usr/local/lib/python3.12/site-packages/securetar/_init.py", line 140, in __exit
    self._tar.close()
  File "/usr/local/lib/python3.12/tarfile.py", line 1975, in close
    self.fileobj.close()
OSError: [Errno 5] I/O error

[sanchosk]

Same thing here. @nicknol did you have any luck? I guess the problem is the file for backup is above 2GB...

[sanchosk]

@nicknol I think I know where the problem is.
I recently moved my backup location from local data disk to remote NFS.
This seems to be the problem - with NFS, the NC backup does not work.
If I switch the default backup back to local device, the NC backup works again.
Can you, plz, check if you also have default backup location switched to some remote drive? (SMB/NFS)

[nicknol]

@sanchosk
yes, the backup itself fails if it is supposed to be created on a NAS and is big:

• a small backup (~500MB) could be created locally and on the NAS
• a big(ger) backup (~3GB) could be created locally but not on the NAS

I could create big backups on the NAS in 2023, means using HA 2023.12. I can't remember exactly whether it stopped working with 2024.1 or 2024.2
Writing about it, I think I remember a comment about an improvement/change to handling tar in one of the recent releases. ... have to dig for it
Found it, it was about HASS OS 12: https://www.home-assistant.io/blog/2024/02/26/home-assistant-os-12-support-for-raspberry-pi-5/

[Sebclem]

Can you confirm that this is not related to this addon ?

[sanchosk]

I am not sure, cannot confirm nor deny. What I can say is that when the backup location is set to local, the addon works as expected, when the backup location is shared drive, it does not.
At the same time, the shared drive has no problem to create backups of 2+GB.
So, can't tell "where is the ball", but I know that the combination of the addon and external drive for backup renders the addon defective.

[Sebclem]

This could be linked to the location api param, but it's strange because this should fallback to the default setting....