RDF System Management Manual

NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-7
Creating a NonStop SQL/MX Backup Database
From an Existing Primary Database
3. If you want each catalog to be seen from both systems, register your primary and
backup catalogs. See Step 3 in Creating NonStop SQL/MX Primary and Backup
Databases from Scratch, above, for instructions and examples.
4. Use the MXGNAMES utility to generate the LOCATION clauses for the RESTORE
utility. To generate a location clause for a single table on the primary node called
CAT.SCH.TAB1, use the following command:
MXGNAMES CAT.SCH.TAB1 -BR2 -node=\bnode -output=TAB1MAP
Refer to the HP NonStop SQL/MX Installation & Management Guide for further
information about the MXGNAMES utility. This command generates the necessary
location clause to restore this table on the backup node, without changing the
volume names, and saves the output to a Guardian EDIT file called TAB1MAP. If
necessary, you can remap the volume names manually by editing this file.
LOCATION
(
\PNODE.$DATA01.ZSDABCDEF.FILE100 TO \BNODE.$DATA0A.ZSDABCDEF.FILE100,
\PNODE.$DATA02.ZSDABCDEF.FILE100 TO \BNODE.$DATA0B.ZSDABCDEF.FILE100,
\PNODE.$DATA03.ZSDABCDEF.FILE100 TO \BNODE.$DATA0C.ZSDABCDEF.FILE100
)
You can generate one such location file for each table, or a single file in one
MXGNAMES command by providing an input list of NonStop SQL/MX names. The
input list must be a Guardian EDIT file consisting of one fully-qualified ANSI SQL
table name per line, such as:
CAT.SCH.T1
CAT.SCH.T123
CAT.SCH.ABC
Assuming this EDIT file is called BR2INPUT, you can use the following command
to generate a single output file call LOCMAP2, containing the necessary
LOCATION clause to back up all three tables, as follows:
MXGNAMES -sqlnames=BR2INPUT -BR2 -node=\bnode -output=LOCMAP2
Refer to the HP NonStop SQL/MX Installation & Management Guide for
information about how to generate input table name lists from your database and
more complete information on the MXGNAMES utility.
5. Use the BACKUP utility to store your primary database objects on tape, using their
ANSI names. The application must be stopped, and the database inactive, while
the backup is being performed.
6. At the backup system, use the RESTORE utility to place the objects on the backup
system, specifying the ANSI names for the backup system. Use the LOCATION
clauses generated in Step 4 to have RESTORE place the objects in the correct
Guardian locations. See Restoring to a Specific Location
later in this section for
general restore syntax for NonStop SQL/MX databases.