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

3. To proceed with the takeover operation, enter Y or YES.
To abort the takeover operation, enter N or NO.
After you enter your response, RDFCOM returns its prompt. Once the Takeover operation is
underway, you can use the STATUS RDF command to determine the progress of the takeover
operation. If the takeover operation is still in progress, RDF displays the current state as
“TAKEOVER IN PROGRESS.”
When the takeover operation finishes, RDF displays a message such as the following in
response to the STATUS RDF command:
STATUS RDF (\RDF04 -> \RDF06) is NOT running
An RDF TAKEOVER has completed
Safe MAT position is SNO 1, RBA 87876660
MAT position for File Recovery: SNO 1, RBA 87876740
By using the TAKEOVER ! version of the TAKEOVER command you eliminate the Expand level-four
timer and the prompt.
For super fast takeover, see “How to Plan for the Fastest Movement of Business Operations to Your
Backup System After Takeover” (page 135).
Issuing the TAKEOVER Command in an Obey File
You have the following three options to issue the TAKEOVER command through an OBEY file.
1. As stated in the section entitled “Using RDFCOM Non-interactively (without an IN File)”
(page 94), you can issue RDFCOM commands in a TACL obey file or a script file. You issue
the command as follows:
RDFCOM <control-subvol-name>; Takeover !
Please note that you run this command on the backup system and that the
<control-subvol-name> is the name that identifies the specific RDF subsystem for which
you want to execute the Takeover command. It is suggested that you use the ! option for
simplicity. Otherwise you must configure your script file to handle the prompts that RDFCOM
asks when executing the Takeover command.
2. The second option is to write the TAKEOVER command appended with the bang (!) character
in an EDIT file and OBEY the file from the RDFCOM prompt.
For example, consider an EDIT file RDFTKOV that has the following content:
TAKEOVER!
Now, you can obey the file RDFTKOV from the RDFCOM prompt, as shown below:
RDFCOM] obey RDFTKOV
3. The third option is to write the TAKEOVER command appended with the bang (!) character
in an EDIT file and pass it as an IN file to RDFCOM.
For example, consider an EDIT file RDFTKOV has the following content:
TAKEOVER!
Now, you can use the EDIT file RDFTKOV as an INFILE to RDFCOM, using the following
command:
RDFCOM /IN RDFTKOV/
NOTE: RDFCOM does not allow the TAKEOVER command without the bang (!) character
when issued in an IN file / OBEY file.
Monitoring Takeover Outcome
You can monitor the status of RDF takeovers by issuing a STATUS RDF command on the backup
system or by examining the events in the EMS log.
Takeover Operations 133