HyperBac is an enterprise backup, recovery, import and export
solution, for your SQL Server databases developed by original developers of LiteSpeed. Working with your existing backup
techniques (TSQL, SQL Enterprise Manager, Management Studio, BCP or DTS), HyperBac uses high
performance lossless compression to reduce the size of your backup data sets by
up to 95% and the time taken to perform your backups by up to 75%.
The HyperBac benefit (and hence its capacity to scale to enterprise use) is
that it provides the appropriate balance between maximizing compression,
ensuring transaction throughput and minimizing operation times.
In practical terms, this means that HyperBac ensures a high transaction
throughput during operation, no CPU bottlenecks and a shorter operation window.
HyperBac works with the resultant backup information stream and thus it
seamlessly integrates with SQL Server's native backup procedures. To that
extent, the database administrator does not need to change their existing
scripts or deal with another application layer to use HyperBac.
As importantly, HyperBac does not directly read or write data from or to your
SQL Server database, it uses all native APIs therefore you can be assured of
data integrity at all times.
In addition archive files created by HyperBac can be converted to native backup
files (physical or logical) at any time on any system, offering peace of mind
for customers as well as a viable alternative recovery path should the restore
or import occur on a system which does not have HyperBac installed. Moreover,
compressed backups can be created in industry standard ZIP compatible output
format (with speeds equivalent to or better than most products on the market),
offering true third party vendor independence. Unique to HyperBac
Last but certainly not least, HyperBac for SQL Server has integrated AES
(128/192/256 bit) encryption to protect your backup sets.
HyperBac delivers a number of technical advantages. Solution
performance means that there is less contention for resources on the system(s)
during backup operations. The advantage here is that you can avoid or avert the
need to re-schedule or partition your backup operations to cater for end user
requirements.
As your data storage grows, so to will your backup times. HyperBac gives you
immediate relief from these growing pains. As well as prolonging the value of
your existing infrastructure, HyperBac also allows you to maintain existing
procedures and scripts for as long as possible. The advantage there is reduced
change management risk and need for support.
Consider the following simple example. Your backup window can no longer
accommodate your nightly incremental backups. The issue is serious as other
batch transactions such as general ledger consolidations and invoice runs
cannot be re-scheduled or changed. One unpalatable response to this situation
is to split the backups and target different database objects for different
nights. This means risk and greater loss of data in the event of disaster.
A far more appropriate option in this circumstance is to deploy HyperBac to
reduce both your backup times to cater for the existing window. The additional
benefit is that your backup will be significantly compressed, freeing physical
storage resources as well.
No. Unlike every other third party SQL Server backup product on
the market.
With HyperBac for SQL Server there are no extended stored procedures to
implement, nor does HyperBac employ command substitution or maintenance plan
conversion. It uses your actual scripts, jobs and procedures.
HyperBac's unique, ground breaking architecture is simply designed to work
with your existing TSQL BACKUP scripts, BCP or DTS jobs or SQL Server Database
Maintenance Plans. The only thing required is to configure HyperBac for your
backup or export output file.
Integration Example 1 - Working with specific file extensions
You perform a backup to a file called mybackup.bak. Just change the filename to
mybackup.hbc, mybackup.hbe or mybackup.zip (built in recognized HyperBac backup
file extensions).
That is all that is required. Change the file extension and HyperBac will
recognize it as a HyperBac backup operation. In the above scenario we used the
default extensions hbc and zip (for compression only) or hbe (for compression
and encryption).
In fact, you can configure HyperBac to nominate any file extension you wish.
Integration Example 2 - Working with specific directories or paths
Let's take the above example and say that you write your backups to the
following path and file C:\mydatabase\backup\mybackup.bak
If you don't want to change your scripts at all, then you can configure
HyperBac to recognize the path c:\mydatabase\backup. That means that all files
written to that path (irrespective of their name or extension) will either be
compressed and/or encrypted, depending upon what you choose.
That's it, no script or database maintenance plan conversion, command
substitution or extended stored procedures to deploy.
But it will give you options that you previously didn't have. By reducing your
backup size you can keep more backups online. That gives your flexibility and
options during recovery. As importantly, it saves you time during recovery,
because you won't have to rely on fetching tapes from off site locations.
You'll reduce risk. Why? Because you'll have more backup sets online and on
your site, which can be validated at greater frequency. This is not always
possible or feasible with off site archives. As importantly you can almost
eliminate the inherent risk associated with failed tape media.
HyperBac works with the existing native interfaces to read and write data to
and from your database. You are still running the native SQL Server commands
(TSQL BACKUP or bcp.exe) at all times.
Therefore HyperBac does not interfere with normal database operation in any
way. As importantly, HyperBac will operate independently of the database
release you have deployed.
HyperBac is a server side, service-based solution, deployed on the same
machine SQL Server is installed on. Importantly, nothing is installed within SQL Server and therefore there are no components to manage or upgrade when you upgrade versions of SQL Server or install additional instances of SQL Server. Unique to HyperBac
As well as being able to restore HyperBac backups seamlessly using native SQL
Server tools (RESTORE and bcp) on any server with HyperBac installed. You have
three additional options.
Firstly, HyperBac provides a "free restore" policy for SQL Server, whereby machines which only do restores (Development, Test or DR systems) are fully licensed for HyperBac at no cost.
Secondly, HyperBac backups can be written directly to a ZIP
compatible format, with performance equivalent to or better than all other solutions. This gives you complete third party vendor independence
allowing you to migrate, extract and restore to any server of your choosing at
any point in time on any system.
Lastly, HyperBac is shipped with royalty free command line and graphical
extraction utilities which can be used to extract compressed or encrypted
archives created with HyperBac at any time.
HyperBac for SQL Server delivers results in an improvement in
transaction throughput by up to 10 times during the backup process in contrast
to comparable conventional backup operations. This is due to the substantial
reduction in write disk I/O during the HyperBac backup process.
As importantly, HyperBac compression and encryption operations are performed
on-the-fly (including backing up to a ZIP compatible archive) which means that
the solution does not require any working space to deliver upon its
capabilities. This means that there is no need to maintain (or waste) an amount
of disk space to perform the compression.
Yes. HyperBac for SQL Server allows you to perform on-the-fly
compressed and/or encrypted logical backup operations (such as bcp or DTS) as
well as physical backup operations. Unique to HyperBac
Not at present. HyperBac for SQL Server is a high performance
disk based backup product designed to perform compressed backups to local or
remote DASD, NAS or SAN devices, which can then be ported to tape for offline
storage or archival purposes.
Disk based backups provide database administrators with fast, reliable recovery
online points. HyperBac's 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 as well as a 75-90%
reduction in DASD, NAS or SAN requirements.
Yes. Using HyperBac does not limit or prohibit you from
performing any other backup operations, the media to which you write it or the
vehicle you use to perform the operation.
The question is why? The performance gains are a significant incentive to take
advantage of HyperBac's capabilities. Above and beyond compression and reduced
backup windows, HyperBac writes its output to a ZIP compatible format, which
makes backups infinitely portable and gives you vendor independence. This is a
first for SQL Server backup technology.
Another first for the SQL Server market, HyperBac can deliver compression for
logical export or bulk copy operations. This makes HyperBac a unique backup
solution.
Last, but certainly not least, all of this functionality is delivered with
integrated AES Encryption to help you protect your backups against both server
and network vulnerabilities. Not to mention, the compliance expectations that
are growing by the day.
HyperBac is supported for SQL Server 2000 and above, including
full support for SQL Server 2000, SQL Server 2005 and SQL Server 2008. Supported operating systems are Windows Server 2003, Windows Server 2008, Windows 2000, Windows XP and Windows Vista (32 and 64-bit).
HyperBac is licensed per physical server (irrespective of the
number of instances, processors or database size). HyperBac is priced and
licensed to give you exceptional value for money and pay back it's investment
in months.
In most cases customers with existing compressed backup solutions in place can switch to HyperBac for less than their existing maintenance renewal payments and furthermore reduce their yearly outgoings by as much as 5 times.
Let's quickly explain what HyperBac does NOT impose upon you.
No licensing costs to perform restores, with the "free restore" policy for SQL Server.
No additional charges are required for the number of SQL Server instances,
databases or number of processors.
No additional charges are required in accordance with the size of your backup.
Whether its 1 GB or 20 TB then the investment is the same.
HyperBac is designed to save you money and time. The licensing model is also designed to reflect this principal.
There are many unique features that make HyperBac for SQL Server stand out in the crowd. Consider the following:
1. Integrated SQL Server backup compression and encryption while working with the native SQL Server commands (no extended stored procedures, maintenance plan conversions or command substitutions)
2. No change to existing procedures or processes and no additional training to deploy the solution. That means no risk or cost of change and a rapid deployment window so you can redeem the benefits sooner.
3. Output files that can be read and extracted by Zip compatible utility (such as shell integrated compressed folders in Windows, WinZip or WinRar) for portability, vendor independence and peace of mind
4. Streaming compression and AES Encryption capabilities for both physical and logical backup (bcp, bulk copy, dts) operations.
All of this is coupled with performance equal to or better than all products on the market and a price point and licensing scheme that ensures that your payback is achieved within months.
HyperBac contributes to a better operational environment for your business. For you, this means lowering the cost of managing your database environment. That could include reduced tape usage; smaller infrastructure requirements, lower support costs and/or deferred infrastructure spend.
Further to this, HyperBac gives you greater surety. By reducing you backup size and window, you can eliminate contention with processes that compete for scarce system resources. Such tasks may include nightly financial batch operations or end user access for transaction processing. With HyperBac you will not have to shuffle resources to meet your backup objectives. More online recovery points also give you surety with regard to the restore process and for disaster recovery planning.
With regard to your customers (whether they are internal or external) HyperBac helps ensure that your existing infrastructure will continue to meet stated service levels for performance and access. That ultimately means greater customer satisfaction and retention.
From a commercial viewpoint, HyperBac is designed to provide you with significant savings on your backup operations. These savings may include, but aren't limited to; lower tape usage, reduced support or personnel costs or even deferred investment in infrastructure spend to accommodate data growth.
HyperBac is priced such that it delivers a payback within months just on the savings you redeem on tape usage alone.
