Informix Dynamic Server 11.50 Fundamentals Exam 555 certification preparation, Part 8: Backup and restore

This tutorial is the eighth in a series of nine tutorials designed to help you become familiar with all the different aspects of IBM Informix Dynamic Server (IDS) and help you get ready for the IDS Fundamentals certification exam. In this part, which corresponds with Part 8 of the exam, learn about essential Informix Dynamic Server 11.50 database backup and restore concepts, and about ON-Bar and ontape utilities to back up and restore database server data. Learn also about table-level restore with archecker utility.

Note: The contents of this article were updated to include a new section on performing an external backup and restore of database server data.

Share:

Amit D. Vashishtha (vashisht@us.ibm.com), Advisory Software Engineer, IBM

Amit Vashishtha  photoAmit Vashishtha is a software engineer working in IBM's Informix Dynamic Server engineering team for the past several years. His experience includes supporting backup-and-restore, replication, and other Informix database server technologies.



Qian Tang (tangqian@cn.ibm.com), Informix Technical Support Engineer, IBM

Qian Tang photoQian Tang is an Informix support engineer on the Informix China Support Team. His experience includes IDS troubleshooting, backup and restore, and more.



11 March 2010 (First published 24 September 2009)

Also available in Russian Portuguese

Before you start

About this series

This complimentary series of nine tutorials has been developed to help you prepare for the IBM Informix Dynamic Server 11.50 Fundamentals certification exam (555). This certification exam will test your knowledge of entry-level administration of IDS 11.50, including basic SQL (Structured Query Language), how to install IDS 11.50, how to create databases and database objects, security, transaction isolation, backup and recovery procedures, and data replication technologies and purposes. These tutorials provide a solid base for each section of the exam. However, you should not rely on these tutorials as your only preparation for the exam.

About this tutorial

In this tutorial, learn about backup and restore concepts and processes, and about utilities to back up and restore database server data. The material provided here primarily covers the backup and restore objectives of the exam.

Objectives

After completing this tutorial, you should be able to gain a basic understanding of:

  • Essential backup and restore concepts
  • Configure ON-Bar for the storage manager
  • Back up database server data with ON-Bar
  • Restore database server data with ON-Bar
  • Set up configuration parameters for ontape
  • Back up database server data with ontape
  • Restore database server data with ontape
  • Table-level restore with archecker

Prerequisites

This tutorial is written for up-and-coming database administrators (DBAs). Basic IDS concepts knowledge is needed.

System requirements

To complete this tutorial, you do not need a copy of IDS. However, if you have one available to use, you will definitely get more out of the tutorial. If you don't have a copy already, you can download a free trial version (see Resources).


Backup and restore overview

Physical backup

A physical backup is a copy of data in storage spaces (dbspaces, blobspaces, sbspaces) maintained by the database server. This copy is typically stored on a secondary storage medium, like a disk or a tape. IDS supports three physical backup levels:

  • Level-0 backs up all the used data pages in the spaces specified to be backed up at the time backup began.
  • Level-1 backs up only the data pages in the specified storage spaces that were modified since the last level-0 backup at the time backup began.
  • Level-1 backs up only the data pages in the specified storage spaces that were modified since the last level-1 backup at the time backup began.

Logical-log backup

A logical-log backup is a copy of logical-log files, also stored on a disk or a tape typically. Logical-log files can be backed up either manually or automatically.

In a continuous logical-log backup, the database server automatically backs up each logical-log file as it becomes full, whereas, in a manual logical-log backup, the user needs to start the backup.

Performing frequent logical-log backups ensures that the data can be restored unto the latest transactions with consistency.

Note: You can back up storage spaces and logical logs only when the database server is in online, quiescent, or fast-recovery mode. You can not back up offline or temporary storage spaces.

Restore

In the event of data loss due to disk failure or database corruption, the database server data can be recreated from the storage spaces backup and logical-logs backup. This process is called restore. There are three types of restores:

  • In a cold restore, you restore data while the database server is offline. Typically, a cold restore salvages the logical logs, restores the critical storage spaces (root dbspace and the dbspaces that contain the physical log and logical-log files), other storage spaces, and the logical logs.
  • In a warm restore, you restore non-critical storage spaces while the database server is online or quiescent. A warm restore consists of a restore of one or more non-critical storage spaces and a logical-log backup followed by a logical restore.
  • In a mixed restore, you do a cold restore of some storage spaces, typically the critical storage spaces, followed by a warm restore of the remaining non-critical storage spaces.

