Hi Everyone,

We've started the development of this feature, but we'd like to ask some feedback before proceeding.

When creating a new file backup for your site you need to select a backup configuration at first. After that we ask some additional information such as the path, interval, excluded folders, etc. Some of them are specific to the backup configuration type (Local, Dropbox, Google Drive, ...).

Would you like to configure these settings when creating a new backup configuration or should we use some default settings that you can adjust if you want to?

Many thanks!

The way that works for me very well at other admin-panels is the following: When creating a new backup configuration/schedule, instead of creating this for a specific site, it is created for "all sites". Every time I add a new site to a server, it is automatically includes in all backups for "all sites".

It would be cool to have an include/exclude filter in "all sites" by site type to cater e.g. for different exclude folders. So I could have like one schedule for "all laravel sites" and one for "all wordpress sites".

This way I can have multiple backup schedules for "all sites" (like daily + weekly + monthly) and additional individual backups schedules for individual sites (like for hourly backups or longer retention).

I came here to put in this feature request and see it's already open and in progress.

In a multi-tenant environment, databases will be added/removed constantly, therefore having an option to automatically add new databases to the backups is quite useful.

This would be a nice option! And also show in the site list if a site has backups enabled or not

Is there already some more info about this feature?

Related: Dynamic backup destination + name https://roadmap.ploi.io/projects/3-panel-requests/items/1082-backup-defining-dynamic-dynamic-destination-folder-name

It would be great if we could automatically add databases to a predefined backup-config after creation (ideally automatically).

In combination with the dynamic target + name from the ticket above this would allow to create a global backup-config for all databses by default.

Same could be build for files: Defining a schedule, dynamic file target, how many to keep, which files to exclude and than just adding sites to it. This allows e.g to create a backup-template per application-type (Nuxt, Directus, Laravel,...)