I guess you have to use the same name pattern for the default backups. They have to start with Samba_Backup_
Unfortunately, we can’t control the name pattern of the default backups. Home Assistant assign one by default, such as ‘core_2022.2.0’ or ‘addon_xxxx_yyyy’ or even ‘os_6.6’.
So, here it comes. The german video including node red automation for Backups on not 24/7 available samba shares.
Lokale Backups auf dem NAS oder PC mit Samba Backup
Hi, seeking some help here. Since December 2021 I have had no successful backup. My backup seems to take longer than 3 hours and that crashes something causing to have local backup but not on samba.
I have excluded addons, but the ones I really need I let in. I deleted the homea sssitant database.
Where and how can I see how many storage an addon is using? e.g. influxdb?
I have glances, but that doesn’t show me:
Nice work solved a problem! Thank!
My suggestion would be to improve error handling.
The remote store could not be reached while performing a scheduled task, so the job failed.
No alerts or warnings were received about the incident, although this would be important for you to investigate the issue. - I accidentally noticed.
@thomasmauerer Opinion on this after 3 months?
Maybe at least allow a wildcard for the exclude_addons
parameter, that’d be a big step forward already. As you see: there are ideas…
Does this samba backup addon also backup node red flows?
This addon uses the normal Home Assistant OS function to backup the system. If the flows are insides these backups, everything is fine.
I realize that it has been a long time, but I had a similar problem caused by the deprecated emulated Hue - Alexa interface grabbing port 80.
Maybe a bit off topic, but what should I backup? I choose everything now, but the backups are growing some Mb per day. I have space, so that is not the issue.
Well you can probably skip the database as that is usually corrupted during backup.
Keep a copy of your addon configurations stored in a text file off system then you can skip a lot of addons too. You just need to reinstall them and copy the config over after a backup restore.
Im trying to exclude the “www” folder and cant get it to do this. How can I accomplish this?
The manual says: The folders to exclude in the backup. This will trigger a partial backup if specified. Possible values are homeassistant
, ssl
, share
, addons/local
and media
.
so, if these are the possible folders, www can’t be excluded.
-
What delete command is used for the remote backup storage cleanup?
I found a lot of “should be deleted” backups in my remote SAMBA storage.recyclebin
folder - just wondering if I need to take care of them by my own or if there’s an option to set the deletion command used for the remote storage. -
How to stop a currently running backup process?
Can I safely stop the SAMBA backup addon and remove the unfinished backup file - or will the process run until it finished, independently of the addon status?
ad 1)
The standard rm
command of smbclient. If you’re using a recycle bin, you have to delete the backups yourself from your recycle bin folder. The addon cannot do this automatically in this case.
ad 2)
You can stop the addon, but the backup will continue running until it is finished. The addon just tells the supervisor to create the backup. That’s exactly the same if you create a backup manually on the supervisor page.
installing samba backup causes an “Unknown error, see supervisor logs”
Logger: homeassistant.components.hassio.handler
Source: components/hassio/handler.py:237
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 03:20:55 (4 occurrences)
Last logged: 09:55:12
Timeout on /supervisor/options request
and
Logger: homeassistant.components.hassio
Source: components/hassio/websocket_api.py:120
Integration: Home Assistant Supervisor (documentation, issues)
First occurred: 09:49:50 (3 occurrences)
Last logged: 09:55:12
Failed to to call /supervisor/options -
what do I do wrong?
Its this step
1. Navigate in your Home Assistant frontend to **Supervisor** -> **Add-on Store**
and add this URL as an additional repository: `https://github.com/thomasmauerer/hassio-addons`
thanks
ps: I did setup my HA freshly yesterday from the official HA .vdi container.
edit: after several trys the repo got added…
i have this code in scipts
alias: backup
sequence:
- service: hassio.addon_stdin
data:
addon: 15d21743_samba_backup
input: trigger
mode: single
but i dont get a backup when triggered, and no entry in the logs
edit: 10 hours later, i just browsed by the backup location, and the backup from noon today was there. funny it took so long to show up for a 112mb backup. the smb share is on a 10gbs link to the HA server, its basically the same machine since HA runs in a VM on the NAS. so problem solved, lets see if the automation works
Apologies for a super simple question here, but how do I install this?
I tried following the instructions on the Gitbhub page, namely adding https://github.com/thomasmauerer/hassio-addons
as a repository, but once that is done, nothing else happens, no extra addons appear in the list, and if I search for samba backup, no results are found.
What am I missing?
Thanks
Did you tried to “Restart” ?