July 31, 2018 at 10:27 am
Hi All,
I'm wondering if anyone has encountered the above scenario before?
I have 6 TDE encrypted databases on the above cluster (my TDE implementation utilises an Azure key vault and the SQL Server Connector functionality).
When I failover from node 1 to node 2 all of my TDE encrypted databases remain in a recovery pending state, the non-encrypted DBs are available.
If I fail back to node 1, all DBs pass the startup DBCC Checkdb ok and everything looks fine.
I have reinstalled the connector on node 2, and even reinstalled SQL on that node to no avail.
Has anyone got any experience of this that could help me resolve my issue please?
Many thanks,
Ross
July 31, 2018 at 1:58 pm
Rosco - Tuesday, July 31, 2018 10:27 AMHi All,I'm wondering if anyone has encountered the above scenario before?
I have 6 TDE encrypted databases on the above cluster (my TDE implementation utilises an Azure key vault and the SQL Server Connector functionality).
When I failover from node 1 to node 2 all of my TDE encrypted databases remain in a recovery pending state, the non-encrypted DBs are available.
If I fail back to node 1, all DBs pass the startup DBCC Checkdb ok and everything looks fine.
I have reinstalled the connector on node 2, and even reinstalled SQL on that node to no avail.
Has anyone got any experience of this that could help me resolve my issue please?
Many thanks,Ross
Check the error log as there be additional information in the SQL Server error log.
Sue
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply