Databases showed "recovery pending" (SQL 2019)

Question

Hello,

• customer has one SQL 2019 Standard on a Windows 2016 Std. (vmware esxi) and he use four databases
• I restarted the Windows Server three different times in the last month because of application maintenance
• at two times SQL Databases showed in MS SQL Studio: recovery pending

adhoc Solution was:

• rightlick restarting SQL-Instance via Studio again

SQL Log I will post here later

Details:

abla_DB (very small)
import_DB (recovery pending) (import_DB.mdf = 3 GB, with approx. 60GB Filestream Folder), BAK = 65 GB)
practical_DB (recovery pending) practical_DB.mdf = 20 GB, with approx 1,5GB Filestream Folder, BAK = 20 GB)
system_DB (very small)

Side-Infos:

• Veeam Backup and Replication is doing Image-Backup
• no SQL Dumb backup via sql agent configured yet
• before reboot I manually stopped onetimes SQL Server Instance Service, looks like no effect
• the Server is installed since 1-2 month

Can you help me find the cause?

Thx + Best Regards in advance!

Answer 1

I see this:

12/31/2020 10:38:54,Server,Unbekannt,SQL Server detected 12 sockets with 1 cores per socket and 1 logical processors per socket<c/> 12 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational message; no user action is required.

And this:

12/31/2020 10:27:08,spid11s,Unbekannt,A failure occurred while FILESTREAM configuration was being changed or applied. For more information<c/> see the SQL Server error log.
12/31/2020 10:27:08,spid11s,Unbekannt,FILESTREAM: effective level = 0<c/> configured level = 2.
12/31/2020 10:27:08,spid11s,Unbekannt,FILESTREAM: failed to connect to kernel driver RsFx0600.<nl/><{1038F43D-3391-45F7-B1B3-BADF26459429}>Failed to initialize CFsaShareFilter: Error 0x80070015 (-2147024875)

You could try setting the SQL Server service to delay start - as it seems some of the drives may not be available after a server restart.

Answer 2

Hi @Matrix-Matrix-Matrix ,
Agree with others. There seems to be a time difference between the startup of the SQL Server instance and the startup of the Filestream driver.
Besides, you can try to set SQL Server Service startup type in manual and create a task to delay for a few minutes to start SQL Server service in Task Scheduler.

Here is a similar thread using this solution to resolve this issue.

Best Regards,
Amelia

---

If the answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Hello,

thx a lot for your constructive ideas and statements!

you could try setting the SQL Server service to delay start

"sql delay-start" solved the situation! thx again