The restore is comprised of two phases:

  • The physical restore phase, which restores data from the latest level-0, level-1, and level-2 physical backups.
  • The logical restore phase, which restores transactions from the logical-log backups.

Backup and restore utilities

IDS provides the following utilities to backup and restore data:

ON-Bar

ON-Bar provides support for IDS data to be backed up to and restored from a storage manager. The storage manager is responsible for managing backups and storage devices. You can back up and restore all or select storage spaces in parallel or serial using ON-Bar. During a backup, ON-Bar gets the data residing in the storage spaces and logical logs from the database server and passes it on to the storage manager, which is responsible for storing the data on storage devices. During a restore, ON-Bar gets the backed-up data from the storage manager and passes it on to the database server for recreating the data on the server.

During a parallel backup or restore, the main onbar driver creates one child onbar process corresponding to each storage space being backed up or restored.

In a serial backup or restore, the onbar driver performs the operation on one storage space at a time. Logical logs are always processed serially.

The onbar processes write status and error messages to the ON-Bar activity log file and information required for a cold restore to the emergency boot file. ON-Bar also updates the catalog tables in the sysutils database to track backup and restore operations.

ontape

The ontape utility also backs up and restores storage spaces and log files, but it does not use a storage manager. Instead, it directly writes database server data to the secondary storage medium, such as a disk or a tape. It also allows you to change the logging status of a database.

Storage manager

The storage manager application manages the storage devices containing backups. ON-Bar and the storage manager exchange data through the X/Open Backup Services Application Programmer's Interface (XBSA) during backup and restore. Though, IDS product is packaged with ISM, On-Bar can work with other storage managers that use XBSA API.

IBM Informix Storage Manager (ISM)

The ISM server can store data on variety of storage devices such as tape, file system or optical disk. ISM runs on the same computer as ON-Bar and IDS. It manages storage devices, and supports data compression and encryption. You can configure up to four storage devices with ISM.


Configure ON-Bar with ISM

You must configure ISM and start it before backing up IDS data with ON-Bar. Also make sure that ISM is ready to receive data before performing a backup. This section provides the information that you need to set up ON-Bar to backup and restore with ISM.

Configuring ISM

You need to have an entry for ISM in the sm_versions file. If this file is not present already, copy the sm_versions.std template file to the file $INFORMIXDIR/etc/sm_versions on UNIX® or %INFORMIXDIR%\etc\sm_versions on Microsoft® Windows®. This file has the following format:

1|XBSA_ver|sm_name|ism_ver

XBSA_ver is the XBSA shared library release version for ISM. sm_name is the storage manager name (in other words, ISM). sm_ver is the ISM version.

The following example shows an ISM definition in the sm_versions file:

1|1.0.1|ism| ISM.2.20.UC1.119|

Configuring third-party storage manager

You need to do the following to configure a third-party storage manager to backup and restore with ON-Bar:

  1. Set ON-Bar configuration parameters in the onconfig file and any storage manager specific environment variables.
  2. Setup the storage manager so that ON-Bar can transfer data to and from it. Configure the storage devices.
  3. Create an entry for the storage manager in the sm_versions file.
  4. Verify that the BAR_BSALIB_PATH configuration parameter or environment variable points to the XBSA shared library for the storage manager.

Configuring ON-Bar

To use ON-Bar with ISM, you need to set the specific parameters in the ONCONFIG file as outlined in Table 1:

Table 1. ON-Bar configurations
Configuration parameterPurpose
ALARMPROGRAMAutomatically backs up log files as they become full, if set to $INFORMIXDIR/etc/log_full.sh on UNIX® or %INFORMIXDIR%\etc\log_full.bat on Microsoft® Windows®.
BACKUP_FILTERSpecifies the path name of an external filter program used in data transformation while backing up data.
BAR_ACT_LOGSpecifies the full path name of the ON-Bar activity log file.
BAR_BSALIB_PATHSpecifies the full path name of the storage manager XBSA shared library.
BAR_DEBUGSpecifies the debugging level for information output to ON-Bar debug log file.
BAR_DEBUG_LOGSpecifies the path name of the ON-Bar debug log.
BAR_IXBAR_PATHSpecifies the location of the ON-Bar boot file.
BAR_HISTORYSpecifies whether the sysutils database maintains the backup history when you use onsmsync to expire old backups.
BAR_MAX_BACKUPSpecifies the maximum number of onbar processes allowed per onbar command.
BAR_NB_XPORT_COUNTSpecifies the number of shared memory data buffers for exchanging data with server.
BAR_PERFORMANCESpecifies the type of performance statistics recorded in the activity log.
BAR_PROGRESS_FREQSpecifies the frequency of the progress messages for backup or restore operations in activity log.
BAR_RETRYSpecifies how many times ON-Bar should retry a backup or restore operation if the first attempt fails.
BAR_XFER_BUF_SIZESpecifies the size in pages of shared memory data buffers for exchanging data with server.
ISM_DATA_POOLSpecifies the ISM volume pool for backing up storage spaces.
ISM_LOG_POOLSpecifies the ISM volume pool for backing up logical logs.
LTAPEDEVSpecifies whether to back up logs.
RESTARTABLE_RESTOREEnable or disable restart able restores.
RESTORE_FILTERSpecifies the path name of an external filter program for restoring transformed data to its original state.

