SQL HyperBac 5.4

SQL HyperBac has a zero-touch deployment, so there are no links into your SQL Server instances, extended stored procedures or command substitutions. It is installed on the server where SQL Server runs, and listens for filesystem traffic to or from set destinations. When SQL Server sends a backup stream to a SQL HyperBac destination, SQL HyperBac intercepts that stream, silently compresses it, and writes it to disk.

SQL HyperBac works at the file system layer, so you can compress:

• Logical operations such as BCP, DTS, or SSIS
• Trace files
• Data replicated between two instances

No changes are needed. No extended stored procedures need to be implemented, nor does SQL HyperBac employ command substitution or maintenance plan conversion. It uses your existing scripts, jobs and procedures, including T-SQL BACKUP scripts, BCP or DTS jobs, and SQL Server database maintenance plans. You just need to configure SQL HyperBac to recognise your backup or export output file.

No. SQL HyperBac works with existing native interfaces to read and write data to and from your database. You are still running the native SQL Server commands, such as T-SQL BACKUP or bcp.exe, at all times.

SQL HyperBac is a server-side, service-based solution. It is deployed on the same machine that SQL Server is installed on. Importantly, nothing is installed within SQL Server, and there are no components to manage or upgrade when you perform version upgrades of SQL Server or install additional SQL Server instances.

Yes. SQL HyperBac is a disk-based backup solution and it will work seamlessly with local or remote DASD, SAN or NAS devices.

Yes. SQL HyperBac backups can be written directly to a .zip compatible format, with performance equivalent to all other solutions. This gives you complete third-party vendor independence allowing you to migrate, extract and restore to any server at any point in time on any system.

SQL HyperBac supports SQL Server 2000, 2005, 2008 and 2008 R2. For more information, please see Requirements.

SQL HyperBac supports Windows Server 2003, Windows Server 2008, Windows XP and Windows Vista (32- and 64-bit). For more information, please see Requirements.

Not at present. SQL HyperBac is designed to produce backups for local or remote DASD, NAS or SAN devices, which can then be ported to tape for offline storage or archival purposes.

SQL HyperBac's silent compression is superior to the hardware compression which is common on many tape devices, so a disk to tape backup strategy will generally yield a 50% reduction in tape storage costs in addition to a 75-90% reduction in DASD, NAS or SAN requirements.

SQL HyperBac is licensed per server.

Some customers may have two or more virtual machine instances running on the one physical server. In this case each virtual machine instance is treated as a server and would have to be licensed individually.

SQL HyperBac needs to be licensed for each node of the cluster. SQL HyperBac's architecture requires that it is installed on each host where a SQL Server instance is running. In the case of a cluster this is a physical node.

If you need a restore-only license for SQL HyperBac, please get in touch with our sales team.

If your trial period expires before you've had a chance to evaluate, please contact us and we would be happy to help.

If you own a license of HyperBac for SQL Server 4.xx or earlier, you can upgrade by downloading a trial from our SQL HyperBac product pages and activating the license.

Please note that HyperBac for SQL Server customers using version 4.xx and earlier will need to contact Red Gate for a new serial key to activate a version 5 license. This is due to licensing changes in version 5.0. For a new serial key, please contact us.

Please note that this is a major driver upgrade, so existing HyperBac for SQL Server customers will need to perform a reboot to complete the upgrade. All products using HyperBac technology on your computer must be updated to use the new engine. Other products using HyperBac technology include SQL Storage Compress and SQL Virtual Restore.