I had installed SAMBA-Backup nearly 4 month ago, the local full backups were scheduled and stored on my HA-server (NUC) and a copy on my Synology NAS. Both worked really fine and smart. So I could sleep well, knowing that I will be able to restore it in case of emergency and it worked once during my project for enlarging my SSD in the NUC.
The details for installation see below.
But unfortunately there was a break 3 weeks ago. I found that the local backups are done well, but the copy on the Synology NAS has a smaller size and I got some feedback by protocol. But I am not able to analyze the content and meaning of the protocol and I do not find the root cause for the not working on my Synology NAS.
The size of the full backup stored local is around 2.1 GB, but on NAS it varies from 500 MB to 2.1 GB for the same files. Is’nt it strange?
Details from SAMBA BACKUP protocol:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/00-banner.sh
-----------------------------------------------------------
Add-on: Samba Backup
Create backups and store them on a Samba share
-----------------------------------------------------------
Add-on version: 5.2.0
You are running the latest version of this add-on.
System: Home Assistant OS 12.1 (amd64 / generic-x86-64)
Home Assistant Core: 2024.4.1
Home Assistant Supervisor: 2024.03.1
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
cont-init: info: /etc/cont-init.d/00-banner.sh exited 0
cont-init: info: running /etc/cont-init.d/01-log-level.sh
cont-init: info: /etc/cont-init.d/01-log-level.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[24-04-06 00:56:14] INFO: ---------------------------------------------------
[24-04-06 00:56:14] INFO: Host/Share: 192.168.178.203/HA-Backups
[24-04-06 00:56:14] INFO: Target directory:
[24-04-06 00:56:14] INFO: Keep local/remote: 10/15
[24-04-06 00:56:14] INFO: Trigger time: 02:00
[24-04-06 00:56:14] INFO: Trigger days: Mon Tue Wed Thu Fri Sat Sun
[24-04-06 00:56:14] INFO: ---------------------------------------------------
[24-04-06 00:56:15] INFO: Samba Backup started successfully
[24-04-06 02:00:16] INFO: Backup running ...
[24-04-06 02:00:16] INFO: Creating backup "Samba Backup 2024-04-06 02:00"
[24-04-06 02:01:13] INFO: Copying backup 533c1c38 (Samba_Backup_2024_04_06_02_00.tar) to share
[24-04-06 02:10:25] WARNING: cli_push returned NT_STATUS_IO_TIMEOUT
NT_STATUS_IO_TIMEOUT closing remote file \Samba_Backup_2024_04_06_02_00.tar
[24-04-06 02:10:25] WARNING: Could not copy backup 533c1c38 to share. Trying again ...
[24-04-06 02:24:32] WARNING: cli_push returned NT_STATUS_IO_TIMEOUT
NT_STATUS_IO_TIMEOUT closing remote file \Samba_Backup_2024_04_06_02_00.tar
[24-04-06 02:24:43] INFO: Backup finished
Thanks in advance for your support.
BR
Thomas