Snapmanager for SQL: Timeout Expired

Error Code: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Example:

[08:01:47.379] [HostName] Connecting to SQL server HostName...

[08:01:47.383] [HostName] Transaction log backup for database [BSM] will truncate logs...
[08:01:47.383] [HostName] Starting to backup transaction log for database [BSM]...
[08:04:15.879] [HostName] Database [HostName:BSM] Percent: 5% completed
[08:06:48.387] [HostName] Database [HostName:BSM] Percent: 10% completed
[08:08:43.885] [HostName] Database [HostName:BSM] Percent: 15% completed
[08:10:43.644] [HostName] Database [HostName:BSM] Percent: 20% completed
[08:11:47.474] [HostName] [SQL SMO Error]: Backup failed for Server 'HostName'. 
An exception occurred while executing a Transact-SQL statement or batch.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[08:11:47.483] [HostName] [SQL SMO Error]: Backup failed for Server 'HostName'. 
An exception occurred while executing a Transact-SQL statement or batch.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
[08:11:47.483] [HostName] [SQL SMO Error]: Backup failed for Server 'HostName'. 
An exception occurred while executing a Transact-SQL statement or batch.
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.

Solution:  http://support.netapp.com/NOW/cgi-bin/bol?Type=Detail&Display=660615

In SnapManager 6.0 for Microsoft SQL Server, if a transaction log backup
takes more than 10 minutes, it will fail with error
[SQL SMO Error]: Backup failed for Server ‘SOMEW’.
An exception occurred while executing a Transact-SQL statement or batch.
Timeout expired. The timeout period elapsed prior to completion of the
operation or the server is not responding.

Add a DWORD registry “LogBackupUseSMO” in HKEY_LOCAL_MACHINE\SOFTWARE\
Network Appliance\SnapManager for SQL Server\Server and set it to 0,
then restart SnapMgrService.

In SMSQL 6.0, SnapManager for SQL uses a different method than in prior
releases for backing up transaction logs, and this method has a timeout
of 10 minutes.
Note the above mentioned workaround does not support copy-only log backup.