HP NonStop RDF J-series RVUs Management Manual page 138

For j-series and h-series rvus
Table of Contents

Advertisement

With reciprocal configurations it is imperative that you make sure the file-sets being replicated
by the two RDF subsystems are absolutely independent of each other, and this can only be done
in one of two ways:
1.
The volumes protected by RDF Subsystem #1 are completely different from the volumes
protected by RDF Subsystem #2. For example, RDF Subsystem #1 protects volumes
$DATA1-$DATA10, and RDF Subsystem #2 protects volumes $DATA20-$DATA30.
2.
You use INCLUDE/EXCLUDE lists to ensure complete separation. For example, RDF
Subsystem #1 INCLUDES SUBVOLA.* on volumes $DATA1-10, and RDF Subsystem #2
INCLUDES SUBVOLB.* on volumes $DATA1-10.
Please note that in each of these configurations, there is no possible overlap of data being replicated
by the two RDF subsystems in a reciprocal configuration. See Reciprocal and Chain Replication
in
Chapter 1
two methods described above.
The steps for performing a planned switchover from \A to \B in such a configuration are:
1.
On system \B, stop RDF subsystem # 2. Note the local system time; you will need it later.
2.
On system \A, stop the business applications that access the primary database (Applications
#1).
3.
On system \A, stop TMF(or if you do not want to stop TMF, use the STOP RDF, DRAIN
command).
4.
Wait for RDF subsystem #1 on \A to shut down.
5.
On system \B, restart Applications #1.
At this point, the RDF subsystem is down on both systems, the business applications from
system \A are now running on system \B, the business applications that were running on
system \B are still running on system \B, and all audit records are being queued in TMF
audit trails on system \B.
6.
When system \A is ready to resume its normal operations, restart TMF.
7.
On system \B, restart RDF subsystem #2 (the RDF subsystem that replicates data from \B
to \A for the business applications that normally run on \B). The subsystem resumes its
processing exactly where it was when you stopped it in step 1.
8.
On system \B, initialize RDF subsystem #1. In the INITIALIZE RDF command, include the
INITTIME option and specify the timestamp you noted in step 1. Configure the subsystem
to replicate data from \B to \A for Applications #1 (the business applications that were
moved from system \A to system \B).
138
Critical Operations, Special Situations, and Error Conditions
for a discussion of the potential problem that can occur if you do not use one of the

Hide quick links:

Advertisement

Table of Contents
loading

This manual is also suitable for:

Nonstop rdf h-series rvusNonstop rdf

Table of Contents