1

Can I take a log backup manually in Primary replica when all my databases are synchronized with secondary replicas in AOAG?

Will it break my Log sequence for Synchronization?

In AlwaysON AGs do we take T-Log backups for Synchronization manually or do they happen over the wire (End points 5022)? Can some one please simplify this process for my understanding?

I would like to understand will it affect my AOAG with LSN Mismatch?

1

You can manually take transaction log backup on any replicas of AG. For primary and secondary replica you can take normal T-log backup, only copy_only full backups are possible on secondary replica. I would suggest to take T-log backup from secondary replica this will put less load on primary replica and would also not affect peak time I/O.

In any case log backup chain would NOT be disturbed just make sure that when you take T-Log backup you do not delete it but store it like you do for your normal backups so that you can use it in case of disaster.

In AlwaysON AGs do we take T-Log backups for Synchronization manually or do they happen over the wire (End points 5022 ) . Can some one please simplify this process for my understanding ?

T-Log backup has no relation with synchronization, yes communication happens via endpoints and commit handshake happens via endpoints. For more details read Always On Series

  • 3
    "secondary replicas you can only take copy_only" is incorrect. You can only take regular log backups at any replica: See: docs.microsoft.com/en-us/sql/database-engine/… . And copy_only log backups are not really useful, as you can never guarantee that you have an intact log chain. – David Browne - Microsoft Jun 26 '17 at 19:11
  • @DavidBrowne-Microsoft Yep thanks for correcting, indeed I missed this. I will correct it – Shanky Jun 27 '17 at 4:28

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.