RDF/IMP and IMPX System Management Manual (RDF 1.4+)

Entering RDFCOM Commands
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
8-98
Command Overview
TAKEOVER
The TAKEOVER command causes the backup database to become transactionally
consistent and available as the database of record.
Where Issued
Backup system only.
Security Restrictions
You can issue the TAKEOVER command only if you are the member of the super-user
group that initialized RDF.
RDF State Requirement
You can issue the TAKEOVER command only if the communication lines between the
backup and primary systems are down, or the monitor process is not running on the
primary system.
Usage Guidelines
The TAKEOVER command is customarily issued when the primary system fails or
otherwise becomes unavailable, and makes the backup database the primary
database.
When you issue a TAKEOVER command, RDF determines whether the monitor
process is running on the primary system:
•
If the communications lines are operational and the monitor and extractor
processes are still running, the TAKEOVER command fails.
•
If the communications lines are down, RDF proceeds as if the monitor process is
not running and executes the TAKEOVER command.
TAKEOVER
Caution. The TAKEOVER command is not a normal operational command. Operators
should never issue this command strictly on their own initiative. Issue this command
only when specifically told to do so by someone in high authority.
It is important to ensure that the RDFCOM session uses the appropriate RDF control
subvolume which is associated with the primary system for this TAKEOVER operation. To do
this, specify the RDF control subvolume through the OPEN command or on the RDFCOM
command line.
Before initiating a takeover, restore all image files to their original location in the image trail (if
you moved them). If you do not restore the image files the takeover may fail or appear to
complete successfully but leave the backup database in an inconsistent state.