Hi,
we're running on SQL Server 2012 SP4 on Windows Server 2012 R2 with SnapManager for SQL Server version 7.2.3.2841 and
our database backup / verification fails every time for one Database with about 2.5 TB:
The following lines are logged in the log file:
Attaching database [MyDatabase__Clone]...
CREATE DATABASE [MyDatabase__Clone] ON PRIMARY
(NAME = 'MyDatabase', FILENAME = 'M:\MP\MPDisk001\MSSQL11.MSSQLSERVER\MSSQL\Data\MyDatabase_Data.mdf'),
(NAME = 'MyDatabase_Data_2', FILENAME = 'M:\MP\MPDisk001\MSSQL11.MSSQLSERVER\MSSQL\Data\MyDatabase_Data_2.ndf')
LOG ON
(NAME = 'MyDatabase_Log', FILENAME = 'M:\MP\MPDisk002\MSSQL11.MSSQLSERVER\MSSQL\Data\MyDatabase_Log.ldf') FOR ATTACH
Database attached.
DBCC CHECKDB (N'MyDatabase__Clone') WITH NO_INFOMSGS, PHYSICAL_ONLY
6 hours later...
[SQL SMO Error]: An exception occurred while executing a Transact-SQL statement or batch.
Timeout abgelaufen. Das Zeitlimit wurde vor dem Beenden des Vorgangs überschritten oder der Server reagiert nicht.
Der Wartevorgang wurde abgebrochen
WARNING: SQLServer DBCC CHECKDB failed.
Maybe the following lines in debug log can help:
I enabled debug logging and found the following lines before DBCC starts
CSnapMgrSqlBase::AttachDatabasesByTSQL_SMO() - Finished hr = 0x0
CSnapMgrSqlBase::AlterDatabaseAutoshrinkOFF_SMO(MyDatabase__Clone) start
CSnapMgrSqlBase::AlterDatabaseAutoshrinkOFF_SMO() return hr = 0x0
CSnapMgrSqlBase:
moAttachDatabase_SMO() - Finished hr = 0x0
CNtapSqlVerify::AttachDatabaseThenDBCC4 - Calling RunSQLCmdDBCC2
CSnapMgrSqlBase::RunSQLCmdDBCC2_SMO - Started
m_dwSmoStatementTimeout: 10800
I guess that's 180min / 3hours which doesn't describe the error after 6 hours, but since the original error message says [SQL SMO ERROR] it may be related.
Smaller databases within the same instance / on the same LUNs run without any problems (but dbcc finishes in less than 3 hours). Datafiles and Logfiles are located on different volumes and the source database instance is used for verification.
We already increased the RemoteBackupThreadTimeout without any success (https://community.netapp.com/t5/Data-Backup-and-Recovery-Discussions/SMSQL-remote-verification-timeout/td-p/42309)
Any ideas? Does someone know a way to increase the SmoStatementTimeout? I couldn't find an option in GUI / registry / config files so far.
Thanks in advance!