HyperBac for MySQL is an enterprise backup and archival solution, for your MySQL environment. Working with your existing backup techniques, HyperBac uses high performance lossless compression to reduce the size of your backup data sets by up to 90% and the time taken to perform your backups by up to 50%.

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 MySQL'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 MySQL database, therefore you can be assured of information 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.

Last but certainly not least, HyperBac for MySQL has integrated AES (128/192/256 bit) encryption to protect your MySQL backups.

HyperBac for MySQL 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 size can no longer be accommodated your existing disk capacity. You find yourself having to manipulate and clear files just to ensure that the backups will perform successfully. Even so, you can't trap all instances, and some fail for a lack of disk space. 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 for MySQL to reduce both your backup size to cater for the existing capacity. The additional benefit is that your backup will be significantly shorter in time, freeing resources usually available to your database to handle transaction processing.

Not at all.

HyperBac for MySQL is designed to work with your existing scripts (mysqldump, mysqlhotcopy, SELECT INTO OUTFILE) or with the MySQL GUI Administrator Console. The only thing required is to point your dump device (or output file) to a HyperBac registered destination.

Integration Example 1 - Working with specific file extensions

You perform a dump that writes a file called mybackup.bak. Just change the filename to mybackup.hbc or mybackup.hbe (file extensions that are registered by default as HyperBac backup files).

That's all that is required. Change the file extension and HyperBac will recognize it. In the above scenario we used the default extensions hbc (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 /mydatabase/backup/mybackup.bak

If you don't want to change your scripts at all, then you can configure HyperBac to recognize the path /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.

No.

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.

Not at all.

HyperBac for MySQL works with the existing native interfaces to read and write data to and from your database during backup and restore operations. For example, if you are using the MySQL Enterprise wizards, then all you need to do is point your dump device to a HyperBac recognized path or file type. The fact remains that you are still running the native MySQL commands at all times.

Therefore HyperBac for MySQL does not interfere with normal database operation in any way. As importantly, HyperBac will operate independently of the database release you have deployed.

Yes, and it is absolutely free.

HyperBac for MySQL is shipped with an extractor utility, which is a simple command line utility for Linux installations. Similarly, it is deployed as a graphical tool as well as a command line utility for Windows installations.

In short, the extractor allows you to take an existing HyperBac backup and transform it into the native MySQL format. There are many benefits to this facility.

1. You can transport compressed and/or encrypted backups (securely and without unnecessary bandwidth demand) to remote sites and then simply use the extractor utility to transform the backup set to native format. This has application to those who replicate testing or development environments.

2. The extractor utility can expedite and lower the cost of server migrations or consolidations.

3. The extractor also serves to give you peace of mind. You can continue to work with HyperBac backup sets irrespective of whether or not the product is deployed. In short, we recognize the importance of vendor independence as much as you.

These are just three examples; however there are many more that simply depend upon your imagination and business circumstance.

HyperBac delivers 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 is streaming 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.

HyperBac for MySQL is a server side solution, deployed on the same machine as your actual MySQL database instance.

Yes.

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

Yes.

You can integrate HyperBac to backup any object level that MySQL permits you to backup.

Yes.

Using HyperBac for MySQL does not limit the type of backup you perform, the media to which you write it or the vehicle you use to perform the operation.

The performance gains are a significant incentive to take advantage of HyperBac's capabilities. Above and beyond compression and reduced backup windows, HyperBac 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.

The transaction throughput available during HyperBac operations makes it ideal for MySQL implementations, which are typically in high transaction volume situations and where the user experience is critical to good business branding.

Yes.

HyperBac for MySQL will work with all storage engines supported by MySQL including the InnoDB and MyISAM storage engines. HyperBac will work with all MySQL backup tools such as mysqldump, mysqlhotcopy or the InnoDB Hot Backup.

Yes.

HyperBac for MySQL will reduce your backup time by up to 50% and your backup size by up to 90%. This can itself be enough to help you reduce costs, ensure end user access to the database and avoid the expense of additional hardware and software costs.

As importantly, HyperBac helps to ensure that your environment remains simple and straight forward to manage. This is in itself an ongoing saving to your business.

Yes.

If you are using the mysqldump flush-logs utility to perform this task, HyperBac for MySQL will accelerate this process and compress the log files, this is accomplished by simply configuring HyperBac for the path where the log files are stored.

The log files will retain their integrity. By speeding the incremental backup process, you contribute to ensuring that end users continue to get consistent and uninterrupted access to MySQL for transaction processing.

HyperBac for MySQL supports for MySQL version 4 and above.

You can deploy HyperBac for MySQL on Windows 2000 and above and all x86 distributions of Linux (kernel 2.4 and above).

HyperBac for MySQL is licensed per physical server. Contact us for more information on HyperBac for MySQL pricing.

HyperBac for MySQL 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 for MySQL 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.