Performing Physical Restore for a Full-System Cold Restore (ON-Archive)
Use
This is the second stage in a
full-system cold restore of the Informix database if you use ON-Archive as your data recovery tool (that is, for your archives and backups).Prerequisites
Mount the volume with the archived data.
Press the return key when ready.
What saveset ID is to be used on volume /dev/rmt/0m?:
Procedure
You normally start with the latest available level-0 archive. For more information about identifying the required tapes, see
Preparing for Full-System Cold Restore (ON-Archive).In this example for a parallel archive, you would enter
1 as your first save set ID, corresponding to the ON-Archive request ID that created this save set. For more information about where to find the correct save set ID, see the message Created request #00000001# in Preparing for Full-System Cold Restore (ON-Archive).
The save set ID is usually the same as the request ID of the
ON-Archive request that created it. If you cannot identify the ID, enter the following command to determine the IDs of save sets on your tapes:$ ondatartr 'list/tape=(/dev/rmt/0m)'
The
list command might take a long time (especially if the volume contains a continuous backup). You need to perform it for each archive and backup volume. You can interrupt the command with CTRL-C once you see the volume header. To avoid having to use the list command, fully label your tape volumes after archives or backups by writing all relevant information on the tape itself.The physical restore starts after you enter the save set ID. Each dbspace is restored in sequence starting with
rootdbs . The dialogue continues as follows:Level 0 physical restore started.
The file rootdbs has been retrieved.
The file physdbs has been retrieved.
......... .........
The file psapbtab has been retrieved.
End of level 0 archived reached on this volume.
Does this saveset continue on another volume? (Y/N)
If the save set currently being restored covers more than one volume, enter
Y and mount the continuation volume. If there are no more volumes for the save set, enter N and the dialogue continues.If you have a level-1 archive corresponding to the level-0 archive for the dbspace set already restored, then answer
Y to the following prompt. Make sure that you do in fact have the tape available. If you enter Y and there is no tape, you might have to restart the entire restore.Do you have a level 1 archive to retrieve? (Y/N): Y
Mount the volume with the archived data.
Press the return key when ready.
What saveset ID is to be used on volume/dev/rmt/0m?: 60
Follow the same procedure if you have a level-2 archive corresponding to the level-0 and level-1 archives for the dbspace set already restored.

In a restore from a normal sequential archive (where
dbspaceset=* ), the physical restore is finished after you have done steps 1 to 3 once. If you are doing this kind of restore, go straight to step "Bring the database server back up without a logical restore".Once the dbspace set containing
Recovery Mode
$ ondatartr 'retrieve/dbspaceset= SET0000072B/tape=(/dev/rmt/0m)'
Dbspace set
SET0000072B contains dbspaces not yet restored.If you have several remaining dbspace sets to restore and have sufficient tape devices and terminal windows, you can restore the other dbspace sets in parallel by entering a series of commands like the one shown above, one for each dbspace set to be restored. For example:
$ ondatartr 'retrieve/dbspaceset= SET0000072C/tape=(/dev/rmt/1m)'
$ ondatartr 'retrieve/dbspaceset= SET0000072D/tape=(/dev/rmt/2m)'

Remember that you must do a
logical restore if you are restoring in parallel. The logical-log files are required to synchronize the components of the parallel archive.If you do not want to do a logical restore (only possible if you have used a sequential archive for your restore, that is,
$ onmode -s
$ onmode -m
If you enter this command before quiescent mode is reached, you might encounter problems.
However, SAP recommends you to perform a logical restore if you have the necessary logical-log backups.
You can see the results by looking in the
Apr 06 1995 10:55:07 #00000000# <20214> ondatartr (informix) Begin retrieve dbspaces
10:57:08 #00000000# <20214> Retrieve rootdbs #00000002# from DBTAP:DBT1:/dev/rmt/0m
11:58:00 #00000000# <20214> Retrieve psapsource #00000002# from DBTAP:DBT1:/dev/rmt/0m
11:58:01 #00000000# <20214> Retrieve physdbs #00000002# from DBTAP:DBT1:/dev/rmt/0m
12:29:30 #00000000# <20214> Retrieve psappool #00000002# from DBTAP:DBT1:/dev/rmt/0m
12:29:30 #00000000# <20214> Retrieve psapuser1 #00000002# from DBTAP:DBT1:/dev/rmt/0m
12:29:33 #00000000# <20214> Retrieve logdbs #00000002# from DBTAP:DBT1:/dev/rmt/0m
12:54:32 #00000000# <20214> Retrieve psapddic #00000002# from DBTAP:DBT1:/dev/rmt/0m
13:45:11 #00000000# <20214> Retrieve psapstab #00000002# from DBTAP:DBT1:/dev/rmt/0m
13:49:30 #00000000# <20214> Retrieve psapclu #00000002# from DBTAP:DBT1:/dev/rmt/0m
14:13:31 #00000000# <20214> Retrieve psapload #00000002# from DBTAP:DBT1:/dev/rmt/0m
14:22:03 #00000000# <20214> Retrieve psapbtab #00000002# from DBTAP:DBT1:/dev/rmt/0m
15:00:56 #00000000# <20214> Retrieve psapdocu #00000002# from DBTAP:DBT1:/dev/rmt/0m
15:02:39 #00000000# <20214> Retrieve psapprot #00000002# from DBTAP:DBT1:/dev/rmt/0m
Apr 06 1995 15:02:54 #00000000# <20214> ondatartr (informix) End retrieve dbspaces: SUCCESS
Result
Now that you have performed the physical restore the database server goes into fast-recovery mode. You can go on to the next stage,
Performing Logical Restore for Full-System Cold Restore (ON-Archive).
See also:
Informix documentation