Log Shipping Failover
I have set up log Shipping with Cluster. In this scenario I want to simulate a situation when the whole cluster becomes inaccessible. My Steps for failover will be
1) Copy and restore the unapplied t logs with Recovery to put the database online 2) Since the Primary in not accessible so I cannot take a t log and put it in restoring state 3) Disable the above two jobs 4) Change the application connection strings to the new primary.
My confusion arises what should I do when the Old Primary comes live again 1)Should I take the t log back up and put the database in restoring state so that I can set it up as a secondary and then failover to make it primary.
If that’s the case then wont the log shipping fail if I want to configure without initializing(since I have the database in restoring state) as it will look for the last t log which I Have not applied to my new secondary as the primary was not accessible during failover.
Thanks in advance