Please see the more recent and detailed articles:

Remote SQL Server backups explained or

How to backup remote SQL Server database using SQLBackupAndFTP

Original article:

In this article, we will talk about the remote backups option which is provided as a Beta feature in SQLBackupAndFTP. Continue reading this article to find out more details.

When it is installed locally, SQLBackupAndFTP will use the default BACKUP DATABASE command in order to make backups of your databases. The outcome of this process is that a single *.bak (backup file) will be created, which you can then later restore using the default RESTORE DATABASE command.

For situations in which you use hosted or remote instances of SQL Server ( to which you are able to connect through SQL Server Management Studio), SQLBackupAndFTP will use make the backup of your database using scripting (“remote backups”).

This actually means that at the end of this process instead of getting just one *.bak file with all of your data, you will get several *.sql script files that contain the required CREATE DATABASE, CREATE TABLE IF NOT EXISTS and INSERT T-SQL statements which will actually recreate the database on the target server. Generally, you cannot use the BACKUP DATABASE command for remote servers because the .bak file (backup file) would be created locally, on the remote server. This would be problematic as you would then have to get the backup file to your local PC or to your other server in order to be able to restore the database.

The remote backup feature is in permanent Beta due to the complexity of the task it executes. There is no chance of doing harm or damaging the existing database during the backup process, but we cannot guarantee 100% the successful completion of the restore operation. You have to try to restore the database by yourself.

Use Remote only if Local Installation is not possible. Also, note that SQL Server 2000 is not supported for remote backups, but all other versions support this.