SCSQL quiesce fails for one or more databases after upgrading to 4.9

Applies to

• SnapCenter Server (SC) 4.9/4.9P1
• SnapCenter Plug-in for Microsoft SQL Server (SCSQL) 4.9/4.9P1

Issue

• After upgrading SCSQL to 4.9 or 4.9P1, the quiesce/unquiesce process fails for one or more databases, even if the VDI timeout has been increased on the SCSQL host(s).
  • Error seen in <installation_path>\Program Files\NetApp\SnapCenter\SnapCenter Plug-in for Microsoft SQL Server\log\SmSql_<id>.log:

DEBUG SmSql_1231046 PID=[7908] TID=[199] Database [DB_Name] Quiesce is done... Waiting for UnQuiesce event...
DEBUG SmSql_1231046 PID=[7908] TID=[99] Calling SQLBackupRestoreVDI...
DEBUG SmSql_1231046 PID=[7908] TID=[99] Creating virtual device on : [host\instance]....
DEBUG SmSql_1231046 PID=[7908] TID=[99] Executing VDI Command on database [DB_Name]....
DEBUG SmSql_1231046 PID=[7908] TID=[146] Vdi timeout value - 1200000
DEBUG SmSql_1231046 PID=[7908] TID=[146] Connecting to SQL Server: [host\instance]
ERROR SmSql_1231046 PID=[7908] TID=[111] Quiesce could not complete for following databases within the timeout:
'DB_Name,DB_Name,DB_Name;'

• Failure of the quiesce/unquiesce process may also result in the following issues being experienced:
  • Loading of jobs in the SC UI Monitor tab taking much longer than normal.
  • SCSQL locking up protected SQL databases with multiple simultaneous connections, resulting in database-connected applications not responding.