Back up IDS data with ON-Bar

You can perform following types of backups with ON-Bar:

Standard backup

In a standard backup the database server performs a checkpoint for each storage space as it is backed up. Hence, you must restore the logical logs from a standard backup for data consistency. You can set the number of parallel onbar processes to run with the BAR_MAX_BACKUP configuration parameter, or can force a standard backup to run as a serial backup by setting it to 1. ON-Bar supports both full (level-0) and incremental (level-1 and level-2) standard backups of storage spaces. By default, ON-Bar performs a level-0 backup.

Examples

To perform a standard level-0 backup of all online non-temporary storage spaces and used logical logs, you can use the following command:

  • onbar -b -L 0

To perform a level-0 backup of specific storage spaces (for example, two dbspaces named dbspace1 and dbspace2) and logical logs use the following command:

  • onbar -b dbspace1 dbspace2

To perform a level-1 incremental backup, use the following command:

  • onbar -b -L 1

Whole-system backup

A whole-system backup (onbar -b -w) is a serial or parallel backup of all storage spaces and logical logs based on a single checkpoint. A whole-system backup can be restored without the logical logs, as the data in all storage spaces is consistent in this backup. You can perform an incremental (level-1 or level-2) whole-system backup in conjunction with a level-0 whole-system backup.

Examples

To perform a level-0 whole-system backup of all online non-temporary storage spaces and logical logs, you can use the following command:

  • onbar -b -w -L 0

To perform a level-1 whole-system backup use the following command:

  • onbar -b -w -L 1

Physical backup

A physical backup only backs up storage spaces. You can perform a physical back up of specific or all storage spaces using On-Bar.

Example

To perform a physical backup of all online non-temporary storage spaces, use the following command:

  • onbar -b -p

Logical-log backup

You must back up logical logs if you perform standard backup because you must restore both the storage spaces and logical logs.

Examples

To perform a backup of full logical-log files manually, use the following command:

  • onbar -b -l

To perform a backup of current logical-log file as well as other full logical-log files, use the following command:

  • onbar -b -l -c

To start a continuous logical-log backup, use the following command (it runs indefinitely, waiting for logical logs to fill; to stop, kill the ON-Bar logical log backup process):

  • onbar -b -l -C

Log salvage

ON-Bar backs up logical logs automatically before it restores the root dbspace in a cold restore except when a physical restore only is specified. To avoid any data loss, manually salvage the logical logs before starting the cold restore, if the device containing the logical logs is still available or you plan to perform a physical restore only.

Example

To salvage the logical logs manually, run the following command:

  • onbar -b -l -s

Verifying backups

To verify a backup of all storage spaces, use the following command:

  • onbar -v

The logical logs are not verified. To verify the backup of storage spaces listed in a file dbsfile, use the following command:

  • onbar -v -f dbsfile

To perform a point-in-time verification, use the following command:

  • onbar -v -t "YYYY-MM-DD HH:MM:SS"

To verify a whole-system backup, run the following command:

  • onbar -v -w

Restore IDS data with ON-Bar

You can perform the following types of restores with ON-Bar:

Cold restore

If the database server fails because a critical dbspace is damaged due to a disk failure, you must perform a cold restore of all critical dbspaces. The database server must be offline for a cold restore.

A cold restore first restores all critical storage spaces, then the non-critical storage spaces, and finally the logical logs. After the restore completes, the database server goes into quiescent mode. It can be brought online using the onmode command.

Example

