RDF System Management Manual

NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-6
Creating a NonStop SQL/MX Backup Database
From an Existing Primary Database
the updater will wait until you have created such a file. At this point, you will have
to correct the naming problem as described under Correcting Incorrect NonStop
SQL/MX Name Mapping.
When you have completed Steps 6 and 7 for each table and index, the primary
database is ready for transaction activity, and the backup database is ready for
RDF to replicate that transaction activity.
Creating a NonStop SQL/MX Backup Database
From an Existing Primary Database
To create an RDF backup NonStop SQL/MX database from an existing primary
database, perform the following steps:
1. Create a catalog on your backup system to correspond to the primary system
catalog whose objects you want RDF to replicate. Note that the name of the
backup catalog must differ from the name of the primary catalog. The volume in
the optional LOCATION clause may differ from the volume used on the primary
system.
CREATE CATALOG <catalog_name> LOCATION <optional_guardian_location>;
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).