Log backup for database on a secondary replica failed because a synchronization point could not be established on the primary database

Hi All,

It's been a long time since I blog posted hence thought of sharing one small issue which I noticed as part of testing on my laptop.

consider the below scenario:

1) create a database on the ALWAYS ON Primary replica
2) Take Full Backup of the Database
3) Add the Database to ALWAYS ON using Automatic seeding or even join only (as i restored only full backup while using join only)
4) Now try to perform Log backup on to the database that has been added on the secondary server.

you will get the below error message:

Msg 35294, Level 16, State 5, Line 3

Log backup for database "AGTEST1" on a secondary replica failed because a synchronization point could not be established on the primary database. Either locks could not be acquired on the primary database or the database is not operating as part of the availability replica. 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.

Msg 3013, Level 16, State 1, Line 3
BACKUP LOG is terminating abnormally.

This is a strange issue and seriously it took some time to identify this.  To overcome for now we need to take LOG backup on the primary replica at least once post that you will not see that message.

This is not a great article however I feel that every small thing would help to us to learn better.

Comments