Select Database(s)

SQL Server Instance Name: This field is a non-editable name of the SQL Server Instance for which the backup needs to be configured. If you want to change the SQL Server instance you need to go back to the SQL Server Connection Properties UI and choose the instance name again.

Select Database(s): Select the database name that needs to be backed up.

SQL Server databases are classified as Full Recovery, Bulk-Logged Recovery and Simple Recovery Models. When a particular Recovery Model is selected, the databases in the SQL server falling under that Recovery Model will be listed for backup. You can select all of them or individually select the ones you want to backup.

If a database is included in a backup schedule, then that particular database cannot be selected in another backup schedule; as the data might get inconsistent when backed up across two different backup schedules. Similarly, a database should not be configured with more than one backup software for the same reason. Select All Databases for this schedule

If "Select All Databases for this Schedule" option is chosen, it will include all the databases present in the SQL server. If a new database is later added to the SQL Server, it will be automatically included in this backup schedule.

Select All Full Recovery Model databases

If "Select All Full Recovery Model databases" option is chosen, it will include all the databases with Full Recovery model from the SQL Server. If a new Full Recovery model database is later added to SQL Server, it will be automatically included in this schedule.

The Full Recovery Model provides extensive backup and restore capabilities. Full, differential and Transaction Log backup of the databases are supported.

To restore a Full Recovery Model database, a full backup has to be first restored. On top of the full backup, differential and/or Transaction Log backups could be restored to recover the database to the latest backup state.

Select All Simple Recovery Model databases

If "Select All Simple Recovery Model databases" option is chosen, it will include all the databases with Simple Recovery Model from the SQL Server. If a new Simple Recovery model database is later added to SQL Server instance, it will be automatically included in the backup schedule.

The Simple Recovery Model provides the simplest form of backup and restore. Full or differential backup of the databases could be done. Transaction log backups are not available for databases belonging to this model. To restore a Simple Recovery Model database, a full backup has to be first restored. On top of the full backup, differential backups could be restored to recover the database to the latest backup state.

Select All Bulk-Logged Recovery Model databases

If "Select All Bulk-Logged Recovery Model databases" option is chosen, it will include all the databases with Bulk-Logged recovery model from the SQL Server. If a new Bulk-Logged recovery model database is later added to SQL Server, it will be automatically included in the backup schedule.

capabilities. Full, differential and Transaction Log backup of the databases are supported. However, compared to the Full recovery model, which logs all transactions, the bulk-logged recovery model minimally logs bulk

operations. Therefore, recovery is possible only to the end of a transaction log backup when the log backup contains bulk changes.

Like Full Recovery Model database, to restore a Bulk Logged Model database, a full backup has to be first restored. On top of the full backup, differential and/or Transaction Log backups could be restored to recover the database to the latest backup state.

Let me manually choose databases

If "Let me manually choose databases" option is chosen, then any databases can be selected for backup irrespective of the recovery model they belong to.

If a database does not support Differential/Transaction Log backups, then that Differential/Transaction Log backup will be skipped for that database and the error message will be reported in backup report.

The database 'tempdb' need not be configured as part of any of the above mentioned schedules. However, if it was configured for a backup, it will be skipped internally when the backup is scheduled. 'tempdb' is used internally by SQL Server just for saving temporary data.

Step 3: Set Basic Configuration

Backup Type

Same Machine - You can backup this client machine to a drive attached to this client machine for the following two purposes:

1. When large amount of data has to be backed up, it might take significant amount of time to transfer all the data to a remote backup server over WAN/Internet. You can take the backup to a local external drive connected to the client machine and then physically move the external drive to the backup server location to migrate the data into the backup server. In such cases, you can select the backup type to be 'Same Machine'. Once the data is migrated to the backup server using the Server Side Seed Backup Migration, you will have to perform Seed Backup Migration (under Settings -> Seed Backup Migration) in the client machine to make it to run its backups to the remote server directly thereafter.

2. If you want to keep a local backup copy that you want to restore quickly when needed.

Local Backup location: Enter the location/directory path where the backup is to be stored in the same machine. This location should be accessible to StoreGrid process and should have enough free disk space for the backup data. You can copy data from this location to the backup server as seed backup data. Or, you can leave the backups in the local drive if you want to maintain a local copy of the backup that you can quickly restore.

NOTE: Deleted File Retention policies and Time Based version file Retention policy will not apply for a local backup. Only Version-Based Retention is supported for a local backup schedule. The Retention policies configured for this backup schedule will work only if the backup data is migrated from the local backup server/external drive into a remote backup server (seed backup).

Remote Server - Select this option if you want the backup data to be transferred to a backup server directly when the backup schedule runs.

Also keep a copy locally (optional) :

Enabling this option will backup the data to the backup server and also keep a copy of the backup data in a local location. First the data will be backed up to the backup server and on completion of the backup, the copy of the backed up data will be saved in the specified local location. The local copy will provide for faster restores and redundancy. You can always do a restore from the backup server as well.

