Samba Backup: Create and store backups on a Samba share

[ovizii]

Sorted with a complete reboot of the OS, not just restart of HA. Seems HA had a hiccup somewhere thinking it was offline. Meanwhile, I was remotely connected to it from a different country and was struggling with this nonsense.

[mauriceatkinson]

Update…
the last 14 daily backups using samba backup where not able to restore. I tried using the HA onboard process and also creating an HA instance and restoring from systems/backup. Nothing worked.

To resolve I fortunatly had the orginal HA vm so I removed samba backup and used HA to create a backup and this restored OK.

Samba backup is now coming nowhere near my system. I run a fairly vanilla version of HA so cannot understand why it didnt restor. I would caution using this without testing your restore files actually work

[KonradJA (Konrad Alder)]

Hi!
I’m getting the following error in Samba Backup Protocol:
Failed to get 15d21743_samba_backup logs, e.callApiRaw is not a function
No protocol is displayed.

Home Assinstant:

• Core: 2024.10.4
• Supervisor: 2024.11.2
• Operating System: 13.2
• Frontend: 20241002.4

I am running HA on a synology NAS.
Thanks and kind regards

[jackjourneyman (Jack)]

Me too. Same error when I try to access add-on logs. Started after upgrading to Supervisor 2024.11.2 (no, really, it did…)

Edit: Also, the upgrade doesn’t seem to have created a backup as it should have done, so I’m a bit stuck…

[makai]

HA 2024.11 is needed to get logs again

[broder]

On my Proxmox Install it seems that this Addin is also responsible for a slow but permanent increase in Memory Usage. Usually I start at around 4GB of Ram. Then after the Backup ran it increased to 9 GB. Then the next night ended up with 16 GB.
This is reproducable in my environment. 2024.11.0 Core with 2024.11.2 Supervisor on Proxmox 8.2.0; HA as virtual machine NOT LXC.

A real pitty, I liked this Addon. Since I disabled it all is fine

[HerbertTestmann]

Hello

1. Backup files are created, but there are error messages in the log file.

2. and the second problem: the backup files are in the share and not in the subfolder specified in the target directory.

does anyone have any ideas

-----------------------------------------------------------
 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 13.2  (amd64 / qemux86-64)
 Home Assistant Core: 2024.11.3
 Home Assistant Supervisor: 2024.11.4
-----------------------------------------------------------
 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
Log level is set to INFO
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-11-22 19:35:16] INFO: ---------------------------------------------------
[24-11-22 19:35:16] INFO: Host/Share: 192.168.1.224/HA_backup
[24-11-22 19:35:16] INFO: Target directory: sambaauto
[24-11-22 19:35:16] INFO: Keep local/remote: all/30
[24-11-22 19:35:16] INFO: Trigger time: 04:44
[24-11-22 19:35:16] INFO: Trigger days: Tue Thu Sun
[24-11-22 19:35:16] INFO: ---------------------------------------------------
[24-11-22 19:35:18] INFO: Samba Backup started successfully
[24-11-22 19:35:45] INFO: Backup running ...
[24-11-22 19:35:45] INFO: Creating backup "Samba Backup 2024-11-22 19:35"
[24-11-22 19:36:44] INFO: Copying backup 446dc45f (Samba_Backup_2024_11_22_19_35.tar) to share
[24-11-22 19:36:44] WARNING: 446dc45f.tar does not exist
[24-11-22 19:36:44] WARNING: Could not copy backup 446dc45f to share. Trying again ...
[24-11-22 19:36:49] WARNING: 446dc45f.tar does not exist
[24-11-22 19:37:00] INFO: Backup finished

[rerpires (Rui)]

Yeap that was it ! thanks ! solved the issue. Full backup every single night.

Thank you !

[Lars6503]

Suggestion.
When I’m making a full backup it fails due to that I have 60% full disk. This is because the backup is made on the disk and then copied to the sambashare and then deleted on the disk.
An option that would make the backup directly on the sambashare would not fail and a copy and delete wouldn’t be necessary.
Thanks.

[YoshY]

Bonjour, j’ai un problème depuis quelques temps, impossible d’effectuer la sauvegarde sur mon NAS, alors que tout fonctionnait correctement
Voici la configuration YAML de l’addon :

Hello, I have had a problem for some time, it is impossible to make the backup on my NAS, while everything was working correctly
Here is the YAML configuration of the addon:

host: 192.168.1.20
share: Backups
target_dir: HomeAssistant
username: **************
password: **************
keep_local: "7"
keep_remote: "30"
trigger_time: "23:00"
trigger_days:
  - Mon
  - Tue
  - Wed
  - Thu
  - Fri
  - Sat
  - Sun
exclude_addons: []
exclude_folders: []
log_level: debug

