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.

Vembu OnlineBackup | Admin User Guide | MS SQL Server Backup and Restore 71

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.

Vembu OnlineBackup | Admin User Guide | MS SQL Server Backup and Restore 72 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.

Similar to a Full Recovery Model database, Bulk Logged Model databases provide extensive backup and restore 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

Vembu OnlineBackup | Admin User Guide | MS SQL Server Backup and Restore 73

Step 3: Set Basic Configuration

Backup Types

Vembu OnlineBackup provides 2 types of Backup options.

1. Seed Backup – With this option you can seed backup to local drive which you can migrate to the Vembu Cloud using USB/External Hard drives to avoid more network bandwidth. It can be done only with the initial Full backup and incremental backup will not be continued.

2. Vembu Cloud – With this option you can directly backup the data into the Vembu Cloud over the Internet.

Test connectivity - Before you proceed with the backup, you can check the connectivity to Backup Server (Vembu Cloud). It will check the Connectivity and DNS Lookup with the Vembu Cloud.

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

Configuring this step is mandatory. Vembu OnlineBackup 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. Vembu OnlineBackup will run the backup every month on the particular day and time chosen. Unless you’ve selected the “Run this Backup each time Vembu OnlineBackup restarts” option in Advanced Settings, Vembu OnlineBackup will run at the stipulated time/day only.

Vembu OnlineBackup | Admin User Guide | MS SQL Server Backup and Restore 74

Run Weekly - Choose the time and the day of the week the backup should run. Vembu

OnlineBackup 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 Vembu OnlineBackup

restarts” option in Advanced Options, Vembu OnlineBackup 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 Vembu OnlineBackup restarts” option in Advanced Options, Vembu OnlineBackup will run at the stipulated time only.

Run Every Few Hours - Choose the hours/minutes interval between each time Vembu

OnlineBackup must run. If Vembu OnlineBackup is restarted in the interim, the backup will run once Vembu OnlineBackup starts. Thereafter, Vembu OnlineBackup 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, Vembu OnlineBackup will first run the schedule at 10am and the next scheduled time will be 11am. However, if at 10.15am, Vembu OnlineBackup 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.