Post reply

failover of the AG group to another stand by node which has asynchronous-commit‌

  • July 24, 2017 at 8:35 am

    #339126

    Hi,

    Before we initiate failover of the AG group to another stand by node which has asynchronous-commit, do we need to follow up any step say ensuring that active logs are not there so that it can initiate a v smooth failover or any other factors?


    Asynchronous-commit availability mode does not support automatic failover. For automatic failover, use synchronous-commit mode.

    Thanks.

  • July 24, 2017 at 9:00 am

    #1952383

    You need to change it to Synchronous Commit and wait for it to catch up before you do the failover if you want to fail over with no data loss.

  • July 24, 2017 at 9:05 am

    #1952387

    In terms of matching user permissions, how it is possible without doing any failover? For exa, one can create a job to transfer login and users but in order to map the security we need to do have the database in r/w mode.

    Any other wait out or best practice?

    Thanks.

  • July 24, 2017 at 9:06 am

    #1952389

    I usually do it when I'm setting up the environment, before it goes into Production.

  • July 24, 2017 at 9:16 am

    #1952396

    But over a period new login accounts will be created/ old accounts will be dropped.

    Thanks.

  • July 24, 2017 at 9:18 am

    #1952402

    You're welcome, by the way ;).

    Yes; if you use Windows Authentication you don't have issues with that.

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply