PDA

View Full Version : Sql2005CreateBackup timed out


ina
08-08-2008, 12:37 AM
Hello,

We tried to perform a backup of our 2005 database, using the discountasp.NET API, but we got the following error:

"The operation has timed out
at System.Web.Services.Protocols.WebClientProtocol.Ge tWebResponse(WebRequest request) at System.Web.Services.Protocols.HttpWebClientProtoco l.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtoc ol.Invoke(String methodName, Object[] parameters) at discountaspApi.CustomerApi.Sql2005CreateBackup(Str ing key, String databaseName).."

For the past 3 weeks, each time we tried to perform a backup we received the above error.
Can you help us to understand what the problem is?

Thank you.
</o:p>

Aristotle
08-11-2008, 04:14 AM
Since the backup calls are synchronous, it can timeout if your database is too big. We'll be working on an asynchronous version of the backup tool, just like in the control panel.

Even if it timeout, is the backup file created anyway?

Aristotle

DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)

ina
08-12-2008, 11:20 AM
Yes, the backup file is created anyway, even if it timeout, but not sure if it is completed.
Anyway after performing the backup, our application should move it to another server and use it to perform some other operations. So it is important for us to know when the backup is ready.
As a temporary solution, we could catch the error and check if the backup exists in case of SQL2005CreateBackup (System.Net.WebException) error.

The only one question is: will it be done (completed) 100%? Can you assure us that the backup will be finished even if it timeout?

How much time will take to have an asynchronous version of the backup tool?

Thank you,

Ina Vaduva

Aristotle
08-15-2008, 05:41 AM
Since the backup procedure continues to run in the background, you won't be able to tell for sure if it has completed. It all depends on the size of the database. I doubt a backup will take more than an hour. So it's pretty safe to assume that after an hour, it has finished.

You can also try increasing the web reference object's WebClientProtocol timeout.

Aristotle

DiscountASP.NET
www.DiscountASP.NET (http://www.DiscountASP.NET)