Introduction
|
|
|
|
Once you have configured the HyperBac Control Service for the output directory
which you want to write your Sybase backups or exports to, you can now use any
Sybase backup or export interface available to you (natively or otherwise), to
perform fast, compressed, encrypted backups/exports.
In this example we are using the Sybase SQL Advantage utility to dump
an entire Sybase database.
|
|
|
Step 1 - Configuring HyperBac for Sybase
|
|
|
|
Before we begin, we will quickly describe how you configure HyperBac for
Sybase. This configuration is a one off exercise and this is the means
by which you determine how you will integrate your native backup processes with
HyperBac
In the example below, we have setup
File extension .hbc
To be applied across all paths or directories in the file system
This extension will compress the backups
In short, any file with a .hbc extension will be recognised by HyperBac
and be compressed.
|
|
|
Step 2 - Using Sybase SQL Advantage Without HyperBac
|
|
|
|
Below is a SQL Advantage dump command that backs up the database model
and writes the output to a file backup.dmp
Remember, we have configured HyperBac for Sybase to recognise .hbc extensions
only. Therefore this backup will not be compressed.
|
|
|
Step 3 - Using Sybase SQL Advantage Integrating HyperBac
|
|
|
|
** It is at this stage that you integrate your operation with Hyperbac for Sybase
**
In this scenario we have told HyperBac for Sybase to recognise file with a .hbc
extension. As shown in the command line image below, all that is required is a
change to the file extension.
The result is a file called backup.hbc giving you over 85% compression.
As importantly, you can simply restore this file as you would with any native
Sybase backup set. There is no change required to your load processes.
|
|
|
