Preparing a demo, I hit Msg 3231: media formatted for 1 media family, but 2 Media Families are expected. Here is what causes it and how to fix it.
Identify SQL Server Version From a Backup File
To identify SQL Server version from a backup file, run RESTORE HEADERONLY and read DatabaseVersion and SoftwareVersionMajor. This post makes a demo backup, reads its header, and maps the numbers to products. It also shows how to compare the backup with your server in T-SQL, and why a header sometimes fails to read on an older server.
SQL SERVER – Fix Error 3271: A nonrecoverable I/O error occurred on file. The remote server returned an error: (404) Not Found
Error 3271 during backup to URL has many causes. After the 403 and 400 versions, here is what causes the (404) Not Found error and how to fix it.
SQL SERVER – Fix Error 3271: A nonrecoverable I/O error occurred on file. The remote server returned an error: (403) Forbidden
A reader’s backup to URL failed with Error 3271: the remote server returned an error: (403) Forbidden. Here is how I reproduced it and the easy fix.
SQL SERVER – What is Tail-Log Backups?
Tail-Log Backups capture the end of an available transaction log before a restore. I assess them within the intended recovery chain.
SQL SERVER – FIX: Msg 3009 – Could Not Insert a Backup or Restore History Detail Record in the MSDB Database
A backup finished but raised Msg 3009: could not insert a backup or restore history detail record in msdb. Here is why, with steps to reproduce it.
SQL SERVER – Fix Error – Restore Operation Failed for Database Due to Insufficient Memory in the Resource Pool ‘Default’
SQL SERVER – Fix Error – Restore Operation Failed for Database Due to Insufficient Memory in the Resource Pool ‘Default’