MSSQL 2012 Backup Timeout

Question

Dear Microsoft Technet Team,
we have an issue regarding creating a Backup using Powershell. Each time we try backing up on special database we get into a timeout after 10 minutes (default connection timeout is as far as we know about 600 seconds). Creating a database backup using the
MSSQL Management Studio it works without any problems. Unfortunately we haven't found the option changing the default timeout. Of course on our other databases which require less time to create our backup there is no problem. We hope you may have any helping
advice. Thank you in advance. Please let us know if you need any further information.
Powershell command: sqlps Backup-SqlDatabase -Server db02 -BackupFile E:\\bacula-tmp\\backup-oewsaas.sql -Database oewsaas -Checksum
Backup-SqlDatabase : Timeout ist abgelaufen. Das Zeitlimit wurde vor dem Beenden des Vorgangs überschritten oder der Server reagiert nicht.
Bei Zeile:1 Zeichen:19
+ Backup-SqlDatabase <<<<  -Server db02 -BackupFile E:\bacula-tmp\backup-oewsaas.sql -Database oewsaas -Checksum
    + CategoryInfo          : InvalidOperation: (:) [Backup-SqlDatabase], SqlException
    + FullyQualifiedErrorId : ExecutionFailed,Microsoft.SqlServer.Management.PowerShell.BackupSqlDatabaseCommand
Event Log:
2014-03-04 08:21:41.89             Fehler: 3041, Schweregrad: 16, Status: 1.
2014-03-04 08:21:41.89             BACKUP failed to complete the command BACKUP DATABASE oewsaas. Check the backup application log for detailed messages.
Best Regards

Answer 1

Hello TenPart,
thank you for you answer. I have tried this already. Unfortunately I have problems using this workaround using the InputObject parameter. In additional is there a solution to set our timeout using the Microsoft SQL Server Management Studio? In the referenced
issue they say this is a bug, do you know if there are any bug fixes yet? Maybe you could give me a helping advice. Thank you in advance.
PS C:\Users\Administrator> [System.Reflection.Assembly]::LoadWithPartialName('Microsoft.SqlServer.SMO')
PS C:\Users\Administrator> $server="db02"
PS C:\Users\Administrator> $serverConn = new-object ("Microsoft.SqlServer.Management.Smo.Server") $server
echo $serverConn
Instance Name
PS C:\Users\Administrator> echo $serverConn.ConnectionContext.StatementTimeout
0
PS C:\Users\Administrator> sqlps Backup-SqlDatabase -InputObject $serverConn -Database oewsaas -BackupFile E:\bacula-tmp\backup-oewsaas.sql -Checksum
Backup-SqlDatabase : Netzwerkbezogener oder instanzspezifischer Fehler beim Herstellen einer Verbindung mit SQL Server. Der Server wurde nicht gefunden, oder
gegriffen werden. Überprüfen Sie, ob der Instanzname richtig ist und ob SQL Server Remoteverbindungen zulässt. (provider: Named Pipes-Provider, error: 40 - V
er konnte nicht geöffnet werden)
Bei Zeile:1 Zeichen:19
+ Backup-SqlDatabase <<<<  -InputObject [db02] -Database oewsaas -BackupFile E:\bacula-tmp\backup-oewsaas.sql -Checksum
    + CategoryInfo          : InvalidOperation: (:) [Backup-SqlDatabase], SqlException
    + FullyQualifiedErrorId : ExecutionFailed,Microsoft.SqlServer.Management.PowerShell.BackupSqlDatabaseCommand
PS C:\Users\Administrator> sqlps Backup-SqlDatabase -InputObject $serverConn -Server db02 -Database oewsaas -BackupFile E:\bacula-tmp\backup-oewsaas.sql -Che
Backup-SqlDatabase : Der Parametersatz kann mit den angegebenen benannten Parametern nicht aufgelöst werden.
Bei Zeile:1 Zeichen:19
+ Backup-SqlDatabase <<<<  -InputObject [db02] -Server db02 -Database oewsaas -BackupFile E:\bacula-tmp\backup-oewsaas.sql -Checksum
    + CategoryInfo          : InvalidArgument: (:) [Backup-SqlDatabase], ParameterBindingException
    + FullyQualifiedErrorId : AmbiguousParameterSet,Microsoft.SqlServer.Management.PowerShell.BackupSqlDatabaseCommand
Best Regards