Do the following to perform a cold restore with log salvage:

  • Copy the following files to another location: ONCONFIG, sqlhosts (UNIX only), emergency boot files and oncfg files
  • Take the database server offline using onmode -ky
  • Salvage the logical log files on the damaged disk using (onbar -b -l -s), and then replace the disk
  • Copy the previously saved files to their original locations. You do not need to copy the administrative files if performing a cold restore because a critical dbspace was lost
  • Restore the storage spaces using onbar -r
  • Bring the database server online when the restore completes using onmode -m

To restore specific storage spaces (for example, the only critical dbspace named rootdbs and a non-critical dbspace named dbspace1) with -r option, use the following command:

  • onbar -r rootdbs dbspace1

You also need to perform a cold restore for one of the following tasks:

Whole-system restore

A whole-system restore requires a whole-system backup, though it does not require you to restore the logical logs.

You can restore a whole-system backup with any of the following commands:

  • onbar -r -w # Whole-system restore with automatic log salvage
  • onbar -r # Standard restore of the whole-system backup
  • onbar -r -p -w # Physical-only whole-system restore (no log salvage)
  • onbar -r -t time -w # Whole-system point-in-time restore

If you perform a physical-only whole-system restore, the database server comes into fast recovery mode after restore completes. Either perform a logical restore or bring the server online using onmode.

Point-in-time restore

A point-in-time restore enables the database server to be restored to a state it was in at a particular point in time. It is typically used in recovering from a mistake such as dropping a database accidentally. In this case, you can restore the server to a point in time just before you dropped the database.

Example

To restore database server data to a specific date and time, enter the following command:

  • onbar -r -t "YYYY-MM-DD HH:MM:SS"

In this example, the restore replays transactions that committed on or before the specified time.

Point-in-log restore

A point-in-log restore is similar to a point-in-time restore. It restores data to the time of the last committed transaction listed in the specified logical log.

Example

To perform a point-in-log restore to log number 8, use the following command:

  • onbar -r -n 8

Imported restore

In an imported restore, the data is restored to a different database server instance than the one from which the data was backed up. The XBSA and storage manager versions must be compatible between backup and restore operations.

Rename chunks restore

You can rename chunks by specifying new chunks paths and offsets during a cold restore. This option can be used for restoring storage spaces to different path names than the one on which the backup was performed.

Examples

To rename chunk (path: /chunk_old and offset: 0) to (path: /chunk_new and offset: 20000) by supplying path names on the command line, use this command:

  • onbar -r -rename -p /chunk_old -o 0 -n /chunk_new -o 20000

You need to perform a level-0 archive after the rename chunks restore completes.

Warm restore

You can restore a non-critical storage space in a warm restore if the storage space is down and the database server is not offline.

Examples

To perform a warm restore of all down storage spaces, use the following command:

  • onbar -r

To perform a warm restore in stages, do the following:

  1. Perform a physical restore using onbar -r -p
  2. Back up the logical logs using onbar -b -l
  3. Perform a logical restore using onbar -r -l

Mixed restore

A mixed restore is a cold restore of all critical storage spaces followed by warm restore of remaining storage spaces. Since not all storage spaces are restored during the initial cold restore, the server can be brought online faster than if you were to perform a cold restore of all the storage spaces.

Logical-log restore

To perform a logical restore, use the following command:

  • onbar -r -l

The logical log files are replayed using a temporary space during a warm restore, hence make sure that you have enough temporary space for the logical restore.

Restartable restore

If a failure occurs during a restore, you can restart the restore from the place where it failed. The RESTARTABLE_RESTORE parameter is ON by default. To restart a failed restore, issue the following command:

  • onbar -RESTART

If the failure occurs during a physical restore, ON-Bar restarts the restore at the storage space at level where the failure occurred.

If a failure occurs during a cold logical restore, ON-Bar restarts the logical restore from the latest checkpoint.

Restartable restore does not work for the logical part of a warm restore.


Set up configuration parameters for ontape

This section explains configuration parameters in the ONCONFIG file that the ontape utility uses for backup.

Tape device parameters

Table 2 identifies the parameters that specify tape device characteristics for storage-space backups:

Table 2. Tape device parameters for storage-spaces backups
Configuration parameterPurpose
TAPEDEVSpecifies the path name of the tape device or file system directory where ontape will write storage space data during a backup and from which it will read data during a restore.

Set TAPEDEV to STDIO to configure ontape to use standard input and output.
TAPEBLKSpecifies the block size of the tape used for storage space backups in kilobytes.
TAPESIZESpecifies the size of the tapes used for storage space backups in kilobytes. Set TAPESIZE to 0 to use the full physical capacity of tape device.

Logical-log backup tape device parameters

