Sunday, 11 December 2016

Managing SharePoint: Truncating the Log file on the Always On secondary

Had an issue where the backup had stopped running and the transaction logs were full

How to resolve this is an always on environment?

  1. On the Primary: Set the recovery model of the Config DB to Simple
  2. Full backup
  1. Remove from Availability group - now the configDB exists on Primary but it is not synching to the Secondary

  1. On the Secondary: Delete the config DB

Did you just say delete the config DB??? - Yes, it's on the secondary. It's ok. The Primary isrunning and not in the AG

  1. On the Primary: Shrink the Log files to 1,024MB - just the logs
  2. Add the Config DB back to the AOAG

And all was well again - time for a coffee

No comments:

Post a Comment

SharePoint Information Architecture Diagram

Here is the template I use for Information Architecture designs. It's built using Mindjet and I flesh the nodes out with the low level d...