SQLBackupAndFTP

Brownie2019

Level 23
Thread author
Verified
Well-known
Forum Veteran
Mar 9, 2019
941
3,435
2,168
Germany

SQLBackupAndFTP

Database Backup Tool

SQLBackupAndFTP is a Windows backup utility focused on automating database backups (primarily SQL Server, MySQL, and PostgreSQL) and then storing/sending those backup archives to local/network storage or common remote destinations (FTP/SFTP/FTPS and multiple cloud providers). ([sqlbackupandftp.com](https://sqlbackupandftp.com/?utm_source=openai))

What it does (at a glance)
  • Schedules database backups (SQL Server supports full/differential/transaction log; MySQL/PostgreSQL support incremental backups per the vendor’s feature notes). ([sqlbackupandftp.com](https://sqlbackupandftp.com/?utm_source=openai))
  • Stores backups to local/network/NAS and remote endpoints like FTP/SFTP/FTPS and cloud storage (Amazon S3/S3-compatible, Azure Storage, Google Drive, OneDrive, Dropbox, Box, Backblaze B2, Yandex Disk, etc.). ([sqlbackupandftp.com](https://sqlbackupandftp.com/features?utm_source=openai))
  • Compression + encryption options are available; their documentation mentions AES-256 encryption via zip/7zip tooling, and their FAQ also distinguishes “ZIP compatible” vs “WinZip AES” modes in some versions/contexts. ([sqlbackupandftp.com](https://sqlbackupandftp.com/docs/docs/job-settings/backup-job/encryption/?utm_source=openai))
  • Email notifications and a “restore” workflow are listed in their feature comparison. ([sqlbackupandftp.com](https://sqlbackupandftp.com/features?utm_source=openai))

Security-focused considerations (important for any DB backup tool)
  • Treat backups as highly sensitive data: database backups often contain credentials, PII, tokens, and business data. Encrypt them and restrict who can read them.
  • Prefer secure transport: if using “FTP destinations,” prefer SFTP or FTPS over plain FTP where possible. (Plain FTP is unencrypted.)
  • Protect destination credentials: use least-privilege accounts/keys for S3/Azure/FTP endpoints (write-only if feasible; separate delete permissions; separate buckets/containers per environment).
  • 3-2-1 and immutability: keep at least one backup copy offsite and ideally immutable/WORM (or at minimum protected from the same admin credentials that run the database/server).
  • Test restores regularly: a backup you can’t restore is not a backup—verify restore chains (especially for SQL Server diff/log chains).
  • Service account hygiene: run scheduled backup jobs under a dedicated service account with minimal OS + DB permissions.

Practical “safety check” before deploying
I can’t determine “safe vs malicious” just from a product name or website, but you can reduce risk with standard verification steps:
  • Download only from the vendor site and verify the installer’s digital signature (Windows file properties) if present.
  • Upload the installer to VirusTotal and review results (watch for false positives; check vendor reputation and signature info).
  • Install on a test system first and monitor: outbound connections, created services/tasks, and what credentials it stores.
  • If it will run on a server, validate it fits your patching process and change-control (and whether auto-update is used/needed).

Current vendor notes (may change over time)
Their support page currently tells users to be on “the latest version (12.7.35)” before contacting support. ([sqlbackupandftp.com](https://sqlbackupandftp.com/support?utm_source=openai))

Bottom line
As a category, this is a “backup + offsite copy” automation tool for SQL Server/MySQL/PostgreSQL. If you evaluate it, focus less on the UI features and more on credential handling, encryption settings, secure transport (SFTP/FTPS), and a restore-testing routine.

Sources
 

You may also like...