Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
Fine-Tuning High Availability Settings
The previous sections describe high availability (HA) for OMi. We recommend that you follow the guidelines described there as the best practice for working with OMi. However, if you must shorten the duration of the failover process, you can fine-tune OMi high availability settings.
Administration > Setup and Maintenance > Infrastructure Settings
Alternatively, click Infrastructure Settings.
Select Foundations and use the list to set the context to High Availability Controller.
Learn More
The High Availability Controller (HAC) component provides failover functionality. The HAC on the data processing server monitors all its processes, and updates their availability status in the database every 20 seconds. A failure condition is detected when the availability state of a process is not updated in the database for a specific (configurable) duration. The HAC then initiates the failover for that process if the backup server is available.
Within OMi, the High Availability Controller infrastructure settings define how high availability is controlled.
Tasks
When setting HAC parameters, always follow the following rule:
Monitor Failures Interval <= Normal Keep Alive Period <= Critical Keep Alive Period <= Keep Alive Timeout.
Modify the parameter values according to the following guidelines:
-
Set the Failover Stabilization Time close to the data processing server start time in your environment.
-
The lowest value should be assigned to the Monitor Failures Interval (default = 1 minute), all other values should be greater than this.
-
The Keep Alive Timeout (default = 5 minutes) should be assigned the highest value among all the parameters.
-
All other parameters should be assigned a value equal to or less than the Keep Alive Timeout; these other parameters are for internal management of the processes when they are failing, so all cleanup tasks must be finished within this time and before failover starts (after expiry of Keep Alive Timeout).
-
Assigning a very low value to Critical Keep Alive Period (default = 4 minutes) and Failover Stabilization Time (default = 10 minutes) can cause the same service to be active on both servers, or multiple failovers during DPS startup and switchover time.
-
When Keep Alive Timeout is set to less than the startup time of the data processing server, restarting the primary server can cause activation of the backup server. To prevent this, stop the backup server before restarting the primary, and start the backup only after the primary is up again.
Note Although there is a logical relationship between the HAC parameters, and their values should follow a logical order, this is not enforced by OMi. OMi enables you to set any value (within the range of 1 – 1440 minutes) for the time-related parameters, and does not validate the values for inter-dependency. For example, you can set the Monitors Failures Interval value higher than the Keep Alive Timeout even though this is logically incorrect.
For example, if the data processing server start time is 5 to 7 minutes and HAC Services Activation Time is 2 to 3 minutes, you can use the following minimum values:
-
Keep Alive Timeout – 2 minutes
-
Critical Keep Alive Period – 2 minutes
-
Normal Keep Alive Period – 2 minutes
-
Failover Stabilization Time – 2 minutes
-
Monitor Failures Interval – 1 minute
As a result, the service failure will be identified within 2 minutes, instead of the default 5 minutes.
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: