Documentation
Setup instructions, troubleshooting and detailed product guides.
Browse documentationSend a question directly to our support team.
Common questions about licenses, subscriptions, backups and support.
Create scheduled database and file backups, use full, differential and transaction log backup types, compress and encrypt backup files, send them to local, network, FTP or cloud destinations, and receive status notifications.
Install SQLBackupAndFTP, create a backup job, connect to your database server, select the databases or folders, choose a destination and configure the schedule. The Documentation section contains detailed setup guides.
Yes. The license does not expire, and you can continue using the version you purchased without an active Full-Service subscription.
It includes product updates, direct technical support, Web Log access, email notifications through our mail servers and service-down alerts.
Yes. You can cancel at any time. When a subscription expires, the license remains valid, but subscription services and future updates are no longer included.
SQLBackupAndFTP supports Microsoft SQL Server, MySQL, PostgreSQL, Azure SQL and compatible hosted database services. Available features depend on the selected edition.
Yes. SQLBackupAndFTP can connect to supported database servers over the network and back up remote databases. The machine running SQLBackupAndFTP must be able to reach the database server and the selected backup destination.
Backups can be sent to local and network folders, FTP, SFTP and FTPS servers, and supported cloud destinations such as Amazon S3, Azure Storage, Google Drive, Dropbox, OneDrive, Box and Backblaze B2.
No. SQLBackupAndFTP creates and transfers backups, but you choose and manage the destination where they are stored, such as a local or network folder, FTP server or cloud storage account.
SQL Server backups created by SQLBackupAndFTP can be restored from the application when the related backup history is available. The restore process can handle full, differential and transaction log backup chains.
Yes. A database can remain online while a backup is running. Backup activity can affect server performance, but the impact is usually minor and depends on the database size and server workload.
Yes. Create a separate backup job for each SQL Server instance and configure its databases, schedule and destinations independently.
Yes. Jobs and supported application operations can be started from the command line, which is useful for scripts, automation and Windows Task Scheduler.
Yes. The backup file naming template can be customized using available variables such as the database or folder name and the backup date and time.
Yes. In the backup destination settings, configure the retention period using the option to automatically delete backups older than the selected number of days.
Yes. The SQLBackupAndFTP window does not need to remain open, but the computer or server where the application is installed must be powered on and running when the scheduled job starts.
A new installation starts with a 14-day Professional trial. When the trial ends, it automatically switches to the Free edition unless you activate a paid license.
Yes. The Free edition can be used without a time limit. It supports up to two databases with full backups and a reduced set of destinations and features.
One license can cover one or more computers. When purchasing, specify how many computers or installations you need, and the license will include that number of activations. Professional 1 database requires a minimum purchase of five computers; you can select any quantity from five upward.
AES encryption for backup files is available in Professional, Professional 1 database and Professional Lifetime. Secure transfer options such as SFTP and FTPS are also available, depending on the selected edition and destination.
Distribution terms depend on the edition and intended use. Contact our sales team about OEM licensing, customization or private-label distribution before including SQLBackupAndFTP with another product.
Automatic mode sends backup status emails through the SQLBackupAndFTP mail service, so you only need to specify the recipients instead of configuring your own SMTP server. An active Full-Service subscription is required.
Yes. You can configure a supported external email account or SMTP server in the advanced email settings. The required authentication settings depend on the provider.
Yes. Add multiple recipients in the notification settings and separate the email addresses with commas.
First verify the same server address, credentials and connection settings in your database management tool. Then check network access, firewall rules, database permissions and whether remote connections are enabled.
Verify the host, port, credentials and encryption mode. If the connection still fails, try changing Passive FTP mode and check firewall, antivirus and network rules.
Increase the database timeout in the advanced job settings. Also check available disk space, destination speed and server load if the backup continues to time out.
Yes. Change the location in the Temporary folder setting. Choose a drive with enough free space for the uncompressed working files created during a backup.
The SMTP server rejected the message because authentication or relay permissions are incorrect. Verify the outgoing mail server, port, encryption method, username and password.
Do not use GO batch separators in custom SQL scripts executed by SQLBackupAndFTP. GO is a client-tool command rather than a Transact-SQL statement understood by the database engine.
Customers with an active Full-Service subscription normally receive a response within one business day.
Customers with an active Full-Service subscription receive direct email support. We normally answer within one business day.