1 – backup-file-spec
A file specification for the backup file produced by a previous RMU Backup command. Note that you cannot perform a remote restore operation on an .rbf file that has been backed up to tape and then copied to disk. The default file extension is .rbf. Depending on whether you are performing a restore operation from magnetic tape, disk, or multiple disks, the backup file specification should be specified as follows: o To restore from magnetic tape: If you used multiple tape drives to create the backup file, the backup-file-spec parameter must be provided with (and only with) the first tape drive name. Additional tape drive names must be separated from the first and subsequent tape drive names with commas, as shown in the following example: $ RMU/RESTORE /REWIND $111$MUA0:PERS_FULL_NOV30.RBF,$112$MUA1: o To restore from single or multiple disk files: If you used multiple disk files to create the backup file, the backup-file-spec parameter must be provided with (and only with) the first disk device name. Additional disk device names must be separated from the first and subsequent disk device names with commas. You must also be sure to include the Disk_ File qualifier. For example: $ RMU/RESTORE/DISK_FILE DISK1:[DIR1]MFP.RBF,DISK2:[DIR2],DISK3:[DIR3] As an alternative to listing the disk device names on the command line (which, if you use several devices, can exceed the line-limit length for a command line), you can specify an options file in place of the backup-file-spec. For example: $ RMU/RESTORE/DISK_FILE "@DEVICES.OPT" The contents of devices.opt might appear as follows: DISK1:[DIR1]MFP.RBF DISK2:[DIR2] DISK3:[DIR3] The backup files referenced from such an options file are: DISK1:[DIR1]MFP.RBF DISK2:[DIR2]MFP01.RBF DISK3:[DIR3]MFP02.RBF
2 – storage-area-name
storage-area-name[,...] A storage area name from the database. This parameter is optional. Use it in the following situations: o When you want to change the values for thresholds or blocks per page. o When you want to change the names specified with the Snapshot or the File qualifier for the restored database. o If you want to restore only selected storage areas from your backup file, you must use the Area qualifier and specify the names of the storage areas you want to restore in either the storage-area-name parameter in the RMU Restore command line, or in the file specified with the Options qualifier. To use this option, specify the storage area name rather than the file specification for the storage area. By using the RMU Backup and RMU Restore commands, you can back up and restore selected storage areas of your database. This Oracle RMU backup and restore by-area feature is designed to: o Speed recovery when corruption occurs in some (not all) of the storage areas of your database. o Reduce the time needed to perform backup operations because some data (data in read-only storage areas, for example) does not need to be backed up with every backup operation performed on the database. If you plan to use the RMU Backup and RMU Restore commands to back up and restore only selected storage areas for a database, you must perform full and complete backup operations on the database at regular intervals. A full and complete backup is a full backup (not an incremental backup) operation on all the storage areas in the database. If the database root (.rdb) file is corrupted, you can only recover storage areas up to (but not past) the date of the last full and complete backup operation. Therefore, Oracle Corporation recommends that you perform full and complete backup operations regularly. If you plan to back up and restore only selected storage areas for a database, Oracle Corporation strongly recommends that you enable after-image journaling for the database (in addition to performing the full and complete backup operation on the database as described earlier). That is, if you are not backing up and restoring all the storage areas in your database, you should have after-image journaling enabled. This ensures that you can recover all the storage areas in your database in the event of a system failure. If you do not have after-image journaling enabled and one or more of the areas restored by RMU Restore are not current with the storage areas not restored, Oracle Rdb will not allow any transactions to use the storage areas that are not current in the restored database. In this situation, you can return to a working database by restoring the database, using the backup file from the last full and complete backup operation on the database storage areas. However, any changes made to the database since the last full and complete backup operation was performed are not recoverable. If you have after-image journaling enabled, use the RMU Recover command to apply transactions from the .aij file to storage areas that are not current after the RMU Restore command completes. When the RMU Recover command completes, your database will be consistent and usable.