RDF/IMP, IMPX, and ZLT System Management Manual

NonStop SQL/MX and RDF
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
15-6
Creating a NonStop SQL/MX Backup Database
From an Existing Primary Database
For example, if issued on the backup system, the command
CREATE CATALOG BCAT LOCATION $DATA01;
creates a catalog named BCAT on volume $DATA01 on the backup system.
For the rest of this procedure assume that the name of the primary system is
\PNODE and the name of the backup system is \BNODE.
2. Create the schema on the backup system using the same schema name and the
same subvolume name as on the primary system.
For example, if issued on the backup system, the following command creates a
schema on the backup system called SCH in catalog BCAT using subvolume
ZSDXYZ3A:
CREATE SCHEMA BCAT.SCH LOCATION ZSDXYZ3A;
You must use the LOCATION clause. If you specified the LOCATION clause when
creating the primary system's schema, you must use the same subvolume here. If
you did not specify the LOCATION clause when creating the primary system's
schema or if you do not know the name of the subvolume used for the schema on
the primary system, then you must query the primary system to obtain the
Guardian subvolume name, and you must use the Guardian subvolume name with
the LOCATION clause here (see the discussion and example at the end of Step 4
in the procedure Creating NonStop SQL/MX Primary and Backup Databases from
Scratch, above).
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