SQLBackupAndFTP is a long-established Windows backup tool for SQL Server, MySQL and PostgreSQL. Of everything on this list, it's the closest to PostgresBackup: a Windows app that schedules database backups. It does more in some directions, and PostgresBackup does more in others. If you need what SQLBackupAndFTP does better, buy it.
Details about SQLBackupAndFTP are from its website as of the date above. Check their pricing page for current editions and prices.
Where SQLBackupAndFTP is stronger
- More database engines. SQL Server and MySQL as well as PostgreSQL. One tool for a mixed estate.
- Built-in destinations. It can send backups to FTP/SFTP, network folders and a range of cloud storage services (which ones depends on the edition). PostgresBackup writes every backup to a folder you choose, and can copy the weekly, monthly and yearly ones to another folder or share, S3 (or S3-compatible storage), Azure Blob Storage or SFTP. It doesn't upload every backup, or use FTP or consumer cloud drives (for those, see synced folders).
- Email notifications on success or failure, in the paid editions.
- Encryption and more options in higher editions, and years of production use behind it.
Where PostgresBackup is stronger
- Price. SQLBackupAndFTP's free edition schedules up to two databases. Its paid editions are priced per computer, from about $39 to $129, with an optional yearly subscription for updates. PostgresBackup is $9.99 once (launch price; $24 from January 1) for the whole app, updates included, with clones, restores and manual backups free forever.
- PostgreSQL focus. Retention with keep-last-N plus hourly/daily/weekly/monthly/yearly rules, per job. Clone a database between servers in one step. Restore any
.dumpor.sqlinto a new or existing database, with an option to wipe the target first. - Hosted-PostgreSQL help. Built-in tips for Supabase's session pooler and Neon's direct endpoint, and current PostgreSQL client tools included.
- Privacy. No account, no cloud service, nothing leaves your machine except your own backups to wherever you send them.
Side by side
| SQLBackupAndFTP | PostgresBackup | |
|---|---|---|
| Databases | SQL Server, MySQL, PostgreSQL | PostgreSQL |
| Price | Free edition (2 scheduled databases); paid ~$39–$129 per computer | $9.99 once (launch price; $24 from January 1); clones, restores, manual backups free |
| Scheduled backups | Yes | Yes, from a background service that starts with Windows |
| Retention | Yes | Last N + hourly/daily/weekly/monthly/yearly per job |
| Cloud / FTP destinations | Built in (varies by edition) | Weekly, monthly and yearly copies to a folder, S3, Azure Blob Storage or SFTP |
| Email alerts | Paid editions | No (Backup History and Activity Log) |
| Clone to another server | No dedicated feature | One step |
| Restore | Yes | Yes, .dump and .sql, into new or existing databases |
| Account needed | Optional cloud features use an account | None |
| Backup files | Database-native formats | Standard pg_dump custom format |
Which should you choose?
- Choose SQLBackupAndFTP if you back up SQL Server or MySQL too, need every backup uploaded to cloud storage or FTP, or need email alerts and encryption out of the box.
- Choose PostgresBackup if your databases are PostgreSQL, you want clone and restore as first-class features, and you'd rather pay once, a small amount, for one focused app.
Both write standard dump files, so trying one doesn't lock you out of the other.