RDF System Management Manual for J-series and H-series RVUs (RDF 1.10)

Indirectly From the Primary to the Backup By Way of a Temporary File
If the number of rows to load over the network is too great, you can use a temporary file on the
primary system:
1. Create a temporary catalog on your primary system to correspond to your regular catalog on
your primary system whose objects you want RDF to replicate.
2. Create a temporary schema for your temporary catalog. Follow the instructions given above
in “Creating a NonStop SQL/MX Backup Database From an Existing Primary Database”. The
name of the temporary schema need not be identical to the name of the schema whose objects
you want replicated, nor must the subvolume name be identical.
3. Create a temporary table in your temporary schema, including all partitions. The partition
ranges must be identical to those of your primary table. Follow the guidelines outlined in
“Creating a NonStop SQL/MX Backup Database From an Existing Primary Database”, above,
except that you must create the temporary table on the primary system and on different volumes
from those used for your primary objects.
4. Now load only the rows from the primary partition that you want synchronized into the
temporary partition:
INSERT INTO backup-table SELECT * FROM primary-table
WHERE key-column >= 'F' AND key-column < 'K';
5. Use Backup to put the temporary table on tape.
6. Create a catalog on the backup system to correspond to the temporary catalog on the primary
system.
7. Create the schema on the backup system using the same schema name and the same subvolume
name as the schema for the temporary database.
8. Use RESTORE to place the temporary objects on the backup system, specifying the temporary
catalog on the backup system as the target. See “Creating a NonStop SQL/MX Backup
Database From an Existing Primary Database” (page 310) for details.
9. For the backup partition you want synchronized, delete all rows in that partition:
DELETE FROM name
WHERE key-column >= 'F' and key-column < 'K';
10. Now load only the rows from the temporary partition that you want synchronized into your
backup table's partition:
INSERT INTO backup-table SELECT * FROM temporary-table
WHERE key-column >= 'F' AND key-column < 'K';
Backup Partition Does Not Already Exist
If a partition does not already exist on the backup system, you must create a partition on the backup
system. See “Creating a NonStop SQL/MX Backup Database From an Existing Primary Database”
(page 310) for instructions. Then you must insert the rows into the backup partition using either of
the two methods described above. In this case you do not need to delete the rows from the backup
partition because it is already empty.
Online Synchronization for a Single Partition
You must first determine the key ranges for each of your partitions.
Perform the steps described in “Online Database Synchronization With NonStop SQL/MX Objects”
(page 312). In this case, you are only dealing with a single partition. If you create a temporary
table on your primary system, you only need to populate the one partition with the INSERT statement
shown in “Offline Synchronization for a Single Partition” (page 314).
If you synchronize the backup partition directly from the primary system, first delete all rows from
the backup partition, as described in “Offline Synchronization for a Single Partition” (page 314),
Online Synchronization for a Single Partition 315