At a glance
| Supported databases | SQL Server 2016, 2017 CU4+, 2019, 2022 and 2025, all editions including Express |
| Backup types | Full, differential, transaction log and file backups, in SQL Safe or native (.bak) format |
| Point-in-time recovery | Yes, listed on the product page |
| Compression and encryption | Compression with multi-threading; 128-bit or 256-bit AES encryption |
| Storage targets | Disk, mirrored locations, Amazon S3, Azure Blob Storage, S3-compatible storage, IBM TSM |
| Retention and automation | Backup and restore policies, scheduled log backups, alerting |
| Restore options | Instant restore, virtual databases, object level recovery, restore of Azure backups on-premises |
| Deployment | Windows agent per instance, central repository on SQL Server, management console; on premises or cloud VMs |
| Licensing | Per SQL Server instance, from 648 USD; term not stated |
SQL Safe Backup suits SQL Server teams that want backup policies, instant restore and virtual databases managed centrally across many instances, and that need current SQL Server 2025 support. It is a per-instance commercial product starting at 648 USD, but IDERA does not state the licence term on the product page, so get a written quote.
Overview
SQL Safe Backup is a backup and recovery product for Microsoft SQL Server from IDERA. A Backup Agent on each SQL Server instance runs backups and restores, a central repository database stores history, and a Management Console, Collection Service, Management Service and REST Service provide policy-based management and monitoring across instances. It compresses and encrypts backups, writes them to disk, to several mirror locations in one operation, or to Amazon S3, Azure Blob Storage and S3-compatible storage, and can integrate with IBM TSM.
The 9.7 requirements list SQL Server 2016, 2017 CU4 or later, 2019, 2022 and 2025 (all editions, including Express) for both the agent and the repository, on Windows 10, Windows 11 and Windows Server 2016 to 2025. Version 9.7 added SQL Server 2025 and Windows Server 2025, improved restores from S3-compatible storage such as Wasabi, allowed Azure backups to be restored to on-premises SQL Server, and patched a MimeKit vulnerability (CVE-2026-30227).
Key features
- Policy-based backup and restore management across many SQL Server instances, with central history
- Instant restore, which brings a database online while data continues to stream in the background
- Virtual databases attached directly from backup files without a full restore
- Compression and multi-threaded writing, plus 128-bit and 256-bit AES encryption
- Backups to Amazon S3, Azure Blob Storage, S3-compatible storage and mirrored locations in one operation
- Object level recovery service on the Backup Agent
- Real-time monitoring, alert e-mails and a command-line tool (SQLSafeCmd)
Integrations and ecosystem
Pros and cons
Pros
- Published support for SQL Server 2025 and Windows Server 2025 in version 9.7
- Instant restore and virtual databases shorten time to first access after an incident
- Policy-based management for many instances from one console
- Native cloud object storage targets, including S3-compatible services
Cons
- Only SQL Server 2016 and later are listed in the 9.7 requirements
- Licence term and maintenance are not stated on the product page
- Windows and SQL Server only
- Several components (agent, repository, management services) to install and maintain
Pricing
IDERA's product page says SQL Safe Backup starts at 648 USD per instance, with volume pricing and quotes through sales. The page does not say whether that figure is a perpetual licence or a subscription, or what maintenance it includes, so ask for a quote. A fully functional 14-day trial is offered.
Pricing checked on the vendor's official page on 7 November 2026. Prices change; confirm before buying.
Who it is best for
DBA teams running many SQL Server 2016 to 2025 instances who want central backup policies, fast restore options and cloud storage from one SQL Server-focused product.
Typical use cases
- Standardising backup schedules for dozens of SQL Server instances with policies
- Getting a production database readable quickly after a failure with instant restore
- Checking or querying an old backup by mounting it as a virtual database
- Writing backups straight to Amazon S3 or Azure Blob Storage from SQL Server on cloud VMs
Who should look elsewhere
- Estates still on SQL Server 2014 or older, which the 9.7 requirements no longer list.
- Small shops that only need scheduled backups to cloud storage, where SQLBackupAndFTP is simpler and cheaper.
Verdict
SQL Safe Backup is an actively maintained SQL Server backup product with current platform support and strong restore options such as instant restore and virtual databases. It needs more infrastructure than a single-server tool and its pricing terms are not fully public, so compare a quote against Redgate SQL Backup Pro if both fit your versions.
Frequently asked questions
Is IDERA SQL Safe Backup still supported?
Yes. IDERA's documentation lists 9.7 as the current version, and its What's New page (updated 5 November 2026) adds SQL Server 2025 and Windows Server 2025 support.
Which SQL Server versions does SQL Safe Backup support?
The 9.7 requirements list SQL Server 2016, 2017 CU4 or later, 2019, 2022 and 2025, all editions including Express.
How much does SQL Safe Backup cost?
IDERA advertises a starting price of 648 USD per instance, with volume pricing through sales. The product page does not say whether this is perpetual or a subscription.
Can SQL Safe Backup write to the cloud?
Yes. It supports Amazon S3, Azure Blob Storage and S3-compatible storage, and it also runs on SQL Server in Amazon EC2 and Azure virtual machines.
Sources
- IDERA SQL Safe Backup product page
- SQL Safe Backup documentation (9.7)
- SQL Safe Backup 9.7 software requirements
- What's New in SQL Safe Backup 9.7
- SQL Safe Backup previous features and fixed issues
- Integrate SQL Safe with TSM
Checked November 2026.
Listed in: Database Backup & Recovery.
How we research reviews and what star ratings mean: our editorial method.