After a network issue, two availability groups vanished from SSMS. Here is how the logs explained an availability group missing or deleted automatically.
SQL SERVER – FIX : Msg 35295, Level 16 – Log Backup For Database ‘DBName’ on a Secondary Replica Failed
During load testing, a log backup on a secondary replica failed with Msg 35295 because the last backup LSN was ahead of the redo LSN. Here is why.
SQL SERVER – How to Apply Patch in AlwaysOn Availability Group Configuration?
A Patch in AlwaysOn Availability Group needs a sequence matched to the topology. I start this two-replica example with the secondary.
SQL SERVER – Migrating AlwaysOn Availability Group to New AD Domain
The steps I gave a client for migrating AlwaysOn Availability Group replicas from an old AD domain to a new one after an acquisition, node by node.
SQL SERVER – UpdateHADRResource – Failed to version-copy file – Exception data is: System.IO.IOException
A SQL Server patch on a cluster failed at UpdateHADRResource with System.IO.IOException, failed to version-copy hadrres.dll. Here is the cause and the fix.
Do You Need an Availability Group? Matching RPO and RTO to a Feature
Match RPO and RTO to backups, log shipping, failover clusters, or availability groups, then test the full service recovery path.
SQL SERVER – AlwaysOn AG (Availability Group) and TDE Error – Please Create a Master Key
A TDE enabled database would not synchronize in an AlwaysOn availability group, and ERRORLOG said please create a master key. Here is what I found.