Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Server Automation10.60

Administer > SA maintenance > Multiple data access engines

Multiple data access engines

This section discusses the following topics:

Overview
Reassigning the data access engine to a secondary role
Designating the multimaster central data access engine

Overview

In a core with multiple instances of the Data Access Engine, each instance may be designated in one of the following ways:

Primary Data Access Engine: Each Facility has only one primary Data Access Engine. This Data Access Engine periodically checks the Managed Servers to determine if SA can communicate with them. If a facility has more than one primary Data Access Engine, the competing reachability checks can interfere with each other.
Secondary Data Access Engine: When a Facility has multiple Data Access Engines installed (for scalability), the non-primary ones are designated as secondary data access engines. The first Data Access Engine installed is designated the Primary or Multimaster Central Data Access Engine. A secondary Data Access Engine does not check managed servers to determine if they are reachable. It only communicates with the Model Repository to write or read data.
Multimaster Central Data Access Engine: An SA Multimaster Mesh has multiple cores and therefore multiple data access engines. One core’s primary data access engine should be designated the Multimaster Central Data Access Engine. Although any of the cores may have multiple Data Access Engines, only one per mesh can be the central data access engine.

Reassigning the data access engine to a secondary role

This functionality was moved from the SA Client to SA Java Client. So, if you installed an additional Data Access Engine, you must perform the following steps to reassign the new Data Access Engine to a secondary role:

Log into the SA Java Client as a user that belongs to SA Administration group.
Select the Administration tab to display your administration inventory.
Select System Configuration > Service Level Members. The Service Levels tree is displayed.
Choose the Data Access Engine (spin) node. The Managed Servers that are hosting a Data Access Engine will appear in the members table.
Select the desired Data Access Engine server and press the Cut button, or choose the Cut action from right-click actions, or from Actions menu.
Then select Secondary node from tree and press the Paste button, or choose the Paste action from right-click actions, or from the Actions menu.
A confirmation dialog will appear. Click Yes.
The new Data Access Engine server will appear in the members table.
In a terminal window, log in as root to the server running the additional Data Access Engine, and enter the following command to restart the Data Access Engine:
/etc/init.d/opsware-sas restart spin

Designating the multimaster central data access engine

The HPE BSA Installer automatically assigns the multimaster central Data Access Engine.

In most cases, you should not change the multimaster central Data Access Engine after the installation. Doing so can cause problems when upgrading the SA core to a new version. Before following the steps in this section, contact HPE Professional Services.

This functionality was moved from the SA Web Client to the SA Java Client, so perform the following steps to designate the multimaster central data access engine:

Log into the SA Java Client as a user that belongs to the SA System Administrators group.
Select the Administration tab to display your administration inventory.
Select System Configuration > Service Level Members. The Service Levels tree is displayed.
Choose the Data Access Engine (spin) node. The Managed Servers that are hosting a Data Access Engine will appear in the members table.
Select the desired Data Access Engine server and press the Cut button, or choose the Cut action from right-click actions, or from the Actions menu.
Then select Multimaster Central node from tree and press the Paste button, or choose the Paste action from right-click actions, or from the Actions menu.
A confirmation dialog will appear. Click Yes.
The new Data Access Engine server will appear in the members table.
In a terminal window, log in as root to the server running the additional Data Access Engine, and enter the following command to restart the Data Access Engine:
/etc/init.d/opsware-sas restart spin

Send Help Center feedback