Configuration of MySQLBackupStTest

This test helps administrators figure out the count of backups that failed and the count of backups that were completed successfully. In addition, this test reveals the count of backups that are currently running in the target environment. This test also helps administrators figure out the maximum time duration for a backup to be completed. Using the detailed diagnostics offered by this test, administrators can identify the backup type that is responsible for more backup failures.

The default parameters associated with this test are:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• In the HOST text box, specify the HOST for which this test is to be configured.

• In the PORT text box, specify the port at which the specified HOST listens.

• In the DATABASE text box, specify the name of a database on the target MySQL database server being monitored.

• The eG agent has to be configured with the credentials of a user who has server-wide Process and Select privileges on the monitored MySQL server. Specify the credentials of such a user in the USERNAME and PASSWORD text boxes. To know how to create such a user, refer to Pre-requisites for Monitoring the MySQL Server topic in the Monitoring MySQL Server document.

• Confirm the password by retyping it in the CONFIRM PASSWORD text box.

• In some environments, backups in the target MySQL database server may often take a few minutes and sometimes, take a few hours to complete. By default, a value of 0 is specified against this parameter indicating that the test will consider all backups executing on the target MySQL database server. However, if you wish to ignore a few regular backups that are completed within a specified time limit from the scope of monitoring, then, you can specify a value in minutes against MAXIMUM DURATION parameter. By doing so, this test will not collect information pertaining to the backups that are completed within the duration specified against MAXIMUM DURATION parameter.

• Set SSL flag to Yes if the target MySQL database server that is to be monitored is SSL-enabled. By default, this flag is set to No.

• To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability.

  • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.