One of my clients migrated to SQL Azure Managed Instance and contacted me for an interesting situation. Let us resolve Restore Error.
Running DBCC CHECKDB on a Restored Copy Instead of Production
Run CHECKDB on a restored copy to validate a recoverable backup, retain the full check output, and understand what remains untested.
Immutable Backups: Keeping a Copy Ransomware Cannot Delete
Design immutable backups with enforced retention, separate storage access, offline recovery material, checksum checks, and restore tests.
SQL SERVER – Error 35296: Log Backup for Database “SQLAuthority” on Secondary Replica Failed Because the New Backup Information Could Not be Committed on Primary Database
Error 35296: log backup on a secondary replica failed because the new backup information could not be committed on primary. Here is the cause I found.
SQL SERVER – What is Wait Type Parallel Backup Queue?
Only official documentation which I could find was about wait statistics related to Parallel Backup Queue is very little available online.
Availability Group Restore Error When You Add a Database
The availability group restore error appears when automatic seeding and a manual restore both fill the same secondary. The post explains the cause, shows read-only checks for the seeding mode and the replica roles, and gives the fix with its undo.
COPY_ONLY Full Backup Size: What Differs Between Always On Replicas
A COPY_ONLY full backup of the same database can have a different size on the primary and the secondary replica of an Always On group. This post reads the log pages in the backup messages, shows them on a standalone database and explains how to compare backups fairly. It also covers what a restore needs.