Initializing RDF To a TMF Shutdown Timestamp
If TMF was running previously on the primary system and did not need to be initialized and
configured, you can initialize RDF to a timestamp that reflects the time of the last TMF shutdown.
This initialization is typically used when one stops TMF in order to initialize RDF to that TMF
stop location. This might be useful if you are about to use RDF for the first time and you stop
TMF in order to synchronize your backup database to your primary database. After you have
synchronized the databases and initialized RDF, you can start TMF, start RDF, and start your
applications with an assurance that no audit will be skipped when RDF commences replication
operations.
To issue the INITIALIZE RDF command without first initiating an RDFCOM session, enter the
command in the following format in response to the TACL prompt. In the TIMESTAMP parameter,
be certain to specify the exact time (to the minute) that TMF was last shut down. You determine
the appropriate timestamp by examining previous TMF messages in the EMS log. In this example,
the TIMESTAMP parameter specifies 1:32 p.m., January 7, 1999:
>RDFCOM;INITIALIZE RDF, BACKUPSYSTEM \CHICAGO,
SUFFIX A, TIMESTAMP 7JAN1999 13:32
To issue the INITIALIZE RDF command from within an RDFCOM session, enter the following
in response to the RDFCOM prompt:
]INITIALIZE RDF, BACKUPSYSTEM \CHICAGO, SUFFIX A,
TIMESTAMP 7JAN1999 13:32
If the INITIALIZE RDF commands in this discussion were issued from the primary system
\DALLAS, RDF would respond by creating a configuration file in the control subvolume named
$SYSTEM.DALLASA.CONFIG.
Initializing RDF Without any Timestamp Option
If you have just installed (or deleted and reinstalled) TMF so that it starts at relative byte address
(rba) 0 in audit trail file sequence number 1, you should now issue an INITIALIZE RDF command
without the TIMESTAMP parameter at the TACL prompt on the primary system:
>RDFCOM; INITIALIZE RDF, BACKUPSYSTEM \BOSTON, SUFFIX A
When you begin an RDFCOM session on a system in which RDF has never been previously
initialized (such as \PRIMSYS, for example), RDFCOM responds with the following prompt:
***Warning*** The control subvolume PRIMSYS is not presently
***Warning*** configured for an RDF primary system.
You must use the OPEN command to open an RDF CONFIG file in an
existing RDF control subvolume, or you must initialize a new RDF
configuration with the INITIALIZE RDF command.
To continue with the session, you must either enter an INITIALIZE RDF command, or use the
OPEN command as directed in
Chapter 8 (page 187)
.
Initializing RDF Without Stopping TMF (Using INITTIME Option)
The INITIALIZE RDF command includes a parameter, INITTIME
inittime
, that you can use
to initialize the RDF product without stopping TMF or your applications.
There are two cases where you would typically use this capability:
•
If you want to install a new version of the RDF product and you cannot afford to stop TMF
even momentarily to get a TMF shutdown timestamp.
•
If you are running RDF and encounter a problem for which you would like to reinitialize
RDF without having to resynchronize your databases.
80
Installing and Configuring RDF
Содержание NonStop RDF
Страница 68: ...68 ...
Страница 186: ...186 ...
Страница 260: ...260 ...
Страница 278: ...278 ...
Страница 284: ...284 ...
Страница 290: ...290 ...
Страница 308: ...308 ...
Страница 322: ...322 ...
Страница 336: ...336 ...
Страница 348: ...348 ...
Страница 464: ...464 ...
Страница 478: ......