SEP sesam Extension for Informix
(C)SEP AG
Copyright 1999-2011 by SEP AG. All Rights reserved.
Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.
Contents |
SEP sesam online backup for Informix (sib) provides a XBSA interface between Informix and SEP sesam for saving data of Informix databases to SEP sesam Server. XBSA API specifies the access from Informix onbar utility to a backup application. SEP sesam will manage the whole backup media handling like loading the correct tapes, whereas ONBAR decides which data has to be saved or recovered. This document provides information about the sesam specific parts of Informix backups. It's not an Informix/ONBAR administration guide. Please read Informix documentation of ONBAR to get familiar with Informix's backup and recovery concepts and tools.
The SIB packet includes only one shared library which Informix server loads dynamically during backup or restore. The library has to be copied to Informix server and the full path to it has to be specified under BAR_BSALIB_PATH in the ONBAR configuration file.
For installation we assume the following environment. Please adjust the paths and variables according to your needs.
/opt/informix
/opt/informix/etc/onconfig
Installation steps:
BAR_BSALIB_PATH Path to installed SEP sesam library
Example (Linux):
Installation steps:
gv_ro_bin:bin\sesam directory.
| Attention |
|
The path to libbsa.dll must use the short notation if SEP sesam is installed in a path with blanks, e.g. 'C:\Program Files\SEPsesam\bin\sesam'. dir /X C: may be used to get the short name notation! |
Example (Windows):
C:\PROGRA~1\IBM\Informix\11.70
%INFORMIXDIR%\etc\ONCONFIG.ol_myinst
| Attention |
|
In the instance specific ONCONFIG file the BAR_MAX_BACKUP gives the number of parallel backup sessions. BAR_MAX_BACKUP must be set at least to '2'. Otherwise a restores will NOT work! |
To set the version of XBSA specification SEP sesam supports, the following entry has to be inserted in table bar_version on sysutils database.
| bar_version | bsa_version | bar_sm | sm_version |
| 1 | 1.0.1 | sesam | 1 |
Instead of inserting this entry into database you can also adopt the INFORMIX template file.
| Info |
|
For the usage of SEP sesam command events, the login scripts of the Informix users should not expect any inputs! |
Create a new backup task for the Informix server with task type Informix. For backup source you must specify the Informix Instance. The instance should map to the instance which is used during ONBAR backup command.
To give ONBAR the necessary information to connect to SEP sesam, the following environment variables have to be set.
Mandatory parameters
Optional parameters
Although XBSA_TRACE XBSA_LOGFILE are not mandatory, they should be set to get information in case of a problem during backup or restore. For a restore only SESAM_SERVER and SESAM_JOB are mandatory.
The following examples show, how backup or restores can be started on Informix server. They do not cover all functions of ONBAR, but should give some hints for using ONBAR and SEP sesam together.
| Attention |
|
The return code of onbar always has to be checked, bcs. onbar writes no error messages to STDERR! The meaning of the return codes can be found in the Informix Backup and Restore Guide under Appendix A: ON-Bar Messages and Return Codes. You have to be informix or root to use onbar. |
The commands shown in the following example:
Perform a level 0 backup of "'dbspace01"' on an Online Dynamic Server instance named venus. Backup all logical log files associated with dbspace01, close and backup the current logical log
| Info |
| The SEP sesam Extension for Informix - Windows ZIP archive contains the sbc_onbar.cmd which is suitable to backup Informix instances via SEP Sesam Command Events by adapting INFORMIX_... and SESAM_... values. |
| The given arguments are passed to onbar command, so typical calls are "sbc_onbar.cmd -b -L 0", or "sbc_onbar.cmd -v". |
ONBAR commands to restore data backed up. The shared XBSA library translates Informix names passed by ONBAR into SESAM server save set (a set of files) for retrieval from the SESAM server's database and restoration to Informix.
Physical Restore:
Physical restores replace lost or corrupted storage spaces from SESAM backup media.
If a critical storage space is damaged because of a disk failure or corrupted data, Dynamic Server goes off-line.
If a disk failure or the corruption of data does not cause the database server to go to off-line mode you can restore any noncritical storage spaces.
Logical Restore:
Logical restores recover the server transactions made since the last storage space backup, followed by a rolling forward of the logical logs backed up for the storage space. If different backup sessions are involved, the log rolls forward transactions made since the backup time recorded for each storage space are restored.
Combined Restore:
Combined restores allow you to issue a single command to perform a physical restore immediately followed by a logical restore. For finer control, use the onbar -b -l -s command to salvage the logs, then the onbar -r -p command to perform only a physical restore, and then the onbar -r -l command to perform only a logical restore.
Point-in-time Restore:
Point-in-time restores involve performing a whole-system, physical restore of Informix data from a whole-system-backup to a specified time instead of the default, which is time of the last Informix backup.
There are two different kinds of restore you can perform in dependence of Informix Dynamic Server current mode. If the server is in quiescent mode or is on-line, you can perform a warm restore (Use the -O option to restore an on-line storage space). Otherwise, if server resides in off-line mode, the restore operation is called a cold restore.
for example Logical Log:
Here the commands are given for the following scenarios.
Backup of database
Complete backup of database (if necessary start the database with oninit -v)
Backup of a single dbspace
Logical Logfiles Backup
Database Restore
Restore of the whole database (cold restore)
Restore of the down dbspaces and corresponding logical logs (cold)
Restore of the down dbspaces without logical logs (cold)
Restore of single dbspaces
Restore of the logical logs (for dbspaces, wich have been restored physically)
| Info |
|
If chunk areas have been deleted the option -O should be used, this could eventually restore the chunk areas: Occasionally no checkpoint is written because of the missing chunk. This situation can be avoided with: or by shutting down the database with a following cold restore. |
Error message when executing oninit
Take a look at this article: http://www-01.ibm.com/support/docview.wss?uid=swg21501819
Error during first backup attempt
Create missing file, here C:\PROGRA~1\IBM\Informix\11.70\etc\ixbar.0 ( See IC50591: IXBAR.FILE IS REQUESTED DURING AN EXTERNAL RESTORE ALTHOUGH NO BACKUP WAS CREATED )
Error 131 during first logical logs backup attempt
Set LTAPEDEV in ONCONFIG file to a valued different to '/dev/null' or 'NUL', e.g. 'LTAPEDEV \\.\TAPE0' for Windows. See IBM Informix Dynamic Server LTAPEDEV
Our sales team would be happy to assist you!
Browse and discover videos by SEP.