March 22, 2013 at 1:32 pm
SQL Server - 2012 SP1
Win OS - 2008 R2 Ent SP1
All,
We are adding 2 additional storage (SSDs) for Log. I have done the following tasks:
1) Went to Failover Cluster Manager
2) Went to Services and Applications and picked (MSSQLServer)
3) Right Click "Add Storage" and added the 2 disks.
4) Select the "Storage" and see the 2 added drives.
Run the restore command pointing the log and data files to the appropriate path:
USE [master]
RESTORE DATABASE [IPS] FROM DISK = N'\\dd860.ingramcontent.com\SQLRepository\ProdServers\USLVBIODSPC_1\IPS\FULL\USLVBIODSPC_1_IPS_FULL_20130321_174916.BAK' WITH FILE = 1, MOVE N'IPS' TO N'F:\MSSQL11.MSSQLSERVER\MSSQL\DATA\IPS.mdf', MOVE N'FG_IPS' TO N'D:\MSSQL11.MSSQLSERVER\MSSQL\SQLData\IPS.ndf', MOVE N'IPS_log' TO N'G:\MSSQL11.MSSQLSERVER\MSSQL\SQLLOGS\IPS.ldf', NOUNLOAD, REPLACE, STATS = 5
GO
Msg 5184, Level 16, State 2, Line 2
Cannot use file 'G:\MSSQL11.MSSQLSERVER\MSSQL\SQLLOGS\IPS.ldf' 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.
Msg 3156, Level 16, State 3, Line 2
File 'IPS_log' cannot be restored to 'G:\MSSQL11.MSSQLSERVER\MSSQL\SQLLOGS\IPS.ldf'. Use WITH MOVE to identify a valid location for the file.
Msg 3119, Level 16, State 1, Line 2
Problems were identified while planning for the RESTORE statement. Previous messages provide details.
Msg 3013, Level 16, State 1, Line 2
RESTORE DATABASE is terminating abnormally.
I run the following cmd:
select * from sys.dm_io_cluster_shared_drives
and still unable to see it.
Is there something that is amiss? Any thoughts?
March 22, 2013 at 9:23 pm
Hello,
Assuming that your disks are properly configured and successfully added to cluster manager (which they seem to be on paper), the final step you are missing is to add them as a dependency under the SQL Server resource within cluster manager. Once this step is completed, you will need to restart the actual SQL Server service within configuration manager for the changes to take effect. This should solve your problem.
Jay Beta
March 22, 2013 at 9:43 pm
I guess there's no need to restart the server after adding the disk as dependency.
March 23, 2013 at 7:57 am
You are right, there is no need under Server 2008. I really thought you did but then confirmed it from multiple sources that you did not. My bad.
March 23, 2013 at 11:41 am
Thank you jay & muthyala_51. I had not even thought about about and would not have thought about the dependencies!
They work like a charm!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply