When you go to create a SQL backup set in the software you will be able to search for SQL servers and instances that exist in your environment. You can then select the method for authentication with that SQL server. You can choose either Windows authentication or SQL authentication.
Windows authentication uses the credentials of the BackupAgent service (we use the Local System account by default) to connect to the SQL instance. SQL authentication allows you to pick a user such as a SQL administrator account and plug in the credentials of that user.
You can then refresh your list of databases to view all of the databases on the instance you have selected to backup. You can select a single database or you can select multiple ones, de-selecting specific databases from the backup.
SQL backups are scheduled by default according to Microsoft best practice of having one full backup per week with six differential backups. Your first backup of the databases will be a true full copy, taking an entire copy. Day to day differentials would then just take the transactional changes since your most recent full backup, and the weekly full would use our Intelliblox technology to run a block-level differential on the previous full backup.
We keep SQL backups on a weekly basis, by default keeping 4 weeks of SQL data. You can configure the software to keep as little as 1 week of data, or you can create custom rules similar to a tape scheme.