Resynchronizing Entire Databases Offline; Resynchronizing Individual Volumes, Tables, And Files Offline - HP NonStop RDF J-series RVUs Management Manual

The remainder of this chapter describes how to do offline resynchronization. For information
about online resynchronization, see
To resynchronize the primary and backup databases, you need to make all backup database files
or tables logically identical to the primary database files or tables when there is no audit data to
be processed for the files or tables. If you know which files or tables are not synchronized,
resynchronize the databases only on the volumes that contain those files or tables.
There is no audit data to be processed for a volume at the following times:
• Immediately after TMF has been started for the very first time and no applications have
been started yet
• When the RTD time is zero for the volume's updater process, and no audit data is being
generated by any application while the files or tables are being duplicated
• When TMF is stopped (without the ABRUPT option)
Make sure the primary and backup databases are synchronized if any of the following should
occur:
• A TMF file recovery operation to a timestamp or to first purge occurs, after which only the
affected database tables or files need to be resynchronized.
• Asterisks (****) appear in the final column of the STATUS RDF display, indicating that an
updater process has experienced an unexpected file-system error.
NOTE:
an RDF process. For example, an updater process reporting an error 122 will restart.
• TMF is deleted and reconfigured, or RDF is reinitialized, after a STOP RDF command is
issued at the primary system.
If RDF fails and reports an event whose recovery text indicates that database resynchronization
is required, you must resynchronize the backup and primary databases.

Resynchronizing Entire Databases Offline

To resynchronize an entire database offline, you must stop TMF, initialize RDF to the TMF
shutdown timestamp, and then copy the complete database from the primary system to the
backup system.
Alternatively, in an environment where there are multiple databases and applications, but RDF
is protecting only one of those databases, stopping TMF might not be desirable. In this case, you
can stop the applications associated with the RDF-protected database, copy the database from
the primary system to the backup system (there are several ways of doing this), reinitialize RDF
using the INITTIME option, and start RDF.
If you are unsure about which tables or files might not be synchronized, you need to compare
the questionable tables or files between the primary and backup databases and then, based on
that evaluation, resynchronize some of the database objects.
To purge a NonStop SQL/MP or NonStop SQL/MX database, use the SQLCI/MXCI PURGE utility
and DROP command, as explained in the SQL/MP Installation and Management Guide and the
SQL/MX Installation and Management Guide.
To recopy a database to the backup system, follow the instructions in
and Backup Databases" (page

Resynchronizing Individual Volumes, Tables, and Files Offline

If you are sure that only certain database files or tables on a particular volume might not be
synchronized, all you need to do is synchronize the entire volume or just the individual files
and/or tables.
Resynchronization is not always necessary, however, after a file-system error in
71).
Chapter 7 (page 167).
"Synchronizing the Primary
Resynchronizing Databases 165