We run a two node cluster, with all resources currently on one node. The server is working no problems - but..

We try to restore a backup and it completes, but leaves the database in LOADING status, without doing anything
We have had this failure when the cluster is not all on one node, we have two group
We can do a RESTORE VERIFYONLY which reports the backup set as valid, and we can copy the backup to another server and restore successfully there. So we suspect the cluster file system is not happy

Anyone seen this behaviour - and fixed it

We are trying to failover to the second node and restore there, and if that doesn't work then we'll try failing back to the first node again and try restoring again

-

We can restore on the second node, thats lucky

I did notice that the drive resources were listed out of order on the failing node, but are in order on the successful node (from Cluster Admin). I wonder if that means anything ?

If the database was left in a loading state, it means that you chose to
restore the backup with the norecovery option turned on.

--

Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com

Windows updates do not affect the ability to restore a back up. Open up
Query Analyzer and explicitly type in the command string to restore the
database. Is it still being left in a loading state?

--

Mike
Principal Mentor
Solid Quality Learning
"More than just Training"
SQL Server MVP
http://www.solidqualitylearning.com
http://www.mssqlserver.com