• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Issue Cannot resume domain, missing remoteStorage column

Runner

New Pleskian
Started happening after moving Plesk website to another server with new version of Plesk.

Code:
Error: domain "xxx.com"
Cannot resume domain 'xxx.com'. The domain 'xxx.com' may be inaccessible after backup. Please, resume it manually!

Error:
Error in execute ''"C:\Program Files (x86)\Plesk\admin/plib/backup/suspend_handler/SuspendHandlerRunner.php" unsuspend ourdatamrc.com "C:\Program Files (x86)\Plesk\PMM\sessions\2018-12-17-075753.970"': Turn on domain failed: DB query failed: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'remoteStorage' in 'field list', query was: select `id`, `obj_id`, `obj_type`, `repository`, `last`, `period`, `full_backup_period`, `active`, `processed`, `prefix`, `email`, `split_size`, `rotation`, `suspend`, `with_content`, `backup_time`, `backup_day`, `content_type`, `backupExcludeFilesId`, `backupExcludeLogs`, `remoteStorage`, `mssql_native_backup` from `BackupsScheduled` where `id`=8

An attempt to add this missing column to backupsscheduled table leads to following:

Code:
SQL Error (1025): Error on rename of '.\psa\#sql-e64_443b' to '.\psa\backupsscheduled' (errno: 184 - Tablespace already exists)

Any idea how to fix this?
 
Unfortunately this only made things worse, "plesk repair db" deleted some tables and were not able to recreate them due to some INNODB issue. Also backups repair tool made were not complete for the same reason. Most likely this is a result of faulty migration and not something that Plesk repair tool introduced.

Anyway, the Plesk database is completely broken now. What are my options of restoring customers accounts and subscriptions from existing customers websites and data? Even if this needs to be done one by one - what can be done and how? Customers websites are in fully working condition, just control panel data is missing.
 
For recovering Plesk database on your server I suggest you contact Plesk Support Team.
 
Back
Top