• About Me
  • #SQLHelp
  • SQLTools
  • AutoMon
  • jDBA
  • Tuning
  • Training
  • Oracle
  • Forum
  • Freelance
  • Disclaimer and copyright
Sql server Blog Forum

Helping SQL server DBAs and Developers

  • About Me
  • #SQLHelp
  • SQLTools
  • AutoMon
  • jDBA
  • Tuning
  • Training
  • Oracle
  • Forum
  • Freelance
  • Disclaimer and copyright
  • About Me
  • #SQLHelp
  • SQLTools
  • AutoMon
  • jDBA
  • Tuning
  • Training
  • Oracle
  • Forum
  • Freelance
  • Disclaimer and copyright
  • AlwaysON

    How to solve the LSN mismatch issue in alwayson mirror SQL server The mirror database has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database

    August 31, 2016

      There are many times, we face the LSN mismatch issue in alwaysON and other HA technologies. It is a bit hard to find the missing transaction log backup to apply. Since, there are hundreds of thousands log generated, depends on the transaction log frequency and it can be run in any secondary alwaysON database server. Think about “the VLDB” and “the backup is in different data center” and database are out of sync in DR site because of LSN mismatch. For VLDB 8 TB database, we cannot take a full or differential backup to fix this. Since, it will take more and more time. Backup is in different data center…

    Read More
    Muthukkumaran Kaliyamoorthy 12 Comments

Search box

Advertisements

Categories

  • AlwaysON
  • AutoMon
  • Azure
  • Backup/Restore
  • Basics for freshers
  • DBA
  • Docker
  • DR/HA
  • Indexes
  • Internals
  • Junior DBA
  • Microsoft
  • Oracle
  • Performance
  • PowerShell
  • Questions
  • Scripts
  • SQL party
  • T-SQL
  • VLDB

Archives

Top SQL server blogs

  • Adam Machanic
  • Amit Banerjee
  • Brent Ozar
  • Gail Shaw
  • Grant Fritchey
  • Paul White
  • Pinal Dave
  • SimpleTalk
  • Sqlblog
  • SQLskills

Top Posts & Pages

  • AlwaysON database NOT SYNCHRONIZED and RECOVERY PENDING
    AlwaysON database NOT SYNCHRONIZED and RECOVERY PENDING
  • AlwaysON database not synchronizing suspect mode
    AlwaysON database not synchronizing suspect mode
  • Test connection failed because of an error in initializing provider. Oracle client and networking components were not found
    Test connection failed because of an error in initializing provider. Oracle client and networking components were not found
  • Login failed for [SQLSTATE 28000] (Error 18456) the step failed
    Login failed for [SQLSTATE 28000] (Error 18456) the step failed
  • The Cluster service failed to bring clustered service or application completely online or offline. One or more resources may be in a failed state.
    The Cluster service failed to bring clustered service or application completely online or offline. One or more resources may be in a failed state.
  • SQL server daily health check DBA script
    SQL server daily health check DBA script
  • How to find slow running T SQL query
    How to find slow running T SQL query
  • How to use Blitz Brent Ozar First Responder Kit
    How to use Blitz Brent Ozar First Responder Kit
  • How to solve the LSN mismatch issue in alwayson mirror SQL server The mirror database has insufficient transaction log data to preserve the log backup chain of the principal database.  This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database
    How to solve the LSN mismatch issue in alwayson mirror SQL server The mirror database has insufficient transaction log data to preserve the log backup chain of the principal database. This may happen if a log backup from the principal database has not been taken or has not been restored on the mirror database
  • TempDB database is Full and Optimization
    TempDB database is Full and Optimization
Savona Theme by Optima Themes