Table 3 lists the parameters that specify tape device characteristics for logical-log backups:

Table 3. Tape device parameters for logical-log backups
Configuration parameterPurpose
LTAPEDEVSpecifies the path name of the tape device or file system directory where ontape will write logical-log data during a backup and from which it will read data during a restore.

When you specify NULL logical-log backup device, you avoid backing up logical-logs. However, you can only restore data upto the most recent physical backup in this case.
LTAPEBLKSpecifies the block size of the tape used for logical-log backups in kilobytes.
LTAPESIZESpecifies the size of the tapes used for logical-log backups in kilobytes. Set LTAPESIZE to 0 to use the full capacity of tape device.

Filter parameters

Table 4 identifies the parameters that specify the filter to transform date prior to backup and following restore:

Table 4. Filter parameters
Configuration parameterPurpose
BACKUP_FILTERSpecifies the path name of an external filter program used in data transformation prior to backing it up.
RESTORE_FILTERSpecifies the path name of an external filter program used in transformation of data back to its original state during a restore.

The data must have been transformed with the BACKUP_FILTER parameter during the backup.

Back up IDS data with ontape

This section describes how to use ontape to back up storage spaces and logical log files.

Storage space backup

The ontape utility supports level-0, level-1, and level-2 backups of storage spaces. It backs up the storage spaces in the following order: root dbspace, blobspaces, sbspaces, and dbspaces.

Before you begin to create a backup with ontape, ensure that the location specified by the TAPEDEV parameter is write-enabled.

Examples

To start a level-0 backup to tape, execute the following command:

  • ontape -s -L 0

To start a level-0 backup to a directory without prompts, execute the following command:

  • ontape -s -L 0 -d

To create a level-0 backup to standard output file named level_0_backup in current directory, execute the following command:

  • ontape -s -L 0 level_0_backup -t STDIO

Logical-log backup

You must only use ontape to back up logical log if you use it to back up storage spaces.

Automatic logical log file backup

To back up all full logical logs manually, use the following command:

  • ontape -a

This command also prompts to switch the logical log after backing up the current log.

Continuous logical log file backup

When you start a continuous log backup, the database server automatically backs up each logical log file when it becomes full. Hence, you will never lose more than a partial logical log file. It does not back up the current logical-log file.

To start a continuous logical-log backup, use the following command:

  • ontape -c

You can also create a continuous logical-log file backup to a directory.

To end continuous logical-log backup, press the Interrupt key (Ctrl+C).


Restore IDS data with ontape

This section describes how to use ontape to restore storage spaces and logical log files.

Cold restore

The database server must be offline to perform a cold restore.

You can salvage the logical logs when the cold restore starts. The ontape utility prompts you to salvage the logical logs.

The ontape utility then prompts you to mount the tapes with backup data. When restoring from a directory, ontape prompts you for the path name of the directory. You can avoid the prompt by using -d option.

At the end of restore, the database server remains in quiescent mode and can be switched to online mode.

Examples

Execute the following command to restore all the storage spaces:

  • ontape -r

To perform a physical restore from the standard input file level_0_backup, you can execute the following command:

  • cat level_0_backup | ontape -p

Rename chunks restore

You can rename chunks during a cold restore with ontape.

Example

To rename chunk (path: /chunk_old and offset: 0) to (path: /chunk_new and offset: 20000) by supplying path names on the command line, use this command:

  • ontape -r -rename -p /chunk_old -o 0 -n /chunk_new -o 20000

Perform a level-0 backup after the rename chunks restore completes.

Warm restore

When you restore only some of your storage spaces during the cold restore (you must restore critical storage spaces), you can perform a warm restore of the remaining storage spaces after database server is online.

At the end of the warm restore, the down storage spaces are marked online.

Examples

To warm restore selected dbspaces (dbspace1 and dbspace2) after restoring critical dbspaces as part of cold restore, use the following command:

  • ontape -r -D dbspace1 dbspace2

In the following example, ontape performs a warm restore of dbspace1 from standard input file level_0_backup :

  • cat level_0_backup | ontape -r -D dbspace1 -t STDIO

Mixed restore

When you perform a mixed restore, you restore only critical storage spaces and, optionally, one or more non-critical storage spaces during the cold restore.

Example

To perform a cold restore of critical storage spaces (rootdbs, llogdbs, and plogdbs), followed by warm restore of other storage spaces (dbspace1 and dbspace2), you can do the following:

  • ontape -r -D rootdbs llogdbs plogdbs
  • ontape -r -D dbspace1 dbspace2

