dbrestore - Database Restore

dbrestore [OPTIONS] [OTHERDA=]zipfile ...]

dbrestore [OPTIONS] --inject zipfile ...]

Use this utility to restore a data area to a previous state. The previous state must be one saved via dbbackup.

Program Option Description
[OTHERDA=]zipfile

OTHERDA is the name of the data area that the database content is to be restored to. Specify a value for this data area if its name is different than the name of the data area that the backup zip file was created from. zipfile is the name of the zip file that contains the database content to restore.

You can specify multiple data areas and zip files by specifying a space separated list of them. For example, you could restore several different data areas, each with a different zip file, or you could use the same backup zip file to restore database content to more than one data area.
--inject Load metadata to create data area. Internal use only.
-b or --brief Print summary only for each file.
--gridstatus= ID

Publish progress to grid. You can then use

managegrid getprogress

to see a list of all running programs, or you can use

managegrid getprogress ID

to see the status of this program. The value you specify for ID must be unique across the system for any programs being run with the gridstatus option.
-q or --quiet Quiet mode - only print errors.
--localize Apply the current configuration to the dictionary.
-T or --timings
--threads=count

Maximum active threads for processing, for example, --threads=3. If you use multiple threads, you may see a performance improvement. However, performance depends on other factors as well. Note that a very large table will be processed in a single thread.

The default number of threads is four.
-x N Copy N rows per transaction. Print timings
dataarea The data area you want to check the database definitions for.
-v errorlevel or --errorlevel= errorlevel

errorlevel, tracelevel, and verbose specified in any order, where:

  • errorlevel Print timings = {n}none | {f}atal | {e}rror | {w}arning (warning is the default)

  • tracelevel = 0:6 where 0 is no message and 6 is everything

  • verbose = whether to display exception stacktrace