• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved Upload backup files

dicker

Basic Pleskian
Server operating system version
Ubuntu 22.04.4 LTS
Plesk version and microupdate number
Plesk Obsidian Version 18.0.58 Update #2
Is there no other possibility? I can't import customers' backups via SSH every time.
File size 2GB for backup is definitely not enough.
What options are there for the customer to independently upload backup data larger than 2GB?
 
Why do the customers download such large backups in the first place? Wouldn't it be much better for them to store them to an external FTP or S3 storage space? For FTP/FTPS all tools are included in the basic version of the product. But with the Cloud Backup Pro extension they could also export their backups to Google Drive, MS OneDrive etc. It's just not best practice to download such large backup files to a local computer.
 
Of course I make backups.
The customer backup is probably older than what I have.
I don't know why the customer wants to import such an old backup.
 
Is there a solution to this problem?
 
Back
Top