Skip to main content
NetApp Knowledge Base

SMSQL verification fails at the attach database phase when creating the clone in an FCI

  1. Last updated
  2. Save as PDF
Views:
181
Visibility:
Public
Votes:
3
Category:
snapmanager-for-microsoft-sql-server
Specialty:
legacy
Last Updated:

Applies to

  • SnapManager for SQL (SMSQL) 7.2.x and above
  • SQL Failover Cluster (FCI)

Issue

  • Verification fails at the attach database phase of the process
  • Error seen in SMSQL job report:

    "[23:02:03.353]  [hostname] Attaching database [database_name_Clone]...
    [23:02:03.353]  [hostname] CREATE DATABASE [database_name_Clone] ON PRIMARY (NAME = 'database_name', FILENAME = 'disk_name') LOG ON (NAME = 'database_name_log', FILENAME = 'disk_name.LDF') FOR ATTACH
    [23:02:03.368]  [hostname] [SQL SMO Error]: An exception occurred while executing a Transact-SQL statement or batch.
    Cannot use file 'disk_name' for clustered server. Only formatted files on which the cluster resource of the server has a dependency can be used. Either the disk resource containing the file is not present in the cluster group or the cluster resource of the Sql Server does not have a dependency on it.
    [23:02:03.368]  [hostname] DBCC CHECKDB (database_name__Clone') WITH NO_INFOMSGS, PHYSICAL_ONLY
    [23:02:03.384]  [hostname] [SQL SMO Error]: An exception occurred while executing a Transact-SQL statement or batch.
    Could not find database 'database_name__Clone'. The database either does not exist, or was dropped before a statement tried to use it. Verify if the database exists by querying the sys.databases catalog view.
    [23:02:03.384]  [hostname] WARNING: SQLServer DBCC CHECKDB failed."

  • Verification done via SQL Management studio without SMSQL using the command below also fails with the same error
    CREATE DATABASE [database_name] ON PRIMARY(NAME = N'database_name', FILENAME = N'database_path.mdf'  ) LOG ON(NAME = N'database_name_log', FILENAME = N'N:\SQLLOG\database_path_log.ldf')"

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.