• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Resolved Plesk backup w/ Dropbox - How to use a date-based filename

MHC_1

Basic Pleskian
Server operating system version
Alma Linux
Plesk version and microupdate number
18
We have the Plesk Backup using Dropbox as an external depository.

However, the backup always uses the same filename, so it only ever saves one back up at a time. Overwriting the previous one.

How can we make the backup filename both in Plesk and exported to Dropbox have dates in the file names?

backup_date.png


Example:

Currently it would be "servername.tar" but we would need the backups to be "servername-<date>.tar" ; eg "servername-20250529.tar" Or the folder path can be date relative; eg: "/20250529/servername.tar"

We use the Dropbox Extension for Plesk here: Dropbox Backup

I have also viewed this topic post Question - Plesk Backup Filename which implies file names by default can do this. How can we implement this on the Dropbox Backup?
 
Hi,
it was implemented this way on purpose, because Dropbox has file versioning Dropbox version history overview
in that case it is required to pay only for this one backup file and the versioning is free. Otherwise it will be required to pay per each backup file.

If you need separate backup files, consider to use other remote backup solutions and Plesk extensions:
 
@Nikolay Thank you. I was not aware that Dropbox had version history like this. While I personally would prefer date-based file naming for ease, your clarification does help and mitigates the fear of overwriting the persistent same file. Thank you. :)
 
Back
Top