Agents Administration - Tests
 

Default Parameters for AzrBackupJobsTest

This test tracks the status of the backup jobs that have been triggered for an Azure Subscription and reports the count of jobs in different states. In the process, the test alerts administrators to failed jobs and jobs that have been running for a duration beyond a configured time limit. Detailed diagnostics throw light on the exact jobs that failed or are long-running, thus enabling administrators to easily troubleshoot the failure/abnormal run time (as the case may be).

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

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

  • Specify the GUID which uniquely identifies the Microsoft Azure Subscription to be monitored in the SUBSCRIPTION ID text box.To know the ID that maps to the target subscription, click here.

  • Specify the Directory ID of the Azure AD tenant to which the target subscription belongs in the TENANT ID text box. To know how to determine the Directory ID/Tenant ID, click here.

  • The eG agent communicates with the target Microsoft Azure Subscrption using Java API calls. To collect the required metrics, the eG agent requires an Access token in the form of an Application ID and the client secret value.Specify the Application ID of the created Application in the CLIENT ID text box. To know how to determine the Application ID ,click here. Specify the client secret value in the CLIENT PASSWORD text box. To obtain the client secret value, click here.

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

  • In some environments, all communication with the Azure cloud be routed through a proxy server. In such environments, you should make sure that the eG agent connects to the cloud via the proxy server and collects metrics. To enable metrics collection via a proxy, specify the IP address of the proxy server and the port at which the server listens against the PROXY HOST and PROXY PORT parameters. By default, these parameters are set to none , indicating that the eG agent is not configured to communicate via a proxy, by default.

  • If the proxy server requires authentication, then, specify a valid proxy user name and password in the PROXY USERNAME and PROXY PASSWORD parameters, respectively. Then, confirm the password by retyping it in the CONFIRM PASSWORD text box.

  • By default, this test does not provide detailed diagnostics for the In progress jobs measure. Accordingly, SHOW DD FOR IN PROGRESS JOBS flag is set to No by default.

    If you want to know which backup jobs are in progress currently, then you need to enable detailed diagnosis for the In progress jobs measure by setting this flag to Yes. Before doing so, make sure that your eG database is well-tuned and adequately sized to handle the additional load imposed by these detailed metrics.

  • By default, this test does not provide detailed diagnostics for the Completed jobs measure. Accordingly, SHOW DD FOR COMPLETED JOBS flag is set to No by default.

    If you want to know which backup jobs are in progress currently, then you need to enable detailed diagnosis for the Completed jobs measure by setting this flag to Yes. Before doing so, make sure that your eG database is well-tuned and adequately sized to handle the additional load imposed by these detailed metrics.

  • In the Azure Backups context, a datasource represents the data to be backed by. By default, this test monitors all backup jobs that have been triggered for the target Azure Subscription, regardless of the location of the datasources that are being backed up. Accordingly, Datasource Location Names parameter is set to ALL by default. However, if you want the test to monitor only those backup jobs that are taking backups of datasources in a specific location (eg., Central US, Brazil Sourth etc.), then specify that location name in the Datasource Location Names text box. You can even configure multiple datasource location names, as a comma-separated list. For instance, your specification can be: Central US, Brazil South, East Asia. To know what location names you can provide,click here

  • By default, this test monitors all back up jobs that have been triggered for the target Azure Subscription, regardless of the type of datasources that are being backed up. Accordingly,Datasource Types parameter is set to ALL by default. However, if you want the test to monitor only those backup jobs that are taking backups of a specific type of datasource (eg., Azure Files, Azure Virtual machines, Azure Disks etc.), then specify that datasource type in the Datasource Types text box. You can even configure multiple datasource types, as a comma-separated list. For instance, your specification can be: Azure Virtual machines,Azure Blobs,Azure Disks. To know what datasource types you can provide,click here

  • A vault is an online-storage entity in Azure that's used to hold data, such as backup copies, recovery points, and backup policies. Azure Backup stores backed-up data in Recovery Services Vaults or in Backup Vaults.

    • Backup Vault: This is a storage entity in Azure that houses backup data for various Azure services, such Azure Database for PostgreSQL servers and newer workloads that Azure Backup will support. Backup vaults are based on the Azure Resource Manager model of Azure.

    • Recovery Services Vault: This is a storage entity in Azure that houses copies of data and configuration information for Azure Virtual machines, workloads, servers, or workstations, and for various Azure services such as IaaS VMs (Linux or Windows) and Azure SQL databases. Recovery Services vaults are based on the Azure Service Manager model of Azure.

    By default, this test monitors all backup jobs that have been triggered for the target Azure Subscription, regardless of the vaults in which the backed up data is stored. Accordingly, Vault Names parameter is set to ALL by default. However, if you want the test to monitor only those backup jobs that are storing backups in a specific vault, then specify the name of that vault in the VAULT NAMES text box. You can even configure multiple vault names, as a comma-separated list. For instance, your specification can be:SMTest2Vault,TempVault,AzrVMVault. Note that your specification can include the names of both Backup vaults and Recovery Services vaults.To know what vault names you can provide,click here

  • Specify the duration (in minutes) beyond which a backup job should be running for it to be considered a long-running job in the LONG RUNNING JOBS LIMIT text box. By default, the value of this parameter is set to 180 minutes. This means that, by default, this test will count the number of backup jobs that have been running for over 180 minutes, and report that count as the value of the Number of long running jobs measure. You can increase or decrease this time limit if you so need.

  • The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

  • Once the necessary values have been provided, clicking on the UPDATE button will 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.