Redirecting an Informix restore to a different client
You have the option to restore an Informix database to a client other than the one that originally supplied the backup. This process of restoring data to a different client is called a redirected restore. You must be the NetBackup administrator to perform these tasks.
To perform a redirected restore, the following conditions must be present:
The source and the destination clients must have identical operating system versions and bit levels.
The source and the destination clients must have identical Informix database versions.
The Informix ownerId, Informix groupId, and Informix home must be identical on the source and on the destination clients.
For more information on redirected restores, see the NetBackup Administrator's Guide, Volume I.
If you use a non-root service user account, specific access must be allowed for that user when you add files to the /usr/openv/netbackup/db/altnames directory. The service user account must have full access to these files through the ownership or group and the permissions. For example, if the service user is svcname and its group is srvgrp, the file can have permissions of 400. If the file owner is for a different user and group, the file permissions must allow access to the service user. For example, 777. Equivalent permission settings must be used in a Windows environment.
To redirect an Informix restore to a different client
- Create the following file on the primary server:
/usr/openv/netbackup/db/altnames/client_name
For client_name, specify the name of the client that is allowed to perform the redirected restore. Add the name of the NetBackup for Informix source client to that file.
- Back up the logical logs on the NetBackup for Informix source client.
A logical log contains records of all the database activity that occurs between backups. These records contain all the database transactions that have taken place after the last backup.
Log into the source client as Informix ownerId and issue the following command:
onbar -b -l
- If the source client database server is down, salvage the logical logs.
This command backs up any logical logs that have not yet been backed up and are not corrupted or destroyed.
Log into the source client as Informix ownerId and issue the following command:
onbar -l -s
- Shut down the Informix database server on both the source client and the destination client.
Issue one of the following commands:
For Informix Dynamic Server:
onmode -ky
For Extended Parallel Server:
xctl onmode -ky
- On the NetBackup for Informix destination client, back up the files that reside in the $INFORMIXDIR/etc directory to preserve the original configuration. The following steps overwrite files in this directory.
- Copy configuration and informational files in the $INFORMIXDIR/etc directory from the NetBackup for Informix source client to the $INFORMIXDIR/etc directory on the NetBackup for Informix destination client.
You can use ftp(1) to copy files from the source client to the destination client.
Copy the emergency or the backup boot files.
For the Informix Dynamic Server, the emergency boot file is $INFORMIXDIR/etc/ixbar.servernum.
For the Extended Parallel Server, the backup boot file is $INFORMIXDIR/etc/Bixbar_hostname.servernum.
For servernum, specify the value of the SERVERNUM configuration parameter that is specified in the $INFORMIXDIR/etc/$ONCONFIG file.
Copy the connectivity information file, $INFORMIXDIR/etc/sqlhosts, which specifies how the client application finds and connects to an Informix database server .
Copy the database configuration file that the environment variable ONCONFIG specifies. This file is located in the $INFORMIXDIR/etc directory.
Copy the files that the Informix database server creates and updates every time a dbspace, blobspace, logical-log file, or chunk is added or deleted.
For Informix Dynamic Server, this file is $INFORMIXDIR/etc/oncfg_servername.servernum
For Extended Parallel Server and for each coserver this file is $INFORMIXDIR/etc/oncfg_servername.servernum.coserverid
The variables are as follows:
servernum
The value of the SERVERNUM configuration.
servername
The value of the DBSERVERNAME configuration.
coserverid
The ID of the coserver.
(Conditional) Copy file xcfg_servername.servernum.
Perform this step if you use the Extended Parallel Server. File xcfg_servername.servernum contains information about coserver location and dbslice definition.
In the file name, the variables are as follows:
servernum
The value of the SERVERNUM configuration.
servername
The value of the DBSERVERNAME configuration.
Configure the NetBackup for Informix destination client.
Set the INFXBSA_CLIENT environment variable to the host name of the source client.
(Conditional) Set the INFXBSA_SERVER environment variable to the NetBackup primary server that is used for the source client backup.
Perform this step if the NetBackup primary server that is used for the source client backup is different than the server that is specified in the bp.conf file on the destination.
Perform the redirected restore.
Log onto the NetBackup for Informix destination client as Informix ownerId.
Perform a physical restore.
Use the following command to restore storage spaces to their most recent backed-up state:
onbar -r -p
Perform a logical restore.
Use the following command to update the most recent backed-up version of the storage spaces with later transactions:
onbar -r -l