RDF System Management Manual

NonStop SQL/MX and RDF
HP NonStop RDF System Management Manual—524388-003
15-11
Creating the Fuzzy Copy on the Backup System
Creating the Fuzzy Copy on the Backup System
The advantage of this method is that it eliminates the use of temporary objects as well
as tape handling because you create your backup objects directly on the backup
system. The disadvantage is that it requires you to load the data from your primary
objects to your backup objects over Expand lines, which might take longer than the
alternate method given above if the data is great in size.
To create the fuzzy copy on the backup system, perform the following steps.
1. Create the backup catalog on your backup system. This operation is identical to
that outlined in Step 1 of Creating a NonStop SQL/MX Backup Database From an
Existing Primary Database, above.
2. Create the schema on the backup system. This operation is identical to that
outlined in Step 2 of Creating a NonStop SQL/MX Backup Database From an
Existing Primary Database, above.
3. So each catalog to be seen from both systems, you must register your primary and
backup catalogs as described in Step 3 of Creating NonStop SQL/MX Primary and
Backup Databases from Scratch, above.
4. Obtain the fully qualified Guardian filenames for all objects on the primary system
that you want replicated.
5. Create each object on the backup system. See Step 7 of Creating NonStop
SQL/MX Primary and Backup Databases from Scratch, above.
6. Determine where you will run the command to load the data from the primary
objects to the backup objects. If you run the command on the primary system,
NonStop SQL/MX selects the data locally and inserts over the network into the
backup object. Alternatively, you can run the operation on the backup system,
which selects the data remotely and inserts the data locally.
7. Populate the backup objects by running an INSERT statement on whichever
system you prefer.
INSERT INTO backup-table SELECT * FROM primary-table;
where backup-table and primary-table are the 3-part ANSI names of the
two tables.
The backup database is now ready for RDF replication.