Show TOC

Minimizing the Risk of Breakdowns Locate this document in the navigation structure

 

The business risk if SAP NetWeaver Enterprise Search becomes unavailable without a backup is that users can no longer access the search functions of SAP NetWeaver Enterprise Search.

In the event of a breakdown without a backup, no critical data is lost because the original data of the business objects and documents is located in the search providers and SAP NetWeaver Enterprise Search is used only for indexing. Consequently, only the indexes and SAP NetWeaver Enterprise Search configuration data, such as search object connectors, are lost.

SAP NetWeaver Enterprise Search provides the following means to minimize the risks of a breakdown:

Redundant Hardware Components

To prevent breakdowns, central hardware components exist more than once.

Example Example

Depending on the hardware provider, these include the Network Interface Controller (Bonding) and the redundant array of independent disks (RAID).

End of the example.
Redundant Software Components

In an SAP NetWeaver Enterprise Search system with six or more blades, the following instances are redundant, that is, they are available in at least duplicate:

  • Dialog dual stack instances (AS ABAP is active)

  • Additional TREX instances

In the event of a breakdown of one of these instances, the SAP Web Dispatcher can distribute tasks in the same way to the remaining instances. Consequently, there is no downtime but simply a reduction in performance.

You can use the appliancecontrol tool to quickly and easily restore instances that have stopped working, assuming the cause is not a hardware problem.

More information: appliancecontrol Tool

Data Backup and Restore

In order to retain the TREX indexes and the AS ABAP configuration data in the event of a complete breakdown, you set up a regular data backup, which allows you to restore the system easily.

More information: Backing Up and Restoring Data

Failover Scenario

The following components are single-points-of-failure, if they break down, system operation is no longer possible and data can be lost:

  • Central services instance (with SAP Web Dispatcher and SAProuter)

  • Central dual-stack instance (with AS ABAP and AS Java)

  • MaxDB database instance

  • Central TREX instance

To eliminate the single-points-of-failure completely, you must use high-availability software and additional hardware to configure a failover scenario. The SAP NetWeaver Enterprise Search system architecture supports this scenario by means of virtual hosts.

For more information, contact your hardware provider.