SOLVED

Secondary database is stuck in "restoring" mode after configuring always on high availability

Copper Contributor

Hello Everyone

I'm using SQL server 2019 and i configured always on high availability group, when i checked the database on the secondary server it was stuck in "restoring" mode instead of being in sync mode.

I tried to use SQL server profiler to get some logs but there is no errors. i just see in the logs that the database on the secondary server was created after restoring the full backup + transactional backup "WITH NORECOVERY" from the primary server database.

i checked many similar discussions and tried a few workarounds before asking here but nothing help.

i also would like to mention that same problem occurred when configuring database mirroring on the mirror database but for this one i found a fix.

could you please help me with fixing this problem?

1 Reply
best response confirmed by Moe-Alkronz (Copper Contributor)
Solution

I found that this happens when carrying out the configuration using SSMS but if i script the always on high availability configuration and run it as TSQL script it works. same thing with DB mirroring.

I'm using SSMS 18.0, is this a bug?

1 best response

Accepted Solutions
best response confirmed by Moe-Alkronz (Copper Contributor)
Solution

I found that this happens when carrying out the configuration using SSMS but if i script the always on high availability configuration and run it as TSQL script it works. same thing with DB mirroring.

I'm using SSMS 18.0, is this a bug?

View solution in original post