• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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