Shared ToDo deleted tasks > how to restore?
Hello everyone, We share a ToDo with my colleagues and I deleted some tasks by mistake. I tried to restore them but whitout success. I cannot find any place where those deleted items went. I tried a lot a of solutions found on the net but none of them worked. I also point out that those tasks were not mine. So I am looking for some help. Does anyone have an idea or even a solution about that?
Secondary Databases Not Recovering
We had a fail over last night due to Windows patches being applied. Most databases were fine but we had a few that were stuck in Initializing / In Recovery. From the logs I see the following for the databases in question. -Availability database 'dbname', which is in the secondary role, is being restarted to resynchronize with the current primary database. This is an informational message only. No user action is required. -Nonqualified transactions are being rolled back in database Administrator for an Always On Availability Groups state change. Estimated rollback completion: 100%. This is an informational message only. No user action is required. -State information for database 'dbname' - Hardened Lsn: '(20363:176333:1)' Commit LSN: '(20363:176332:1)' Commit Time: 'Apr 8 2020 7:42PM' -Always On Availability Groups connection with primary database established for secondary database 'dbname' on the availability replica 'nodename' with Replica ID: {...}. This is an informational message only. No user action is required. -6 transactions rolled forward in database 'dbname' (5:0). This is an informational message only. No user action is required. -Always On Availability Groups connection with primary database established for secondary database 'dbname' on the availability replica 'nodename' with Replica ID: {...}. This is an informational message only. No user action is required. Those logs lead me to believe the recovery process completed but the databases never actually recovered, syncing did not start back up. What else can I look at to troubleshoot this issue? Is this a bug? We would like to figure out the root cause so this does not occur again. SQL Server version 13.0.5598.27