Voici le log (debug)
here is the log (debug) :

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 14.0 (aarch64 / raspberrypi5-64)
Home Assistant Core: 2024.12.1
Home Assistant Supervisor: 2024.11.4
.-----------------------------------------------------------
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
Log level is set to DEBUG
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-12-10 10:47:09] INFO: ---------------------------------------------------
[24-12-10 10:47:09] INFO: Host/Share: 192.168.1.20/Backups
[24-12-10 10:47:09] INFO: Target directory: HomeAssistant
[24-12-10 10:47:09] INFO: Keep local/remote: 7/30
[24-12-10 10:47:09] INFO: Trigger time: 23:00
[24-12-10 10:47:09] INFO: Trigger days: Mon Tue Wed Thu Fri Sat Sun
[24-12-10 10:47:09] INFO: ---------------------------------------------------
[24-12-10 10:47:09] DEBUG: Backups local/remote: 58/30
[24-12-10 10:47:09] DEBUG: Total backups succeeded/failed: 292/43
[24-12-10 10:47:09] DEBUG: Last backup: 2024-10-21 23:00
[24-12-10 10:47:30] WARNING: protocol negotiation failed: NT_STATUS_IO_TIMEOUT
[24-12-10 10:47:30] FATAL: Target directory does not exist. Please check your config.
[24-12-10 10:47:30] DEBUG: Posting sensor data to API at /core/api/states/sensor.samba_backup
[24-12-10 10:47:30] DEBUG: API Status: 200
[24-12-10 10:47:30] DEBUG: API Response: {“entity_id”:“sensor.samba_backup”,“state”:“FAILED”,“attributes”:{“friendly_name”:“Samba Backup”,“backups_local”:“58”,“backups_remote”:“30”,“total_backups_succeeded”:“292”,“total_backups_failed”:“43”,“last_backup”:“2024-10-21 23:00”},“last_changed”:“2024-12-10T09:39:35.138675+00:00”,“last_reported”:“2024-12-10T09:39:35.138675+00:00”,“last_updated”:“2024-12-10T09:39:35.138675+00:00”,“context”:{“id”:“01JEQZ0D329Z9KDYSEV7KFW443”,“parent_id”:null,“user_id”:“97be99298795434ca1acd9e0e2e166f6”}}
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

j’ai acces au NAS depuis la section Stockage de Home assistant :
I have access to the NAS from the Storage section of Home assistant:

j’arrive aussi a faire une sauvegarde manuelle vers le NAS :
I can also do a manual backup to the NAS:

J’ai accès au nas depuis mes autres appareils comme mon pc qui est sauvegardé tous les jours.
Merci pour votre aide et bonne journée.

I have access to the NAS from my other devices like my PC which are backed up every day.
Thank you for your help and have a nice day.

[Mikethehobbit (MK)]

Hallo Thomas,
im struggling to get it work (correctly). Latest version but I got this WARNING:
[24-12-30 22:00:23] INFO: Backup running …
[24-12-30 22:00:25] INFO: Creating backup “Samba Backup 2024-12-30 22:00”
[24-12-30 22:00:45] INFO: Copying backup 71a3ef34 (Samba_Backup_2024_12_30_22_00.tar) to share
[24-12-30 22:00:46] WARNING: 71a3ef34.tar does not exist
[24-12-30 22:00:46] WARNING: Could not copy backup 71a3ef34 to share. Trying again …
[24-12-30 22:00:51] WARNING: 71a3ef34.tar does not exist
[24-12-30 22:01:02] INFO: Backup finished

I looked through your documentation, but cant find why the file name change to “71a3ef34” which is quite logic to me that it cant be copied. The file “Samba Backup 2024-12-30 22:00” is there as expected (so the BackUp worked :-)) at least I have a backup automation…
Any Idea why the file cant be found or why it change the name?
Is it failure 42 or Im missing something?

[tmo]

Same here:

[25-01-04 23:32:15] INFO: Samba Backup started successfully
[25-01-04 23:33:15] INFO: Backup running ...
[25-01-04 23:33:16] INFO: Creating backup "Partial Backup 2025.1.0 2025-01-04 23:33"
[25-01-04 23:33:41] INFO: Copying backup 0eebd5c4 (Samba_Backup_Partial_Backup_2025_1_0_2025_01_04_23_33.tar) to share
[25-01-04 23:33:41] WARNING: 0eebd5c4.tar does not exist
[25-01-04 23:33:41] WARNING: Could not copy backup 0eebd5c4 to share. Trying again ...
[25-01-04 23:33:46] WARNING: 0eebd5c4.tar does not exist
[25-01-04 23:33:56] INFO: Backup finished

However, 0eebd5c4.tar can later be found on the samba drive, i.e. the backup was successful.

[saxos]

The 2025.1 release has now a much more sophisticated built-in backup mechanism, including saving a backup to a Samba share.

Have a look here

[makai]

I don’t think so. With built-in backup you can’t choose different retention periods per location, you can’t change when the backup is done (4h45 only and every day or one time per week only), you can’t fine tune what to backup and it is encrypted with no easy way to decrypt backups… but it’s a start

[loic69]

I don’t think so
Built in backup in 2025.1 is so light.
We can choose only 1 auto backup and transfer it to samba share, Nabucasa cloud, choose very simple retention,…
I prefer continue using auto backup which is really finer

[nibotg]

I’m looking for any guidance please, it looks like this addon stopped working for me on 20 December 2024:

{
  "state": "FAILED",
  "attributes": {
    "friendly_name": "Samba Backup",
    "backups_local": "10",
    "backups_remote": "10",
    "total_backups_succeeded": "193",
    "total_backups_failed": "26",
    "last_backup": "2024-12-19 04:32"
  }
}

I’m running it on a Proxmox host but under HASOS:

 Add-on version: 5.2.0
 You are running the latest version of this add-on.
 System: Home Assistant OS 14.1  (amd64 / qemux86-64)
 Home Assistant Core: 2024.12.5
 Home Assistant Supervisor: 2024.12.

And I’m seeing this error in the logs:

[25-01-09 17:01:26] WARNING: Error relocating /usr/lib/libgmp.so.10: __gmpn_toom42_mulmid__gmpn_mulmid_n: symbol not found

[25-01-09 17:01:26] FATAL: Cannot access share. Unknown reason.

I’ve tried creating a new share and pointing the backup to that but it made no difference so any help appreciated please. Thanks.