Availabiliity group replica error
Question
Saturday, September 17, 2016 5:13 PM
On the replica secondary the under Availability Databases the database has a yellow yield icon on the database. When you right click the database it says "Joni to Availability Group". When I chose this it errors out with the below error.
Failed to join the database 'DATABASE' to the availability group 'grpMain' on the availability replica
The mirror database, "DATABASE", has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database. (Microsoft SQL Server, Error: 1478)
Alan
All replies (3)
Sunday, September 18, 2016 11:11 AM ✅Answered
yes follow what above said, you might be missing the pre-requisites-
Prerequisites
You must be connected to the server instance that hosts the secondary replica.
The secondary replica must already be joined to the availability group. For more information, see Join a Secondary Replica to an Availability Group (SQL Server).
The secondary database must have been prepared recently. For more information, see Manually Prepare a Secondary Database for an Availability Group (SQL Server).
Ref-https://msdn.microsoft.com/en-us/library/ff878535.aspx
Also if you still unable to perform through GUI then try with T-SQL and see if that works.
The error clearly says that "has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database".
Regards, S_NO "_"
Wednesday, September 21, 2016 11:28 AM ✅Answered
The mirror database, "DATABASE", has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database. (Microsoft SQL Server, Error: 1478)
Alan
That is simple and it means the secondary replica cannot be initialized as it cannot get complete log information because you did not restored all log files or you made some mistake.
Cheers,
Shashank
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
Sunday, September 18, 2016 5:07 AM
Please check this below links , This happens very rarely
Issue: Replica Unexpectedly Dropped in Availability Group
FIX: Error 1478 when you add a database back to the AlwaysOn availability group in SQL Server