Logical-log restore

You must restore all the logical log files backed up after the last level-0 backup when you perform a mixed restore.

When you perform a full restore, you have the option to not restore logical log files.

To restore the logical logs, use the following command:

  • ontape -l

External backup and restore

An external backup or restore operation is performed external to IDS, without using ON-Bar or ontape during the backup or restore. The data is backed up or restored using a third-party tool instead.

External backup

The following is a summary of steps required to perform an external backup:

  1. Block the database server using onmode -c block.
  2. Back up all the storage spaces and administrative files using a third-party tool or copy command.
  3. Unblock the database server using onmode -c unblock.
  4. Back up all the logical logs including the current log using ontape -a (ontape) or onbar -b -l -c (ON-Bar).

External restore

The following is a summary of steps required to perform an external restore:

  1. Salvage the logical logs using ontape -S (ontape) or onbar -b -l -s (ON-Bar).
  2. Restore all the storage spaces from an external backup to the original locations using a third-party tool or copy command.
  3. Perform an external restore of all storage spaces and logical logs using ontape -p -e followed by ontape -l (ontape) or onbar -r -e (ON-Bar).

Table-level restore with archecker

This section describes table-level restore using the archecker utility.

To restore a table using the archecker utility you need to specify the source table from where the data will be extracted, the destination table where the data will be restored and an INSERT statement which will associate the source table with the destination table in a schema reference file.

archecker configuration parameters

The archecker utility uses a configuration file to specify archecker specific parameters. Set the AC_CONFIG environment variable to the path name of the archecker configuration file. This environment variable is set to $INFORMIXDIR/etc/ac_config.std on UNIX® or %INFORMIXDIR%\etc\ac_config.std on Microsoft® Windows® by default.

Table 5. archecker configuration parameters
Configuration parameterPurpose
AC_IXBARSpecifies the location of the On-Bar boot file.

AC_LTAPEBLOCKSpecifies the size of the tape block for log backup.
AC_LTAPEDEVSpecifies the device name used by the ontape utility for log backup.
AC_MSGPATHSpecifies the location of the archecker message log.
AC_RESTORE_FILTERSpecifies the path name of the filter program that restores transformed data to its original state.
AC_SCHEMASpecifies the location of the archecker schema command file.
AC_STORAGESpecifies the location of the directory where archecker stores temporary files.
AC_TAPEBLOCKSpecifies the size of the tape block for storage space backup.
AC_TAPEDEVSpecifies the device name used by the ontape utility for storage space backup.
AC_VERBOSESpecifies either verbose or terse output in the archecker message log and screen.

Schema command file

The archecker utility uses a schema command file to specify the source and destination tables. This file uses an SQL-like language for information archecker uses to perform table-level restore.

Example

The example schema command file in Listing 1 restores a table from the most recent level-0 backup. The data is restored to table test:tlr. Logs are applied to bring the table to the latest point in time.

Listing 1. Sample schema command file
                    database test;
                    create table tlr (a_serial serial, b_integer integer, c_char char); 
                    insert into tlr select * from tlr;

Restoring with archecker

The archecker utility can perform two types of restores:

  • A physical restore from a level-0 backup
  • A physical restore followed by a logical restore to a specific point in time

Archecker determines the type of restore to perform from the command file. By default, archecker performs a physical followed by logical restore unless you use the WITH NO LOG clause in the command file, in which case archecker does not perform a logical restore.

Example

To perform a table-level restore consisting logical restore from a tape backup, use the following command (where schema_file is the name of archecker schema command reference file):

  • archecker -tvsX -f schema_file

To perform a physical-only restore, use the following command:

  • archecker -tvsX -f schema_file -lphys

Conclusion

After reading this tutorial, you should have a better understanding of the following:

  • Essential backup and restore concepts
  • Setting up On-Bar, ontape, and archecker configuration parameters
  • Backing up IDS server data with ON-Bar and ontape utilities
  • Restoring IDS server data with ON-Bar, ontape, and archecker utilities

Resources

Learn

Get products and technologies

Discuss

Comments

developerWorks: Sign in

Required fields are indicated with an asterisk (*).


Need an IBM ID?
Forgot your IBM ID?


Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.

 


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name



The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.

 


All information submitted is secure.

Dig deeper into Information management on developerWorks


static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Information Management
ArticleID=430447
ArticleTitle=Informix Dynamic Server 11.50 Fundamentals Exam 555 certification preparation, Part 8: Backup and restore
publish-date=03112010