Mirroring- How to start the endpoint (mirror db) if not able to recover transaction log backup from the primary?
I have seen the below youtube video to know how to recover the DB during failover scenarios. Regarding this, I have gone through some articles too.
https://www.youtube.com/watch?v=HyGzgzRQCcI
If you want to use the mirror database you need to have transaction log backup from the primary server. If you have multiple transaction log backups then you need to restore one by one in mirror server to activate. How to start the endpoint (mirror DB) if not able to recover transaction log backup from the primary?
Who is Participating?
Experts Exchange Solution brought to you by
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Experts Exchange Solution brought to you by
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialIt's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
You can follow the steps as described here http://sql-articles.com/articles/high-availability/how-can-i-bring-mirror-database-online-after-principal-server-is-down/ based on SQL Docs from https://docs.microsoft.com/en-us/sql/t-sql/statements/alter-database-transact-sql-database-mirroring?view=sql-server-2017 however...
NOTE/CAUTION: This should be done only under severe Principal Server issues and assuming the data loss since last synchronization. Please do not attempt to test any of these in a production Environment as data loss is irreversible.