In this blog post, let’s learn about the error message “35296 – Log backup for database “%.*ls” on secondary replica failed because the new backup information could not be committed on primary database. Check the database status in the SQL Server error log of the server instance that is hosting the current primary replica. If the primary database is participating in the availability group, retry the operation.” in Microsoft SQL Server, the reason why it appears and the solution to fix it.
SQL Server Error Message
35296 – Log backup for database “%.*ls” on secondary replica failed because the new backup information could not be committed on primary database. Check the database status in the SQL Server error log of the server instance that is hosting the current primary replica. If the primary database is participating in the availability group, retry the operation.
Reason for the Error
To be update soon…
Solution
To be update soon…