It would be great if backup names included the Server Name in the backup file name, so instead of the file name being: backup_2109240314_2109300314.tar it is identifiable as: backup_example_server_2109240314_2109300314.tar.

For ie: an INI variable that can be set or some other option to change this behaviour

The reason for this change is that long term storage and search tools only allow file archival retrieval by searching for a file name part or a date range. So restoring a backup for a specific server becomes very challenging when the backup files for all the servers have similar file names!

Applies to: I'm currently using a paid Dropbox account as an offsite backup, but this is relevant for all (offsite) backups.

What happens: When running full server backups, Plesk currently creates a file called server.domain.tld.tar.

The problem: When scheduling (daily/weekly/monthly) full server backups, the new backup file will have the exact same name as the previous backup file.

The result: When selecting e.g. the 12 latest backups to be saved, Plesk backup manager will display these backups as individual entries, but in reality when using a service like Dropbox to create automated off-site backups, the next backup overwrites the previous backup and relies on the version history feature (if available) of your off-site service. In case of Dropbox this is 30 days for a lot of plans.
In another uservoice entry, Plesk team calls this behavior a feature, as it doesn't count against the storage cap when version history is used. However, the availability of version history is way more restricted (and more expensive) than simple storage space.

Suggested solution: Allow users to add a dynamic prefix/suffix like the creation date of the backup to the file name. This simple change would allow users to choose between:
1. having the dynamic prefix (date) in the file name allowing for longer backup history than the off-site service 'version history' dependency allows for, while taking up more storage space.
2. not having a dynamic prefix (date) in the file name, allowing for the use of the off-site service 'version history' feature.

This way users can pick between less storage used or a longer backup history.

In my personal situation I have 2TB of storage, 20GB full server backups that I run once a month. I want to keep 12 backups for a total of ±240GB of storage. This is well within the boundaries of my storage allocation, but is currently impossible as Plesk is overwriting the file, causing a 30 day expiry of my monthly backups instead.

Thank you for adding a custom space in front of the name of the backups to help differentiate a set from another

Hello,

Please add ability to modify names for backups to help differentiate them.

Adding my vote to this - current backup is hopeless. I create hundreds of backups of individual domains every day. It's virtually impossible to try and track one down to restore without manually clicking on each one. Even if we could add our own comments for each backup so you could identify them. It's very frustrating

For whatever it is worth, this is not a feature addition. The latest release breaks existing functionality that many of depended on for daily functionality of Plesk. Please do not treat this request as an option, but rather a restoration of a vital feature.

I have now put all my backups into individual folders to TRY and get round this issue. It’s a manual process and a real pain to do. I am also now in the position that any old backups I want to keep from domains no longer on the server can’t be accessed from Plesk because they are in a folder of a domain no longer on the server.

The no naming of these backup files is madness.

I just encountered another case where it was almost impossible to distinguish all of the backups, especially incremental ones. There is no way around it. We need to have filenames that make sense. Otherwise, I have to find a different way to backup the server, and I really would rather keep it within the same system, if possible.

This feature is not helpful it's a MUST HAVE, with all the various backup of different domains done on the server it is very frustrating not being able to differentiate them easily.

Please add this feature as soon as possible for the conveniance of all server administrators.

Agree new 12.5 backup file naming convention is totally useless.

It would appear that in version 12.5, the backup engine now saves everything with a filename of backup_infoxxxxx. This is absolutely no help to discerning dozens, hundreds or even thousands of backup files. I am not sure why this was changed, but it needs to be the domain and the date and comments, just like the old versions of the backup manager.

The ability to add a prefix to the backup name was quite useful, as I could immediately identify the files when connecting in SSH.

Could that option be re-installed in the backup system?

Now I have all theses backup files named "backup_1510290401.zip" and I don't know which server they are for!?!?!