SQL/MP Installation and Management Guide

Moving a Database
HP NonStop SQL/MP Installation and Management Guide—523353-004
9-6
DUP and BACKUP/RESTORE
Guidelines for Name Mapping in BACKUP and RESTORE
To move interrelated SQL objects from one volume or node to another, you can use the
MAP NAMES option. Use of this option requires familiarity with the way in which the
BACKUP and RESTORE utilities handle file names. Be sure to specify a target file set
list or define the MAP NAMES and CATALOG options correctly for the dependencies of
the target object, or the moved objects might be left in an invalid state or might not be
moved.
File set Considerations
All files in the specified file set must originate from the same node; you cannot specify
two nodes in the BACKUP command.
Although the files in a file set all reside on one node, they might have implicit
relationships with files on other nodes. For example, a file might be partitioned across
several nodes, or a base table might reside on one node and have indexes on another.
Unless you specify otherwise, the BACKUP utility backs up these related files along
with the files specified explicitly in the file set.
The BACKUP utility saves the names of the backed-up files in local or network format,
depending on the location of the file set relative to the BACKUP process:
•
The files are considered “local” if the file set is on the node running the BACKUP
utility. Local file names are saved without a node identifier.
•
The files are considered “remote” if they reside on a node other than that running
the BACKUP utility. That is, if the BACKUP utility is running on node \A and is
backing up a file set from remote node \B, the file set defined on remote node \B
would be considered “remote” by BACKUP. The BACKUP utility stores the names
of files from remote nodes in remote internal format
(\<node-number>.<volume>.<subvolume>.<file-identifier>) to prevent accidental
overwriting of files that have the same file names.
This example backs up a remote table and a local index. Suppose that TABLE1
resides on remote node \B and has index TINDX on local node \A. This BACKUP
command (issued from node \A) backs up TINDX along with TABLE1:
BACKUP $TAPE, \B.$VOL.SUBVOL.TABLE1
The files are backed up as:
\B.$VOL.SUBVOL.TABLE1 $VOL.SUBVOL.TINDX
Note. The PARTONLY and MAP NAMES options are mutually exclusive. So, if you use the
PARTONLY option during BACKUP and RESTORE, you will not be able to use the
MAP NAMES option.
Caution. When backing up files, be aware that you cannot currently restore files in a remote
file set if their associated node number is not available on the destination network.