IMG.LOAD

Restores a physical backup of a database.

Caution

IMG.LOAD completely overwrites the contents of the database.

Note: The LOAD-IMAGE Proc calls IMG.LOAD and should be used in preference to it.

Syntax

IMG.LOAD {(options}

Options

Y Automatically answers Y to the Ok to continue? prompt.

Restrictions

IMG.LOAD is only available in the SYSMAN account.
IMG.LOAD may only be run by the database owner.
Only one instance of IMG.LOAD may be run at a time on a database. IMG.LOAD cannot be run at the same time as any of the other physical save and restore commands.

See also the Overview of Save and Restore.

Comments

IMG.LOAD uses the tape unit(s) currently attached to the default channel.

IMG.LOAD locks the target database and shuts it down (logging off all users) before starting to load the data. Its previous lock state is restored when the load completes unless the load fails, in which case the database is left locked.

IMG.LOAD can only restore a complete database. To restore individual files, restore the backup to a new database (created with mkdbase) and then use remote accounts and files to access its contents. The database may have a different configuration (in terms of number of stripes and stripe size) from the original database, but must be large enough to contain the data – IMG.LOAD fails immediately if the skeleton database is not large enough.

The internal name of the restored database will be the same as that from which it was saved. To change the internal name to match that in the ROUTE-FILE, use the CUSTOMER.IDENT TCL command. The internal database name is used by TCL commands such as WHO.

If a CREATE-INDEX or DELETE-INDEX was in progress when the database was saved, the index concerned will be incomplete when restored and this could result in an unexpected reduction in performance. You can identify the incomplete indexes with LIST-INDEXES; the indexes concerned are marked as invalid. Incomplete indexes must be deleted and recreated if required.

If the data on the tape is encrypted, your REK file must contain the correct encryption keys to allow your users access. If transferring data from another database, you must load the keys (using the LOAD-REK command) after the restore has completed, so that the REK file is not overwritten. Refer to Copying Encrypted Data to another Host for more details.

Procedure

Ensure that the tape is loaded and on-line, that the tape is write-protected, and you are logged on to SYSMAN.
Use T-ATT or ASSIGN to attach the required tape units to the default channel.

Note: If your backup was saved using multi-deck parallel save, you must attach the same number of tape units as used when saving. If you need more tapes than you have tape decks, you can use tape images as additional decks.
Enter at the TCL prompt:
```
IMG.LOAD
```

You are then prompted:

This operation will log off all users from databasePath
and will overwrite the database.
OK to continue? [N/Y/Q]

Enter Y to continue, or N or Q to exit.

Unless an obvious problem is detected during start up (such as no tape being attached), IMG.LOAD then exits from Reality and runs the realload host command. On completion you will be prompted
```
Hit <return> to exit
```
When you respond to this prompt, if you are logged on to Reality locally, you will be returned to the host system prompt; if you are connected directly to Reality over a network, your network connection will be broken.

Example

:T-DEVICE 1 C:\TEMP\FASTBACKUP.RTI:C2 9

:T-ATT
[1021] Device(s) TAPE 1 now assigned,
       record size = 8000     density = 0.

:IMG.LOAD

 This operation will log off all users from C:/Databases/fbtest
 and will overwrite the database.
 OK to continue? [N/Y/Q]Y
 100% complete
Load complete in 00 hrs 00 mins 01 secs
Image Load completed.
Hit <return> to exit...