Quick Maintenance & Backup for MS SQL
Backup creation settings

This step of the wizard called "Backup creation settings” allows you to specify the parameters of the backup creation process for this maintenance policy: folder, backup naming rules and the storage period. Backups are created by corresponding Tasks included into QMB Jobs. That is why the type of a backup and the frequency of its creation are defined by a particular QMB Job of in a policy and its schedule.

Recovery model - recovery model applied for the databases of a maintenance policy. Changes to the model are made with a wizard after creating or editing the policy.

The database recovery model defines the date to which the data will be restored to in case of an accident. For instance, the Full recovery model implies that the data can be restored virtually to the instant when the system crashed or any other preceding moment, given that there is a full backup and the necessary backups of the transaction log. When the Simple model is used, data can only be recovered to the date of the most recent backup. See more details https://msdn.microsoft.com/en-us/library/ms189275.aspx 

Backup folder – a full path to a folder on the SQL server that will contain database backups created by the maintenance policy. You need to specify an existing folder.

If you use the Ola Hallengren solution for database maintenance, the specified folder will contain subfolders called Server name\Database name that will store corresponding backup files.

Create subfolders - this option allows you to create backups in different subdirectories. For example, for different databases. The hierarchy and naming rules for subfolders are given in the text template. In the template text you can specify placeholders (see below for a description of what placeholders are). This option is not available for Ola Hallengren policies.

Naming of backups – this parameter sets the backup file naming rules. This option is not available for Ola Hallengren policies. The following placeholders can be used in the string. They will be replaced by corresponding values in file names:

%instance% Name of the SQL server instance
%weeknumber% Week number. Sometimes, the week number in the names of backup files is used for sorting
%database% Database name


Backup type: Full, Diff or Log


Date in the yyyymmdd format


Date and time in the yyyyddmm_hhmmss format


Date in the ddmmyyyy format


Date and time in the ddmmyyyy_hhmmss format


Date of the first day of the week in the ddmmyyyy format (Monday)


Date of the last day of the week in the ddmmyyyy format  (Sunday)


The marker is replaced by the _cmp string if shrinking of backups is enabled on the SQL server. If the server does not support shrinking or this parameter is disabled, an empty field is inserted.
An SQL server can save an arbitrary number of backups to one file. The number and the size of backups depend on the value of the Naming of backups parameter. That is, if %timestamp% is used in a file name, each backup will be saved to a separate file. There will be more files of a smaller size. If %date% is used, all backups made during any one day will be saved to a single file.
We recommend saving each backup to a separate file, i.e. using the %timestamp% marker.

Create an XML Restoration Plan - when selecting this option, the program will automatically create an XML restoration plan immediately after the backup has been successfully created. Enabling this option allows you to keep your XML restoration plan up-to-date. In this field you must specify the file name of the XML restoration plan.

Delete old backups after their expiry – if you enable this option, you will need to specify the storage period for database backups. 

In order to remove archive backups, the Delete old backup files  task must be enabled in the QMB Job. Otherwise, outdated archive backups will not be deleted.

Full backup creation strategy – informs the program when to create backups. The parameter does not affect the creation of full backups (this is defined by tasks in the QMB Jobs of a maintenance policy). The parameter only affects the list of storage duration units. That is, if a full backup is created once a week, the storage duration cannot be set in days. Otherwise, the sequence of backups will be broken – for example, when a full backup is deleted (as an outdated one), while the disk still has backups of logs and differential backups that cannot be used for restoring data without a full backup.

Storage period for backups – a period in days, weeks or months. Backups are always stored for one full period to avoid breaking the sequence of backups.

Copy new and modified  backup files - this option enables you to specify settings for additional backup copying to a networked or local folder. If the policy does not have saved settings for copying files, then during setup a form will open called Settings for Copying.

New and modified backup files are copied with the task Backup Copying.  This task should be included in one or several QMB jobs, depending on the desired frequency of copying. When you create a maintenance policy from a template, the task is included in a nightly and a weekly job.


See Also

User interface

General Information