Timeout problem in Backup-SQLDatabase cmdlet in SQLPS module - by Zerocool18

Status : 

  Duplicate<br /><br />
		This item appears to be a duplicate of another existing Connect or internal item.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 805087 Comments
Status Closed Workarounds
Type Bug Repros 3
Opened 10/10/2013 11:11:50 PM
Access Restriction Public


I’m trying to take back-up of a large database using “Backup-SQLDatabase” cmdlet using following statement, but I’m getting time-out error after 10 minutes.

    Backup-SqlDatabase -ServerInstance $Server -Database $DatabaseName -BackupFile $BackUpFile -CompressionOption On -ConnectionTimeout 0 -Initialize -Verbose -ea Stop

Here’s the error exactly after 600 seconds of execution :

VERBOSE: 60 percent processed.
VERBOSE: The backup or restore was aborted.
The wait operation timed out
    + CategoryInfo          : InvalidOperation: (:) [Backup-SqlDatabase], Win3 
    + FullyQualifiedErrorId : ExecutionFailed,Microsoft.SqlServer.Management.P 
    + PSComputerName        : localhost 

I looked up at internet and found a bug filled for Restore-SQLDatabase.
However, the issue still exists in SQL Server 2012 (11.0.339).

I’ve also tried reconfiguring “remote query timeout” to 0 as given , but the issue persists.

This negates the very purpose of this cmdlet. Back-ups do take more than 10 minutes. And I don’t think this scenario was even tested.

Sign in to post a comment.
Posted by maemmott on 7/14/2017 at 9:13 AM
When you mark an entry as a duplicate, please would you link to the entry it duplicates, so that interested people can see the outcome on the lead entry. This would fit most naturally as a hyperlink in the 'Duplicate' text in the header, but I cannot find a link anywhere in this entry.
Posted by Zerocool18 on 8/17/2015 at 12:04 AM
Why is this item "Closed As Duplicate" ?
Posted by Microsoft on 11/22/2013 at 3:24 PM
This item has been promoted to a hotfix and will be addressed in a coming Cumulative Update for SQL Server. Thank you for your feedback.
Posted by Microsoft on 10/25/2013 at 9:18 AM
Thanks for the feedback. We'll keep this item active so that other members of the community get a chance to see it and provide their own input. We'll keep an eye on it as we plan the next big things for SQL.