Recovering a Mirrored Devspace 

Use

If the devspaces of you database instance are mirrored, one of the devspace mirrors may fail. In this case, the database continues to operate but only the part of the devspace pair that is intact can be accessed. The faulty mirror devspace is displayed as a Bad Devspace.

You use this function to recover a damaged mirror devspace. This can be a data devspace, a system devspace or a log devspace.

To ensure the availability of your system, however, it is advisable to mirror log devspaces only. We recommend RAID 5 configurations to protect your data and system devspaces.

Recovering a damaged log devspace mirror

When you trigger the recovery of a log devspace, it is only reinitialized. In other words, the data is not copied from the intact devspace. Following this, both log devspaces are written to sequentially. The devspace originally marked BAD must be written to fully before the contents of both devspaces are identical again and both devspaces can be read.

The defective devspace remains marked BAD during the entire reintegration phase.

Prerequisites

The database instance is ONLINE or ADMIN mode.

Procedure

  1. Choose Instance ® Recovery ® Devspaces.
  2. Select the BAD devspaces that are to be recovered.
  3. Choose RecoverDevspaces ® Reintegrate to start initializing the mirror devspace.

Recovering a damaged data devspace mirror

When a damaged data devspace is recovered, the intact data devspace is copied to the repaired data devspace. Following this, both data devspaces operate normally again in mirrored mode.

Prerequisites

The database instance is in ONLINE mode.

Procedure

  1. Choose Instance ® Recovery ® Devspaces.
  2. Select the BAD devspaces that are to be recovered.
  3. Choose RecoverDevspaces ® Reintegrate to start copying the data to the mirror devspace.