mrecover

Use the mrecover command to recover the state of a cell after a catastrophic loss of data. Typically, a catastrophic data loss is caused by a system failure. You can use the mrecover command locally on the computer hosting the cell from which the data was lost.

The process recovers the data from other cells that received events from the local cell and that sent events to the local cell. The command cannot recover unpropagated events sent directly from adapters.

Notes

The mrecover command recovers only propagated events.

The mrecover command contacts each of the cells that you list in the TargetCell option and requests that each target cell produce an up-to-date saved state. The events that were propagated from the local cell are extracted from each target cell and stored locally. After all of the target cells have been prompted and the propagated events are retrieved, they are merged into a new saved state for the local cell. Then, the saved state is processed by the local cell during a recovery process.

If the local cell is running or contains an mrecover file, the recovery process aborts. If the recovery process cannot connect to a target cell, you are prompted to choose to stop or continue the recovery process. If you choose to continue, you are prompted to choose to include events collected from the previous session. After the recovery process completes, the saved state is used to restart the recovered cell.

Note

If the data loss includes the BMC Impact Solutions product executables or the Knowledge Base definition of the cell, you must reinstall the cell software, the Knowledge Base, and a dedicated recovery Knowledge Base (if applicable) before using the mrecover command.

Ensure the following before you run the mrecover command:

  1. Navigate to the <MCELL_HOME>\etc\<brokencell> directory, and open the mcell.conf file.
  2. Find the following code line, and uncomment it.
    #KBRecoveryDirName=kbrecovery
  3. Ensure that the kbrecovery directory is present in the <MCELL_HOME>\etc\<brokencell> directory. If it is not present, create a directory with this name. If you want to use a different directory instead of kbrecovery, then set the KBRecoveryDirName parameter accordingly. For example, if you want to use kb instead of kbrecovery, ensure that the kb directoy is present in the <MCELL_HOME>\etc\<brokencell> directory, and set the parameter as KBRecoveryDirName=kb

mrecover syntax

The following figure shows the syntax for mrecover.

mrecover syntax

mrecover [-c <ConfigFile>] [-q] [-h|-?] [-l <HomeLocation>]
[-n <cellName> | -n @Host[/Port[#Key]]]{-p <"Var=Value">} [-z]
{<TargetCell>} . . .

The following table lists the command-specific option for mrecover. For a list of common command options that apply to all CLI commands, see Event management common command options.

mrecover option

Option

Description

TargetCell

Specifies the name of the cell that propagated events or to which events have been propagated

mrecover example

To fix a broken cell with input from cellacellb, and cellc, type the command shown in the following figure.

Fixing a broken cell by using mrecover

mrecover -n broken_cell cella cellb cellc

mrecover return codes

The following figure lists the command-specific return codes for mrecover. For a list of common return codes that apply to all CLI commands, see Event management return codes.

mrecover return codes

Code

Description

2

Failed to send the command that started the StateBuilder on a remote cell

3

Could not obtain information from one or more neighbor cells

5

Could not launch an external program (mrmerge or mcell)

6

mrmerge exited abnormally

7

mcell (in recovery mode) exited abnormally

Was this page helpful? Yes No Submitting... Thank you

Comments