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

Problem with Backup

E

elenlace

Guest
For a week now, when ever the daily backup runs I get the following error:

Backup error.
Unable to create dump file for MS-SQL database XXX on domain YYY

Attempting to run the backup manually to further debug the error, after the error appears, on the "Show Details" button the following shows:

Timeout Expired. The timeout period elapsed prior to the completion of the operation or the server is not responding.

I have tried the fix that appears on the KB but it doesn't do any good. Any thoughts?

The server is responding and the databases are working normally with ASP.NET.

Warmest Regards
 
Thank you for the response.

This is a local MS SQL server but apparently I have been able to
fix the issue.

Actually it was a Plesk timeout issue, I did a bit of searching in google and found a fix. It worked for last night backup.

In Remote Desktop, modify the Registry (REGEDIT)

Key: HKEY_LOCAL_MACHINE\SOFTWARE\PLESK\PSA Config\Config
Type: DWORD
Value: ADOConnectionTimeout
I modified this value to 300 (Decimal)

Key: HKEY_LOCAL_MACHINE\SOFTWARE\PLESK\PSA Config\Config
Type: DWORD
Value: ADOCommandTimeout
I modified this value to 300 (Decimal)

The default timeout set by Plesk is apparently too small for larger (>500MB) SQL Server databases.

Many thanks and Warmest Regards
 
Hi,

I have the same problem but my database is smaller than 500mb.
I tried the workaround (regedit) without any results.

Any other ideas?

Thanks.
 
Then I guess you can try a higher value (600 for example) until the timeout is sufficient for your particular database.

Or you might want to contact Plesk, although they are very seldom of any help.

Warmest Regards
 
Back
Top