Key-Sequenced Files With Frnl (Step 4, Method 2); Relative Files With Create/Load (Step 4, Method 1); Relative Files With Frnl (Step 4, Method 2); Entry-Sequenced Files - HP NonStop RDF J-series RVUs Management Manual

To load the primary partition only, issue the following command:
FUP LOAD $DATA1.TEST.PART0100, $DATA1.TEMP.PART0100,
PARTONLY,SHARE
To load the secondary partition only, issue the following command:
FUP LOAD $DATA2.TEST.PART0100, $DATA2.TEMP.PART0100,
PARTONLY,SHARE
When the load operations are finished, use BACKUP and RESTORE (or FUP DUP) with the
PARTONLY option to copy the partition you need to the backup system.

Key-Sequenced Files with FRNL (Step 4, Method 2)

With this method, you only need to use FRNL to obtain a copy of the specific partition and then
move the copy to the backup system.

Relative Files with Create/Load (Step 4, Method 1)

First create a non-audited duplicate file on the primary system. You must create the entire file
with all its partitions. Unlike key-sequenced files, you must load the entire file. For example,
assume the file has two partitions: $DATA1.TEST. PART0100 (primary) and
$DATA2.TEST.PART0100 (secondary). Issue the following command:
FUP CREATE $DATA1.TEMP.PART0100,
LIKE $DATA1.TEST.PART0100, NO AUDIT
That command creates the two files $DATA1.TEMP.PART0100 (primary partition) and
$DATA2.TEMP.PART0100 (secondary partition)
You must load all the partitions of a relative file. Therefore, only one command is possible.
FUP LOAD $DATA1.TEST.PART0100, $DATA1.TEMP.PART0100,
SHARE
You can then use BACKUP and RESTORE (or FUP DUP) with the PARTONLY option to copy
the loaded partition you need to the backup system.

Relative Files with FRNL (Step 4, Method 2)

With this method, you only need to use FRNL to obtain a copy of the specific partition you want
and then move the copy to the backup system.

Entry-Sequenced Files

If you use Step 4, Method 2, there are no special considerations for entry-sequenced files. You
cannot use Step 4, Method 1.

NonStop SQL/MP and NonStop SQL/MX Tables Without Partitions

Tables with SYSKEY or Clustering Keys

For online database synchronization, you must use FRNL method (See Step 4, Method 2 under
"Synchronizing Entire Databases
considerations.

Tables without SYSKEY and Clustering Keys

Create/Load (Step 4, Method 1)
First create a non-audited duplicate table on the primary system and then load it. Use BACKUP
and RESTORE (or SQLCI DUP) to move the duplicate table to the backup system.
Alternatively, you can use the create and load method to put the duplicate tables directly onto
the backup system, provided you have enough Expand capacity to handle both the data being
loaded and the audit being shipped to the backup system by the extractor.
178 Online Database Synchronization
Online"). When using this method, there are no special