Our Clone DB went into RECOVERY PENDING state, after a reboot. It seems like the servers loses the connection to the image location. Is this normal? How to fix this?


Comments
3 comments
-
Is the SQL Clone Agent service running? Databases need to be remounted by the service on reboot, which should be done automatically by the Agent.
-
Yes. Clone agent was stopped. As soon as I started it, everything went well! Thank you so much.
-
If you have a group MSA account and SQL Clone, then make sure your SQL Clone Server depends on SQL Server and w32time services. This will avoid situations where you reboot the domain controller and sql server at the same time and a race condition occurs between SQL Sever starting and SQL Clone coming up.
Cheers
Add comment
Please sign in to leave a comment.