Open topic with navigation
After successful execution of either hot copy on an SSM or a copy operation on a stopped SSM, you have the snapshot whose state you want to restore to. You also have the archive and journal data that is needed to create a new archive that provides the database state captured by the snapshot of interest. You are ready to invoke the
nuochk utility to restore to that snapshot. Execution of the
nuochk utility is the only way to restore to a snapshot.
nuochk restore operation is an offline operation. You do not restore to the snapshot on a running database. Neither the source nor the target archives can be in use by a running database. The
nuochk restore operation creates a new archive and you can then specify this archive when starting an SM or SSM.
nuochk utility is in the
NUODB_HOME/bin directory. The format for invoking
nuochk to restore to a snapshot is as follows:
nuochk --repair --restore-snapshot
|--repair||Required. Execution of
Required. Specify the ID of the snapshot you want to use to restore data. For example:
|--restore-dir destination_dir||Required. Specify a file system directory that will contain the restored archive. This directory must not exist. For example: ‑
Specify the directory that contains the snapshot you want to restore
to. This snapshot archive must be the result of a hot copy operation.
|--journal enable||Required. The
Specify the path of the journal directory that was the result of the
|location||Required. Specify the path of the archive directory that was the result of the
nuochk --repair --restore-snapshot 123456 --restore-dir /tmp/archive-at-snapshot-123456 --snapshot --snapshot-archive /tmp/hotcopy/1/snapshots --journal enable --journal-dir /tmp/hotcopy/1/journal /tmp/hotcopy/1/archive
For more information, see NuoDB Check.