@karam
A small tip - it is recommended to allocate a new server and migrate all data to the new server, before doing something on the old (problematic) server.
After all, the site data is or should not be compromised, the Plesk related (server-wide) data probably is.
If you follow this procedure, you will have a fresh Obsidian 18.0.27 instance, which can also function as a backup (of data) and a fail-over (of sites and services).
Please note that you should inspect disk performance on the old (problematic) server, since it is very likely that you will encounter problematic performance - this is another reason for not using regular backup methods : a regular backup process via Plesk will put a heavy burden on your (old) server.
In short, in order to prevent a full breakdown of the old server with complete data loss, I would recommend to migrate data to a new server - as a work-around.
Hope this suggestion helps a bit.
Kind regards........
Got it, thanks for the tip, what I usually do, I re-insert manually the backed up domains, (very small number and won't be large as we are private company)
So I take the user files and database and insert them manually in the new plesk server, I also take every needed information, like emails and dns data.
I never restore a full backup between old and new server. that should be a good practice right ?