SQL/MP Installation and Management Guide

Moving a Database
HP NonStop SQL/MP Installation and Management Guide—523353-004
9-8
DUP and BACKUP/RESTORE
Restoring Files to a Different Network
When restoring files on a node that is not connected to the network where the original
BACKUP process was run, RESTORE attempts:
•
If all files on the BACKUP tape are in local format, the files are restored to the local
node.
•
If any files on the BACKUP tape are in remote format, RESTORE attempts to
restore the files to the node assigned to the node number stored with the file name.
In this situation, follow these steps before requesting the restore operation:
1. Run the RESTORE utility with the LISTONLY option:
RESTORE $Tape, ( *.*.* ), LISTONLY
The output describes how the node numbers of the backed-up files match the node
names on the destination network. If the source node number exists in the
destination network, the output from the LISTONLY option displays the matching
node name in the destination network, as follows:
$VOL.SUBVOL
TINDX
\B.$VOL.SUBVOL
TABLE1
2. Run the RESTORE utility again, specifying the appropriate file set in the
RESTORE command. Use the MAP NAMES option to specify destination node
names. For example, this command restores the files in the previous example:
RESTORE $TAPE, ( \B.$VOL.SUBVOL.TABLE1),
MAP NAMES ( \B.$VOL.SUBVOL.* TO $NEW.SV2.* )
If the node number does not exist on the destination network, the node name is
replaced by “\??” in the LISTONLY output, as follows:
$VOL.SUBVOL
TINDX
\??.$VOL.SUBVOL
TABLE1
For additional examples of the MAP NAMES option in the RESTORE utility, see the
Guardian Disk and Tape Utilities Reference Manual.
Caution. You cannot currently restore files of a remote file set if their associated node number
is not available on the destination network.