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-7
Creating a NonStop SQL/MX Backup Database
From an Existing Primary Database
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.
For example, assume you have the objects on your primary system that have the
following fully qualified Guardian names:
\pnode.$DATA01.ZSDABCDEF.FILE100
\pnode.$DATA02.ZSDABCDEF.FILE100
\pnode.$DATA03.ZSDABCDEF.FILE100
For the RESTORE command, you must name the qualified Guardian filenames of
your source objects and also the qualified Guardian filenames of your target
objects in the LOCATION clause.
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
)
Note that the volume names can differ between the primary and backup systems.
Also, the subvolume and filenames on the backup system must be identical to
those on the primary system, and the the subvolume must correspond to the
subvolume you used when you created your schema.
The backup database is now ready for RDF replication activity.