• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion
  • Inviting everyone to the UX test of a new security feature in the WP Toolkit
    For WordPress site owners, threats posed by hackers are ever-present. Because of this, we are developing a new security feature for the WP Toolkit. If the topic of WordPress website security is relevant to you, we would be grateful if you could share your experience and help us test the usability of this feature. We invite you to join us for a 1-hour online session via Google Meet. Select a convenient meeting time with our friendly UX staff here.

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