Full, Differential and Transaction Log backup type

1. Backup name and path

• Single backup
• Backup physical name: If it's a single backup, this field indicates the physical file name. Also at the end of the file SQLServerBooster concatenates the date and time with this format "yyyyMMdd24HHmmss"
• Multiple-database backup
• Multi-database prefix: If it's a multi-database backup, a concatenation of the prefix and database name will be given to the physical file name. Also at the end of the file SQLServerBooster concatenates the date and time with this format "yyyyMMdd24HHmmss". At the end the physical file name will look like this "PREFIX_DATABASENAME_yyyyMMdd24HHmmss"
• Database server path: Indicates where the backup file will be generated. It's important that the directory has read/write permissions
• Is a remote database server?: In case the machine where SQLServerBooster it's installed and MS SQL Server it's installed is not the same. It has to specify a UNC path to be able to compress (in case this option was selected) and has access to copy to the other paths

1. Make a copy of the backup to these other paths

• Copy path: It's possible to copy the backup to three different paths
• Delete backup after copy: This will delete the backup after being copied and uploaded to the Cloud or send through FTP

1. Helps to test that the paths exists

Remote (Script) backup type

1. Backup name and path

• Single backup
• Backup physical name: If it's a single backup, this field indicates the physical file name. Also at the end of the file SQLServerBooster concatenates the date and time with this format "yyyyMMdd24HHmmss"
• Multiple-database backup
• Multi-database prefix: If it's a multi-database backup, a concatenation of the prefix and database name will be given to the physical file name. Also at the end of the file SQLServerBooster concatenates the date and time with this format "yyyyMMdd24HHmmss". At the end the physical file name will look like this "PREFIX_DATABASENAME_yyyyMMdd24HHmmss"
• Script path: This is a local path
• Batch size: The statement "GO" is used. This statement signals the end of a batch of Transact-SQL statements to the MS SQL Server utilities (*)
• Split into multiple files: If the database has a lot of data it is recommended to use this option. MS SQL Server Management Studio has limitations related with the files size to execute. Each file has a correlative to know the order in which has to be executed
• Size of the splited files (50 MB): The size of each file

1. Make a copy of the backup to these other paths

• Copy path: It's possible to copy the backup to three different paths
• Delete backup after copy: This will delete the backup after being copied and uploaded to the Cloud or send through FTP

1. Helps to test that the paths exists

Next: Configure FTP, Amazon S3, Amazon Glacier, Windows Azure and Dropbox

(*) Source Technet Microsoft