enerspace
Basic Pleskian
Username:
TITLE
Plesk Backup Manager creates backups using only one CPU thread (No multithreading)
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian 18.0.72 Update #1 Web Pro Edition
Almalinux 8.10
PROBLEM DESCRIPTION
Currently, a backup that is several hundred GB in size can take several hours to be restored. The reason is the lack of multithreading support.
This must finally change in the year 2025.
There has already been a UserVoice post about this for over a year. But there really shouldn't have to be one in the first place:
https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/49036487-add-backup-restore-sw-tar-multithreading
I therefore kindly ask that a multithreading alternative is finally added.
STEPS TO REPRODUCE
Restore a backup
ACTUAL RESULT
One CPU Thread
EXPECTED RESULT
Multithreaded
ANY ADDITIONAL INFORMATION
(DID NOT ANSWER QUESTION)
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
Plesk Backup Manager creates backups using only one CPU thread (No multithreading)
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian 18.0.72 Update #1 Web Pro Edition
Almalinux 8.10
PROBLEM DESCRIPTION
Currently, a backup that is several hundred GB in size can take several hours to be restored. The reason is the lack of multithreading support.
This must finally change in the year 2025.
There has already been a UserVoice post about this for over a year. But there really shouldn't have to be one in the first place:
https://plesk.uservoice.com/forums/184549-feature-suggestions/suggestions/49036487-add-backup-restore-sw-tar-multithreading
I therefore kindly ask that a multithreading alternative is finally added.
STEPS TO REPRODUCE
Restore a backup
ACTUAL RESULT
One CPU Thread
EXPECTED RESULT
Multithreaded
ANY ADDITIONAL INFORMATION
(DID NOT ANSWER QUESTION)
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug