Systems with Master, Backup, and Slave Index Servers
This section depicts the configuration for systems with master, backup, and slave index servers. The systems differ as to the number and assignment of backup index servers. The following variants are taken into account:
- One backup index server per master index server
- One backup index server, one master index server
- One backup index server, two master index servers
- One backup index server for all master index servers
The same specifications are valid for the master and backup queue servers.
TREX admin tool, Landscape Configuration
Areas Scenario, Scenario Details, and Index
| Area | Field | Value |
|---|---|---|
|
Scenario |
Use Backup Index/Queue Servers |
! |
|
Use Slave Index Servers |
! |
|
|
Use a File Server |
! |
|
|
Scenario Details |
Use One Shared Backup Server |
|
|
Assign Existing Indexes/Queues to New Backup/Slave Servers |
||
|
Index |
Search on Master/Backup Server |
|
|
Search Version |
majority |
|
|
Replication Threads |
1 |
Hosts table (extract 1)
| Host | Name Server Mode | Master Index/Queue Server | Backup Index/Queue Server for | Slave Index Server for |
|---|---|---|---|---|
|
mytrexmaster |
1st master |
! |
||
|
mytrexbackup |
2nd master |
! mytrexmaster |
||
|
mytrexslave1 |
slave |
! mytrexmaster |
||
|
mytrexslave2 |
slave |
! mytrexmaster |
Hosts table (extract 2)
| Host | Preprocessor Mode | Base Path |
|---|---|---|
|
mytrexmaster |
index |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexbackup |
index |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave1 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave2 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
Windows: TREXDaemon.ini on all hosts (extract)
[mappings]
map_t=\\myfileserver\mytrexshare
Two Backup Index Servers, Two Master Index Servers
TREX admin tool, Landscape Configuration
Areas Scenario, Scenario Details, and Index
As in the previous example
Hosts table (extract 1)
| Host | Name Server Mode | Master Index/Queue Server | Backup Index/Queue Server for | Slave Index Server for |
|---|---|---|---|---|
|
mytrexmaster1 |
1st master |
! |
||
|
mytrexmaster2 |
2nd master |
! |
||
|
mytrexbackup1 |
3rd master |
! mytrexmaster1 |
||
|
mytrexbackup2 |
slave |
! mytrexmaster2 |
||
|
mytrexslave1 |
slave |
! mytrexmaster1 |
||
|
mytrexslave2 |
slave |
! mytrexmaster1 |
||
|
mytrexslave3 |
slave |
! mytrexmaster2 |
||
|
mytrexslave4 |
slave |
! mytrexmaster2 |
Hosts table (extract 2)
| Host | Preprocessor Mode | Base Path |
|---|---|---|
|
mytrexmaster1 |
index |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexmaster2 |
index |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexbackup1 |
index |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexbackup2 |
index |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave1 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave2 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave3 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave4 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
One Backup Index Server for All Master Index Servers
TREX admin tool, Landscape Configuration
Area Scenario Details
| Area | Field | Value |
|---|---|---|
|
Scenario |
Use Backup Index/Queue Servers |
! |
|
Use Slave Index Servers |
! |
|
|
Use a File Server |
! |
|
|
Scenario Details |
Use One Shared Backup Server |
! |
|
Assign Existing Indexes/Queues to New Backup/Slave Servers |
||
|
Index |
Search on Master/Backup Server |
|
|
Search Version |
majority |
|
|
Replication Threads |
1 |
Hosts table (extract 1)
| Host | Name Server Mode | Master Index/Queue Server | Backup Index/Queue Server | Slave Index Server for |
|---|---|---|---|---|
|
mytrexmaster1 |
1st master |
! |
||
|
mytrexmaster2 |
2nd master |
! |
||
|
mytrexbackup |
3rd master |
! |
||
|
mytrexslave1 |
slave |
! mytrexmaster1 |
||
|
mytrexslave2 |
slave |
! mytrexmaster1 |
||
|
mytrexslave3 |
slave |
! mytrexmaster2 |
||
|
mytrexslave4 |
slave |
! mytrexmaster2 |
Hosts table (extract 2)
| Host | Preprocessor Mode | Base Path |
|---|---|---|
|
mytrexmaster1 |
index |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexmaster2 |
index |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexbackup |
index |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave1 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave2 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave3 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
|
mytrexslave4 |
search |
UNIX: /mypath/mytrexdir Windows: T: |
Features of a Blade System
If you are using a blade system and the TREX data is located in the installation directory, the column Base Path has the following value:
Hosts table (extract)
| Host | Base Path |
|---|---|
|
mytrexmaster |
usr/sap/<SAPSID>/TRX<instance_number> |
|
... |
... |
The rest of the configuration is the same.