MS SQL Backup Requirements
When backing up MS SQL using N-able Backup, there are several requirements that must be met.
- Using Backup Manager, you must back up at minimum a single database
- The Backup Manager must be installed on the same MS SQL server that you want to back up
- There must be sufficient free space in the VSS Shadow Copy storage area, as MS SQL backups depend on VSS Snapshots
- If the MS SQL Server has the Azure AD Connect feature enabled, we recommend running a test backup.
- We highly recommend setting the database to the Simple Recovery Model before starting backups
It is not possible to exclude certain tables or files from a backup selection.
When a backup session is completed, snapshots are automatically deleted.
MS SQL Server Configuration: Azure AD Connect
If the backup session fails with a VSS error, this may be due to an Azure AD Connect upgrade released in October 2017. If this version is of use on the device, ensure you update to the highest version.
You can also resolve the issue by changing the "Log On" account for the SQL Server VSS Writer service from "Local System account" to a domain administrator account. To learn more about possible solutions, see the help articles listed below.
- A COM+ application may stop working on Windows Server 2008 when a user logs off (Microsoft support article)
- MS SQL backup is failing with VSS error 0x800423f4 error when Azure AD connect feature is enabled on the server
Simple Recovery Model
Under this model, inactive virtual log files are automatically removed after each checkpoint (or shortly after it). This saves space and helps avoid unnecessary processing.
Set the model selection by:
- Start the SQL Server Management Studio
- In the Object Explorer, right-click a database and then select Properties from the context menu that opens
- In the Recovery model list, select Simple
The simple recovery model makes it possible to restore a database only to the end of the most recent backup. We recommend scheduling backups frequently enough to prevent the loss of recent changes.
If you choose to back up a database under the full recovery model, you are responsible for truncating the logs.