Select Backup Server :

This is the list of peers/backup servers in which the backup data can be stored. Once the backup server is selected, you cannot change the server name. In case the backup server name or IP address is to be changed in future, you can change it from the Seed Backup Migration page. The client will run the backup to the selected backup server.

Test connectivity - Before you select the backup server for this backup schedule, you can check the connectivity to backup server. It also checks the different settings configured in the backup server for this client and confirms if this client can backup to the chosen backup server or not.

Add Backup Server- If you don't see a particular backup server listed, you need to first add it by following this link before you can select it for this backup schedule.

Temporary location for backup dumps

Enter the location/directory path to which the MSSQL Server database dumps has to be stored temporarily before uploading to the backup server. Please ensure that you have enough disk space in the configured temporary location (where the backup dump has to be saved). Please note that, backup dumps stored in the temporary location will be deleted once backup dumps are transferred successfully to the remote backup server.

Encryption

Password Protect this Backup

This option is to enable or disable encryption of the data that is being backed up. StoreGrid uses a well known encryption algorithm, Blow fish. If enabled, a password has to be specified which will be used for generating the encryption key. Encrypting data ensures that it cannot be read in the destination machine (backup server) where your backup is stored, and is especially relevant for sensitive information.

Password Protection

This option is to enable System Generated Encryption Key or use a Customized Encryption key for encrypting the backup data.

System Generated: The selected files and folders will be encrypted using Blow fish algorithm with a 448 bit encryption key automatically generated by StoreGrid before been backed up. No password will be required while restoring the data. Make sure you use this option only when the backup server is setup such that the backup server requires the client machines to authenticate before accepting the backup from the client.

Custom: This will enable the user to select the custom Encryption Technique, Encryption Key Size and the Encryption Key that needs to be used for encrypting the selected files and folders. Please don't lose the customized encryption key, as the backed up data cannot be restored without this key. Default Encryption Password: The selected files and folders will be encrypted with the Default Encryption Password as provided in the "Settings -> Advanced Options -> Default Encryption Password" page. Default Encryption Password is a convenient way to use the same password for all the backup schedules created in this client machine. It saves you from having to remember a different password for each backup set.

Encryption Technique

StoreGrid supports encryption using Blow fish or Triple DES. The Blow fish is a commonly used open source encryption technique which provides encryption based on the size of the encryption key length (from 64 bits to 448 bits). Higher the number of bits stronger is the encryption. Triple DES is a block cipher formed from the Data Encryption Standard (DES) cipher by using it three times, this technique is also supported by StoreGrid for encrypting the backup data. By default, Triple DES encryption technique is chosen. Encryption Key Size

StoreGrid supports encryption using variable length (64 to 448 bits for Blow fish and 192 bits for Triple DES) keys. The key is generated using the password you provide. Basically the longer the key size you give the more difficult it is for someone to decrypt the encrypted files. For normal backup purposes the default 64 bit encryption should be good enough.

Type Password

Provide a password here to generate the encryption key. If the password is forgotten the data can never be recovered as the data cannot be decrypted without this password. So, please ensure that you keep your

password in a safe place.

Step 4: Full Backup Scheduling (Decide When To Do Full Backup)

Configuring this step is mandatory. StoreGrid will do a full backup dump of the database whenever the full backup is scheduled and back it up.

This step has the following options from which any one can be chosen.

Run Monthly At - Choose the time and day of the month the backup should run. StoreGrid will run the backup every month on the particular day and time chosen. Unless you’ve selected the “Run this Backup each time StoreGrid restarts” option in Advanced Settings, StoreGrid will run at the stipulated time/day only.

Run Weekly - Choose the time and the day of the week the backup should run. StoreGrid will execute the backup every week on the particular day and time chosen. Note that you can select multiple days of the week if you wish to run the backup on multiple days of the week. Unless you’ve selected the “Run this Backup each time StoreGrid restarts” option in Advanced Options, StoreGrid will run at the stipulated time/day only.

Run Daily - Choose the time at which the backup should run daily. This will execute the backup everyday at the time you have provided. Unless you’ve selected the “Run this Backup each time StoreGrid restarts” option in Advanced Options, StoreGrid will run at the stipulated time only.

Run Every Few Hours - Choose the hours/minutes interval between each time StoreGrid must run. If StoreGrid is restarted in the interim, the backup will run once StoreGrid starts. Thereafter, StoreGrid automatically reschedules the next backup after the period you’ve set. For example, if you created a backup schedule at 10 am and set it to run every 1 hour, StoreGrid will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, StoreGrid is restarted, then the schedule will run once at 10.15am and the next scheduled time will now be set to 11.15am.

Additionally, you can also select the days in which this schedule should run. For example, if you do not want to run this backup schedule on Saturdays and Sundays, uncheck the checkbox against these days. If the "Select all days" checkbox is checked, then the schedule will be run on all the days of the week.

Run Once Only - Choosing this option will do the backup only once at the stipulated time.