Thanks for implementing the many new options in 2025.2 (testing in beta currently), among which the option to customize the automatic schedule time. Either set it to the optimal default, or set it to user preference.
Personally, I like the optimal defaults, for all locations, system internal and cloud.
However, I also added my Synology Nas as location, which is down during the night (power savings)
So, if I want the backup system to use the Synology, I need t adjust the scheduled backup time, to let’s say 22:00.
This would be fine, if it wouldnt also set that timing now for all other locations.
And, being called optimal for the system, that is not optimal
and while on the topic of config per location:
it would be great if we could set a delete option per location too, and not per backup (for all locations ensemble)
we already have Download from this location, please add Delete from this location
Just updated to version 2025.2.1.
Tried to user the new backup system.
My objective here is save my backups local and on OneDrive.
My request 1 - retention: Allow set the retention by destination. My request 2 - cancel backup execution: Notice the integration automatically triggered a backup creation before I finish my setup and there is no way to cancel it. Should be. My request 3 - OneDrive : Appears this integration was created to be specific to backup. But not allow customize the destination folder and this is bad. Should have a way to specify the folder when add the service, so this integration can be used for multiple objectives where we can add multiple services , eachone for each folder.
To exemplify:
My HA run on container, over a tvbox with debian , so low disk space.
I want to keep a considerable history backup on my OneDrive where I plenty of space.
@ceinmart 's Request 1 is important also for me.
I would add also: to be able to select included addons by destination.
My problem: the full backup is ~4.x GB (because of InfluxDB → 3.7 GB)
Additionally I would appreciate a solution to be able to do dayly a backup WITHOUT influxDB , and weekly a backup WITH influxDB and somehow be able to make use of the backup retention by keeping last few days but also last weekly full backup
I looked for these requests and didn’t found. If you saw another request for this, please reference it here to allow us to vote too.
About making them separated, you are 100% right, this was my first request and don’t pay attention to the operational of votes here…
I see one problem in the backup location. If I use Samba Backup and I can place the backup in a subfolder. With the new HA backup and network location settings, this is not possible. The problem arises if I set the path to one location. Production HA and test HA how do I know which backup belongs to one or the other HA if it is not possible to place each HA in a subfolder separately.
This is actually possible right now: on the network storage configuration use share/folder (with forward slash) in the “Remote share” field and it works fine…
Today I took the opportunity to set up cloud backup with the new features, and the results were very good.
But I have some questions that I don’t know if they are just my own:
Why can’t I set up an automatic backup in addition to daily or weekly, for example once a month?
Why can’t I create multiple backup rules, for example daily backups on NAS and weekly backups on One Drive?
An alternative to the two items above would be to include parameters for where the backup should be saved in the backup.create action, so I can automate it with the frequency I want and indicate the location where the backup should be saved.
At this point, these are just abstractions that I had, I’m sharing them to see if they are needed by other users.
I mean, why would you ever need more than a few days backups? If I mess up my installation, I just go back to the prior day’s backup. I’ve never needed to go further back.
If there is a reason for a flood of backups, I don’t get it.
I literally was about to write a feature request for this exact PROBLEM. Having the retention on the LOCATION would be much more useful. I keep filling up my Google Drive and have to manually go in and remove them every few days.
So either I have to tune it down to 3 backups across the board or deal with the tedious task of this chore. Seems like a short-sighted way to implement retention policies when most folks probably do a few local and remotes for safety.
And this is why normally you can set very specific retention, for example: Keep 7 days of daily backups, then 4 weekly backups, then 3 monthly backups. So now you will have 12 backups going back 3 months, instead of 90 backups. So if something went really wrong, or more likely you need to extract something from an old backup, then you still can, without wasting space.
