MS SQL Server Backup

Configure MS SQL Server differential backup in TrueSecure Backup by following these steps:

Start the backup wizard by clicking the MS SQL Server button on the Home tab:

In the next step, you select whether you want to perform a Local or Cloud Backup or a mix (Hybrid Backup). In this guide, we will choose the cloud backup destination.

Choose your specific storage location (Amazon S3 in this example): If necessary, you can add a new storage account by clicking the corresponding link ‘Add new Storage Account.’

Provide the name for this backup plan and proceed. At this point, you need to connect TrueSecure Backup to the target SQL instance. TrueSecure Backup will verify the necessary permissions. If you have created a separate backup account in MS SQL Server, use the Authentication menu to specify its credentials.

If you Select the first checkbox you will have go to your database and grant the permission like the picture below.

If you select the second checkbox you can skip the above step and move onward no changes need to be made to the SQL database.

Select the databases you want to protect. We choose "DataFileIronSteelRetail" in this example.

If you select the option backup all database then it will backup all of the database available if you select the second option backup all user database then all user related database will be uploaded.

On the Compression and Encryption Options screen, you can change additional processing options, such as data compression and encryption, or set cloud-specific options.

Note: If your current SQL Server version/edition supports the compression feature, TrueSecure Backup will use the native SQL Server compression during a backup's processing. Otherwise, TrueSecure Backup will use a custom compression algorithm.

Specify the Retention Policy for your backup to save only the necessary number of copies. This helps to prevent you from running out of space or paying more than necessary when using cloud storage. You can set the expiration time for any backup copy and store the least amount of full copies.

The scheduling step allows you to create a “run once” job or configure one of the available schedule templates. In most cases, we suggest using a Recurring (predefined templates) schedule that already includes a set of full, differential, and log backups, which you can modify depending on your needs. If that schedule is not what you are looking for, check Recurring (advanced schedule) and create your own template. It is also a good idea to check the Run missed… option, which will perform missed backup jobs of your server that were not available at the time of a backup run.

Specify recurrence details from a set of templates. In the example below, we configure weekly full backups, daily differential backups, and transaction log backups every hour.

Set the rest of the advanced options, such as pre/post actions and notifications settings, and complete the backup plan creation.

Summary

Differential backup is a must-have part of any SQL Server database data protection plan. It allows you to simplify the data restoration process and keeps backups smaller than generic full backups.

All of the tools needed to perform a differential backup are built into SQL Server, but they require you to write scripts and perform manual configuration. If you would like to simplify your backup configuration, as well as use cloud or hybrid backup storage