Synchronizing Entire Databases Online - HP NonStop RDF J-series RVUs Management Manual

NOTE: RDF does not replicate NonStop SQL/MP and NonStop SQL/MX catalogs. Therefore,
if you are synchronizing NonStop SQL/MP and NonStop SQL/MX tables, you might need to
create NonStop SQL/MP and NonStop SQL/MX catalogs manually on the backup system if they
do not already exist.

Synchronizing Entire Databases Online

To synchronize an entire RDF backup database to the primary database online:
1. If RDF is currently running, issue a STOP RDF command on the primary system.
2. Purge the RDF control subvolume on both the primary and backup systems and then issue
an INITIALIZE RDF command of the following form on the primary system:
INITIALIZE RDF, BACKUPSYSTEM \system, SYNCHDBTIME ddmmmyyyy hh:mm
where system is the name of the backup system, ddmmmyyyy is today's date (such as
17DEC2004), and hh:mm is an appropriate timestamp prior to the current time (see the
description of the INITIALIZE RDF command in
NOTE:
attribute in the above INITIALIZE RDF command to keep this RDF configuration separate
from the other RDF configurations on the primary system. Also, if this configuration is to
protect different data from the other RDF configurations, you might want to consider using
the INCLUDE and EXCLUDE options for your updaters.
3. Configure RDF and then issue a START RDF, UPDATE OFF command on the primary
system.
4. Make a copy of all tables and files in the database:
• Method 1
— Create an empty set of duplicate key-sequenced and relative files and tables that
— Using load commands, populate the empty tables and files.
• Method 2
— Take online dumps of your entry-sequenced, key-sequenced, and relative files and
— Using these online dumps, perform File Recovery to a New Location to different
— Move the copy of the database to the backup system.
5. When you have completed getting a copy of the database, issue the RDFCOM STOP SYNCH
command on the primary system. This command issues a message to the extractor. The
168 Online Database Synchronization
If you have multiple RDF environments, be sure to specify an appropriate SUFFIX
do not have SYSKEYs and clustering keys on either the primary or backup system.
The duplicate tables and files must not be audited.
You can create these files and tables on either the primary or backup system, but
you should only create them on the backup system if you have sufficient Expand
bandwidth between the two systems to handle both the audit sent by the extractor
and the data sent by the load operations.
For NonStop SQL/MP tables, use SQLCI LOAD commands with the SHARE option.
For Enscribe files, use FUP LOAD commands with the SHARE option.
tables. Note, this is the only method you can use for entry-sequenced files and
tables, as well as any tables that have SYSKEYs and clustering keys.
locations on the primary system.
Chapter 8 (page 187)).