Archive:SEP sesam extension for Ingres

From SEPsesam
Jump to: navigation, search
SEP AG has discontinued support for obsolete SEP sesam versions. Instructions are still available for these SEP sesam products, however, SEP AG accepts no responsibility or liability for any errors or inaccuracies in the instructions or for the incorrect operation of obsolete SEP sesam software. It is strongly recommended that you update your SEP sesam software to the latest version. For the latest version of SEP sesam documentation, see documentation home.

Copyright © SEP AG 1999-2020. 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.


SEP sesam extension for Ingres provides the following functions:

  • Interface for chkdb and rollforward commands to use SEP sesam as media manager (instead of using tar)
  • Complete database backup over Sesam GUI. This includes backup of data, journal and dump directories
  • Complete disaster restore of database

System requirements

  • Supported Versions
  • SEP sesam Server >=
  • SEP sesam extension for Ingres DB
  • Previous installation of the standard Sesam Backup Client
  • working Sesam file system backup for this client


  • First, verify that the standard Sesam Backup Client is already installed
  • File system backup must be active for this SEP sesam Client
  • Login as root user
  • Unpack the file sesam_ingres_x.x.x.x.tgz in a temporary location
  • Copy ingres/sbc_ingres into $<$SESAM_ROOT$>$/bin/sesam directory

  root@db:~> cd /tmp                                                     
  root@db:/tmp> tar xvzf sesam_ingres.tgz                                
  root@db:/tmp> cp sesam_ingres_3.4.1.60/sbc_ingres /opt/sesam/bin/sesam


Complete database backup

In this case SEP sesam calls the Ingres executable ckpdb to perform a checkpoint. After saving all files of the checkpoint, a backup of the directories dump and journal is made. With this information a complete disaster recovery of a database is possible.

The backup source has the following format:

 <db name>@<path of config file>
Backup source has to be entered manually

In the current version, it is not possible to use the GUI file system browser to choose the backup source

Additional backup options

You can enter additional options for the tasks in Options 1->Save options by -a switch:

Delete the last checkpoint after the backup
Delete all checkpoints after the backup
dbuser=<ingres os user>
Use this OS account instead of the default user ingres


Uses the user ingres2 for the backup and deletes all checkpoints after a successful backup

 -a delete=all,dbuser=ingres2

Checkpoint backup

In this case SEP sesam acts as a Media Manager. Instead of the default tar command, database files are directly saved by SEP sesam Server. To use SEP sesam as a media manager an adopted check point template file has to be created:

  • Create a copy of the Default Template File:
 cp /opt/Ingres/IngresII/ingres/files/cktmpl.def /opt/Ingres/IngresII/ingres/files/cktmpl_sm.def
  • Adopt the template file:
 old:  WSDD: cd %D; /bin/tar cf %A *
 new:  WSDD: cd %D; /opt/sesam/bin/sesam/sbc_ingres ckpdb -b -j ingres -S barometrix -m LARGE %D %A
 old: WRDD: cd %D; /bin/tar xf %A
 new: WRDD: cd %D; /opt/sesam/bin/sesam/sbc_ingres rollforward -r -j ingres -S barometrix %D %A

The task (-j) has to be created in the SEP sesam GUI as described earlier.

  • Set the environment variable II_CKTMPL_FILE:
 export II_CKTMPL_FILE=/opt/Ingres/IngresII/ingres/files/cktmpl_sm.def

Certainly the Default Template can be adopted as well but then SEP sesam is always used for creating checkpoints.

The filename cktmpl_seseam.def is reserved because SEP sesam uses it internally.

Checkpoint is not sufficient for disaster recovery

If you only create checkpoints make sure that the directories dump and journal are saved by normal file system backups


Disaster Recovery

  • The database must exist before it can be recovered
  • SEP sesam backup log can help you to identify the data locations


If a complete backup was done with SEP sesam all necessary files can be restored with the SEP sesam GUI. In the restore wizard the backup of the configuration file has to be used, not the external checkpoint backup.

Select complete restore of selected task


Overwrite all exiting files
Auto recover after restore
Starts rollforward command after data restore
Auto recover and online after restore
Starts rollforward command after data restore

Hint: There is no difference between the two Auto recover options in case of an Ingres restore

Additional options

Point in time recover
checkpoint=<checkpoint number>
Using this checkpoint for recover

 -a until=01-aug-2009:07:13:58

File system restore

As data is saved in files these files can be restored into the file system. To do this, select a new target in restore wizard starting with /. There will be no Ingres specific processing in this case.


Restore all files into /tmp/ingresrestore