Default Parameters for CmvltJobSmryTest

Jobs are placed in a job controller and run when resources are available. If the jobs in the job queue are not processed quickly, it would result in an overload condition characterized by long-winding job queues thus leading to the slowdown of the Commvault Backup server. In the event of such abnormalities, administrators will have to instantly figure out the count of jobs that are pending / queued / waiting. The CmvltJobSmryTest test helps administrators in this regard.

This test reports the total number of jobs executing on the target Commvault Backup server. In addition, this test reveals the number of jobs that are pending / waiting and those that are queued. Administrators can use this test to further analyze on why the jobs are pending / waiting in queue for a duration longer than usual.

This page depicts the default parameters that need to be configured for the CmvltJobSmryTest test.

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

• By default, the eG agent executes CLI Commands on the target Commvault Backup server to collect the required metrics. For the eG agent to execute the CLI commands, a special user with monitoring privilege is required. Specify the credentials of such a user in the COMMVAULT ID and COMMVAULT PASSWORD text boxes.

• Confirm the password by retyping it here in the Confirm Password text box.

• By default, the CLI commands that need to be executed by the eG agent will be located within a folder called ‘Base’ within the install directory of the target Commvault Backup server. For the eG agent to execute the commands, specify the full path to the Base folder against the BASE INSTALLED LOCATION parameter. For example, the full path to the Base folder can be specified as: C:\\Program Files\\Commvault\\Contentstore\\Base.

• Once the above values are provided, click on the UPDATE button to register the changes made.

When changing default configurations of tests, the values with “$” indicate variables that will be replaced by the eG system according to the specific server being managed - for instance, $hostName is the host/nickname of the target host, $port is the port number of the server being monitored. E.g., for a server xyz:80, $hostName will be changed automatically by the eG manager to “xyz*” and $port will be changed to “80” when configuring a test.