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

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 Online” (page 159)). When using this method, there are no special
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.
FRNL (Step 4, Method 2)
This method can be used for tables with or without SYSKEY or clustering keys.
There are no special considerations for key-sequenced tables with indexes, but see below for issues
regarding the synchronization of indexes.
NonStop SQL/MP and NonStop SQL/MX Tables With Partitions
The utilities associated with and related to the NonStop SQL products have limitations that make
synchronization of individual partitions complicated and difficult. The following represent methods
that enable you to circumvent these limitations.
• SQLCI DUP and MXCI DUP does not have a PARTONLY option. Therefore, you cannot duplicate
only an individual partition.
• While BACKUP and RESTORE have the PARTONLY option, if you have backed up tables from
the primary system, you must use the MAP NAMES option (LOCATION option with BACKUP
and RESTORE 2) when restoring them on the backup system in order to specify the correct
system name. You cannot, however, include both the MAP NAMES (LOCATION option with
BACKUP and RESTORE 2) and PARTONLY options in the RESTORE operation. Therefore,
because you must use MAP NAMES or LOCATION, you cannot restore only a single partition.
Synchronizing Selected Database Portions Online 169