SMSQL verification fails at the attach database phase when creating the clone in an FCI
- Last Updated:
- SnapManager for SQL (SMSQL) 7.2.x and above
- SQL Failover Cluster (FCI)
- 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')"