- Overview
- Connecting to an SQL Instance
- Backing up Microsoft SQL Databases
- Select SQL Databases to Backup
- Edit the Plan for this Backup
Overview
Macrium Reflect LTSC Server Plus can perform granular backup and recovery of Microsoft SQL databases. This is ideal for environments where multiple SQL databases exist on the same volume, meaning that a disk image would not be a suitable way to backup and recover individual databases without impacting other databases.
Macrium Reflect LTSC Server Plus supports SQL Server 2005 and above. All versions of Microsoft SQL Server and Microsoft SQL Server Express are supported. SQL Server 2000 and earlier are not supported.
Connecting to an SQL Instance
First, to be able to backup SQL databases, Macrium Reflect LTSC Server Plus must connect to the local SQL instance. To do this, select 'Manage SQL Logins' under the 'SQL Server Tasks', on the 'Create Backups' tab.
The window that opens will display the SQL instances that have been found on the local computer:
Select the relevant instance, then select 'Connect'.
In the window that opens, enter the SQL Server or Windows credentials, the 'Authentication' dropdown box can be used to select the authentication method:
If the authentication completes successfully, the SQL instance will be shown as 'Connected':
This window can now be closed.
Backing up Microsoft SQL Databases
Now that Macrium Reflect LTSC Server Plus has connected to the SQL instance, a backup of the relevant SQL databases can be created.
First, select 'Backup SQL Databases' under the 'SQL Server Tasks', on the 'Create Backups' tab.
Select SQL Databases to Backup
In the window that opens, all the databases associated with the connected instances of SQL will be dispalyed. Using the checkbox next to each SQL database, select the database(s) that will be backed up.
The destination for the SQL backup is specified at the bottom of this page. The destination can be a local drive or network share specified in UNC format (\\Server\Share).
Alternative Locations
The 'Alternative Locations' option can be used to specify alternative locations for the image destination. If the primary backup location is not available when the image starts, each location specified will be tried in sequence until an available destination is found. This can be used to easily configure drive rotation, enabling images to be taken offsite for redundancy and provide extra resiliency if the primary destination is not available.
Alternative locations can be specified and added to the list of locations using the 'Add to list' button. The destinations will be attempted in the order they appear in this list. The order the destinations are attempted can be changed using the 'Up' and 'Down' buttons or removed from the list with the 'Remove' button.
Once all the alternative destinations have been specified, select 'OK' to complete the window.
Edit the Plan for this Backup
On the second page of the wizard, a schedule can be created to automatically create new backups of the SQL database(s), ensuring that any changes to the database(s) have also been backed up.
There are three types of SQL backup schedule that can be specified using the 'Add Schedule' button:
| Backup Type | Description |
| Full | A full backup of the whole SQL database. |
| Differential | A differential backup will include all of the transaction logs that have been created since the previous full backup. |
| Log | Backs up the transaction logs that have been created since the previous backup of any type. |
In the window that opens, the 'Frequency' and 'Options' for the schedule can be changed. The list of options on this page will change depending on the 'Frequency' that has been selected:
 |
 |
 |
 |
 |
 |
Selecting 'Conditions' will display additional options that can be used to determine whether the task should run:
| Option | Description |
| Run task as soon as possible after a scheduled start is missed | If a scheduled start is missed, e.g. due to the system being powered off, the scheduled task will start when it's next possible. |
| Start the task only if the computer is on AC power | The task will not start if the computer is on battery power. |
| Stop if the computer switches to battery power | If the computer switches to battery power during the clone, the clone will stop. This option is only available if Windows Task Scheduler is selected in the 'Schedule Settings'. |
| Wake the computer to run this task | When selected, the system will attempt to wake from sleep to run the scheduled backup. |
Define Retention Rules
Macrium Reflect retention rules provide a powerful and flexible way to manage the lifetime and storage space used by your backups.
When SQL backups are created, log, differential, and full backups are stored in the same backup container file. The example below shows one of these container files:
Viewing this backup in the 'Existing Backups' tab shows the full, differential, and log files contained inside the MRSQL backup file:
Read more about restoring these backup files here.
The SQL backup retention rules are used to specify how many of these container files should be retained at any one time.
These rules can be applied based on the number of MRSQL backup files or the age of the backup files. Additionally, the 'Run the purge before backup' checkbox can be used to apply the retention rules before the in-progress backup begins.
SQL Database Backup Summary
The final page of the wizard shows a summary of the SQL backup that is about to be performed and the settings that were specified. We recommend double-checking the settings that have been selected. The '< Back' and 'Next >' buttons can be used to navigate through the wizard and make changes as necessary.
'Advanced Options' can be selected on any page of the wizard to specify advanced options for the image that will be performed. Read more about the available options here.
Backup Save Options
After selecting 'Finish', the 'Backup Save Options' window will be displayed with options to 'Run this backup now' and 'Save as a Backup Definition File'.
If 'Run this backup now' is left unchecked, the backup will run at the next scheduled start time, if a schedule was specified, or can be launched manually on the 'Definition Files' tab:
'Save as a Backup Definition File' must be left checked if a schedule has been specified. This option can still be left checked if a schedule has not been specified to make manually running the same backup again in the future easier, as shown in the screenshot above.