• 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.

Issue Testing Disaster Recovery - Windows: Stored Procedures missing after full backup restoration on another server.

Superbutler

New Pleskian
Server operating system version
Windows Server 2022 Datacenter Version 10.0.20348
Plesk version and microupdate number
18.0.59 #2
Hi,

We are testing disaster recovery on Windows Server.

We performed a full backup of Plesk, including databases and subscriptions, with the database located on the same Plesk server. The backup was successfully generated. We then restored this backup on another server with the same version of Plesk, and the restoration process was successful. However, when we attempted to access the application, it resulted in an error.

Upon reviewing the application logs, we discovered that some stored procedures were missing. This issue might be due to database referential integrity. We did a manual fix by generating a comparison script using MS Visual Studio and executing it. Our application was up and running after this.

Please note that we have already tried disabling the triggers and constraints before restoring the Plesk backup using the following commands:

-- Disable triggers
EXEC sp_MSforeachtable "ALTER TABLE ? DISABLE TRIGGER all";

-- Disable constraints
EXEC sp_MSforeachtable "ALTER TABLE ? NOCHECK CONSTRAINT all";


Could you please advise on how to ensure all database components, including stored procedures, are accurately backed up and restored?

Thank you.
 
Just to understand the issue a bit better, you saying that some Stored Procedures are restored but other are missing after a backup restore?
 
Hi Kaspar, thanks for your message. Yes, that is correct. Some of the SPs were not executed in the restoration process.
 
Back
Top