Hi Experts,
I have a doubt on Always on Availability groups. While trying to add(i.e. JOIN only) a database to AG. It was throwing below error.
I tried to check the backup history of that database. There were 10 log backups taken to a network share since last FULL backup. Full backup was already restored with no recovery on secondary.
Now, instead of copying those 10 log backups , I took a fresh local differential backup and tried to restore it with no recovery option. restore was successful. However, when I tried to add the database to AG from Primary replica , it again throws the same
above error message. I took another differential backup, and tried restoring with no recovery and it back to AG. Still same error message.. yes I do agree there are some incoming connections to the database on Primary (even before adding to AG). Finally,
I tried to take a fresh log backup on primary, restored with no recovery on secondary. now performed the JOIN only to AG. This way, I was able to add the database AG.
Now, my question is, Is there any difference in restoring Differential and log backup in this scenario ?
I just went for differential to avoid copying/restoring so many log backups. I have observed this in more than 2 times in our environment and that is the main reason why I want to know more about this. LOG BACKUP restore always worked.
Thank you
Sam