Home » Blog » Topic » Alwayson is out of sync

Alwayson is out of sync

Lincoln Burrows ~ Modified: June 9th, 2016 ~ ~ 1 Minute Reading

Home › Forums › Alwayson is out of sync

Viewing 14 posts - 1 through 14 (of 14 total)
  • Author
    Posts
  • June 9, 2016 at 12:09 pm #2230 Score: 0
    Lincoln Burrows
    Moderator
    16 pts

    In my production environment, SQL Server 2012 enterprise edition installed with alwayson configured, sometimes due to heavy transactions, log files increases rapidly due to which alwayson is out of sync for some hours but it automatically comes back in sync after there is lesser transaction, is this a network issue or alwayson’s drawback? Why does it take longer time for the transactions to get transferred on alwayson dr?

    June 13, 2016 at 11:57 am #2239 Score: 0
    Eddie Thwan
    Moderator
    44 pts

    Is your log file set to auto growth?

    June 14, 2016 at 12:10 pm #2252 Score: 0
    Stephen West
    Moderator
    4 pts

    Can you check the SQL logs and also share db configuration

    June 15, 2016 at 12:13 pm #2265 Score: 0
    Michael Scofield
    Moderator
    20 pts

    Check the performance of the disks in the mirror.

    June 16, 2016 at 12:46 pm #2267 Score: 0
    Lincoln Burrows
    Moderator
    16 pts

    Yeah autogrowth is set on database, DD size is 5TB & 400GB is provided to SQL Server

    June 17, 2016 at 12:47 pm #2272 Score: 0
    Kerry Morris
    Moderator
    33 pts

    Increase the Auto grow size of log file accordingly for few days and can observe it

    June 18, 2016 at 12:39 pm #2278 Score: 0
    Lincoln Burrows
    Moderator
    16 pts

    There was no issues with autogrowth my doubt is that why does the alwayson lags for such a long after log files increase heavily

    June 20, 2016 at 12:10 pm #2284 Score: 0
    Kerry Morris
    Moderator
    33 pts

    Is this a network issue or some cluster issue?

    June 23, 2016 at 1:07 pm #2310 Score: 0
    Andrew Jackson
    Moderator
    1 pt

    I think when log file grows many times in small time take extra i.o. and locks to add new extents. This may result in delay for entire system concurrent processes while we have the same setup. My options is without demand of other resources so. As a DBA we can try. Else network issues can be verified in parallel in other way during low peak hours.

    June 24, 2016 at 11:21 am #2314 Score: 0
    Lincoln Burrows
    Moderator
    16 pts

    In low peak hours alwayson doesn’t lag, but when the log file increases abruptly alwayson goes on lagging then it takes some time to get back in sync, this itself doesn’t allow to shrink log which is occupying large log space

    June 27, 2016 at 11:14 am #2332 Score: 0
    Henry Davidson
    Moderator
    31 pts

    Try to change replica to synchronous and check once

    June 28, 2016 at 12:57 pm #2337 Score: 0
    Dexter Morgan
    Moderator
    38 pts

    For best option increase the log file size

    June 30, 2016 at 1:32 pm #2353 Score: 0
    Lincoln Burrows
    Moderator
    16 pts

    There are already six log files present with sufficient space provided on both prod & always on dr

    July 4, 2016 at 12:40 pm #2379 Score: 0
    Andrew Jackson
    Moderator
    1 pt

    Yes, it is a AlwaysOn drawback. SQL Server Replication uses very high bandwidth. I think its best to use log shipping for a DR solution, because you can use DR db in standby mode & it uses very low traffic.

  • Author
    Posts
Viewing 14 posts - 1 through 14 (of 14 total)
  • You must be logged in to reply to this topic.