HyperBac for Oracle is enterprise disk based database backup
software. HyperBac uses integrated, high performance lossless compression to
reduce the amount of disk I/O and DASD storage requirements by up to 90%.
HyperBac backups are faster and result in increased transaction throughput and
system performance. In contrast, other methods which can be used to produce
compressed backup sets typically incorporate aggressive compression routines
which yield a high rate of data compression but introduce a CPU bottleneck.
HyperBac uses native backup and export technologies such as RMAN, EXP/IMP and
EXPDP/IMPDP and as such supports all types and options for backups, restores
and ETL operations including hot, cold, offline, online, physical, logical,
physi-logical and all others.
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.
The diagram below summarizes the architecture for HyperBac for Oracle:
HyperBac for Oracle 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.
Other methods used to produce compressed backup sets in Oracle 10g typically
use more aggressive compression routines, while reducing disk write I/O, these
routines generally result in excessive CPU utilization introducing a different
system bottleneck. As a result, these methods may adversely impact transaction
throughput and system usability and responsiveness.
Yes. Nothing changes to the way you had previously performed
native backups and ETL operations or to your existing high availability or
disaster recovery procedures when using HyperBac. HyperBac is invoked simply by
changing the file extension of the backup pieces to HBC (or another user
configured file extension) before executing the RMAN, EXP or EXPDB operations
or copying the data files to a destination file with a HBC extension (in the
case of cold backups). Below in an example demonstrating how HyperBac is
incorporated into your existing backup scripts and jobs:
No. As HyperBac uses native backup technologies, no changes are required to
your existing disaster recovery procedures or policies. All backup operations
including hot, cold, physical, logical, incremental, differential are all
supported. In addition, technologies such as RAC, Oracle Data Guard, warm and
hot standby databases are fully supported.
Other methods used to produce compressed backup sets in Oracle
10g use more aggressive compression routines, while reducing disk write I/O,
these routines typically result in excessive CPU utilization introducing a
different system bottleneck. As a result, these methods may adversely impact
transaction throughput and system usability and responsiveness.
HyperBac's high performance compression technology reduces disk I/O and
provides a high level of data compression and storage reduction without
creating a CPU bottleneck. Transaction throughput is markedly increased and
disk I/O wait states are reduced.
Yes. Because HyperBac uses native backup and ETL technologies,
such as RMAN, EXP and EXPDP (Oracle Data Pump), all physical, logical and
physi-logical backup operations are supported including database, archive log,
datafile and tablespace backups using RMAN and table/schema exports using EXP
or EXPDP.
Moreover, all backup options including parallelism, incremental, differential,
image copies and all other options. All recovery operations are supported
including point-in-time and flashback are fully supported.
Yes. You are able to perform native or HyperBac backups on the same system, to
perform a native backup or export you would simply use an output file extension
which was not associated with HyperBac, for instance .BAK or no extension.
HyperBac for Oracle leverages native Oracle backup/recovery and
export/import tools, including RMAN, EXP/IMP and the Oracle Data Pump (Release
10g). All interactions with the Oracle instance and database are performed
through these standard interfaces, ensuring data integrity and consistency.
Interface Ensuring Data Consistency and Integrity. In addition, all of the
recovery catalog, job and script metadata is retained by Oracle and can be
queried or reported on.
As HyperBac can use all of the standard Oracle backup, recovery and ETL tools
and commands, all of the functionality available in these tools is available
using HyperBac. This means that your standard backup and recovery procedures
and methods can be maintained while attaining optimal speed, transaction
throughput and storage savings and the validity of the output devices is
uncompromised by the process.
HyperBac for Oracle delivers enterprise class performance without the
enterprise software price tag. We recognize your requirement for a rapid return
on your investment. Starting at $999 per server, HyperBac reduces operational
costs and on going infrastructure costs such as growth and maintenance
expenditure on DASD, NAS, SAN and tape costs.
HyperBac for Oracle is supported on Microsoft Windows Server
2008, Windows Server 2003 and Windows 2000 Server Service Pack 4 and above operating
systems, Solaris (8, 9 and 10), Linux operating systems (all distributions, kernel 2.4 and above), and HPUX 11i v2 and 11i v3. HyperBac for Oracle supports Oracle database versions 9i, 10g and 11g (all releases) for all of the aforementioned supported operating system platforms.
Not at present. HyperBac for Oracle currently supports disk based backup devices only. 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. HyperBac for Oracle can backup or export to any logical disk device. NAS,
SAN, and any other appliance based storage devices are fully supported as well
as local DASD and shared network devices. Backups and exports to all output
logical disk devices are seamless and transparent to the administrator.
Yes. In an Oracle RAC environment, HyperBac for Oracle should
be installed on each physical node in the RAC configuration. This will allow
for all types of physical, logical, hot and cold backup operations on any node
and would provide complete flexibility for disaster recovery, duplication or
ETL operations. However if you wish to perform all backup operations from one
node, you would license and install HyperBac on this particular node only.
In an Oracle Data Guard configuration, HyperBac can be installed on the primary
or standby node or both depending upon which system is used to perform the
backups or exports.
HyperBac for Oracle is licensed per logical server, this is
irrespective of how many Oracle instances or Oracle databases are on the
server. In a RAC environment, a license is required for each physical node in
the RAC configuration that HyperBac is installed on. In a virtual server
environment, a license and installation is required on each virtual server on
the host machine.
You do not need a license to restore a HyperBac backup or export file, to
restore the database or objects without HyperBac you would simply extract the
archive files using the HyperExtract conversion utility and restore the files
natively.
HyperBac for Oracle means reduced costs, reduced database backup and export
windows, portability, flexibility and performance. HyperBac means increased
transaction throughput which equates to increased revenue. Moreover, with
increased availability and reduced storage costs HyperBac means increased
profitability for your business.
Yes. Using HyperBac for restores is a seamless one step process however
HyperBac backups are simply compressed native archive files which can be
exported to native format (RMAN or EXP) at any time using the HyperExtract
conversion utility. The extracted archives can then be restored or imported on
any Oracle server.
