• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

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