SQL Server Log Shipping Compression

Unique to HyperBac

HyperBac for SQL Server integrates seamlessly into your native log shipping operations. There is no need for complex command substitution or the redevelopment of existing procedures.

As for all HyperBac for SQL Server integration scenarios, all that is required is that you match the extension of the backup on your primary server with an extension that HyperBac is configured to recognize.

By default, HyperBac for SQL Server recognizes the following extensions:

1.   .HBC – Compressed backup in native HyperBac format
2.   .HBE – Compressed and encrypted backup in native HyperBac format
3.   .ZIP – Compressed backup in vendor independent ZIP format **Unique

Any custom extensions can be easily configured using the HyperBac Configuration Manager, for instance .BAK or .TRN, to inegrate seamlessly with existing native transaction log shipping. Similarly the HyperBac instance on the secondary server where the restore operation is to be performed is also configured to recognize the same backup file extensions.

The result is that your backed up transaction logs:

1.   Are 80% smaller
2.   Have been created in half the time
3.   Consumed far less network bandwidth and
4.   Were restored 20% faster than the native file size