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

Figure 10 Synchronized Databases After STOP TMF Command
Figure 11 shows unsynchronized databases. In this figure, T5 and T6 (transactions 5 and 6) have
not been transmitted to the backup system because of a physical disaster, such as fire or flood, or
because the primary or backup systems have failed. The databases are unsynchronized because
transactions were committed or aborted on the primary system before an unexpected shutdown,
and the extractor cannot transmit the commit or abort status records for those transactions (T5 and
T6) to the backup system.
NOTE: If you have not lost your primary system to a disaster, then, when the failed system comes
back online and RDF is restarted, RDF will put the backup database into synchronization with the
primary when it has caught up.
Figure 11 Unsynchronized Databases
Making Changes to Database Structures
When you change the structure of a database on the primary system, you also need to change
the structure on the backup system.
150 Maintaining the Databases