Skip to main content
Monitor Azure SQL jobs
Updated over 2 weeks ago

❗ Important

This feature has limited availability. To know more about limited availability and sign up for this feature, contact your Account Manager.


The All Jobs page on the Management Console provides an integrated view of all UI-triggered scheduled and maintenance activities. Each job is identified by a unique Job ID and holds a specific status, and the job progress can be tracked via the progress log.

To view Azure SQL jobs:

  1. Log in to the Management Console.

  2. On the console, from the top menu, select Organization.

  3. Select Protect > Go to Azure.

  4. Navigate to All Jobs > Azure SQL.
    You can view all Backup and Restore jobs on this page.The following table lists the fields on the All Jobs page.

Field

Description

Job ID

A unique identification number associated with the job. Click on the job ID to view the job details. For more information, see View job summary. You can also view the logs of each job. For more information, see View job logs.

Job Type

The type of operation, that is Backup or Restore. You can filter jobs based on the job type.

Backup Set

Name of the SQL backup set for which the job was created.

Resource Type

The Azure SQL resource for which the job was triggered. The resource can be SQL server on Azure VM, SQL Database, or a Managed Instance.

Start Time

The time when the job was initiated.

End Time

The time when the job ended.

Status

The current status of each job.

  • Queued: The triggered jobs that are waiting to be processed.

  • Running: The jobs that are being processed.

  • Successful: The jobs were completed without any errors.

  • Successful with errors: The jobs that are executed with a few errors.

  • Failed: The jobs that did not complete successfully.


    πŸ“ Note
    ​ A failed job is displayed with an error code. Hover over the error code to view the error message. You may click the error code to be redirected to the error documentation.


  • Canceled: The jobs that were canceled.

  • Waiting for Retry: The jobs that failed in the previous attempt and waiting to be processed again.

  • Skipped: The jobs that were skipped.

  • Backup window expired: Jobs that could not be completed because their backup window expired.

  • Canceled: The jobs that were canceled.

  • Waiting for retry: The jobs that failed in the previous attempt and are waiting to be processed again. A job is retried twice within an interval of 10 minutes.

  • Window Expired: The list of backup jobs Phoenix could not complete because the entire data set was not backed up within the specified duration, and a restore point was not created.

Filters

Use the job filters to filter the jobs based on Job Type, Job Status, or when the job was triggered. You can apply one or more filters to view individual jobs and associated logs within the chosen job category.

  • Job Created in: Filter jobs triggered in the Last 24 hrs, Last 7 days, Last 1 month, or specify a custom Date Range.

  • Job Type: Filter by type to view Backup or Restore jobs.

  • Job Status: Filter jobs based on the current job status. For more information see Job Status.

View job details

Click the Job ID to view the job details. The job details page has two tabs:

  • Details

  • Logs

Details

The details tab has following sections:

  1. Job Details

The details section gives the summary of the triggered job and has following details:

Field

Description

Job Type

The type of job executed-Backup or Restore.

Backup Set

The backup set on which the job was triggrered.

Instance

The name of the SQL resource on which the job was triggered.

Resource Type

The type of resource- SQL Server on Azure VM, SQL Database, or Managed Instance.

Backup Policy

The backup policy associated with the backup set

Status

Completion status of the job

Start Time

The time when the job started.

End Time

The time when the job ended.

2. Data Estimation

The Data Estimation section has the following fields:

Field

Description

Source Data Scanned

The volume of data scanned at the source for the backup.

# DBs Changed

The total number of databases that were changed as compared to the previous backup.

# DBs Added

The total number of databases that were added as compared to the previous backup.

# DBs Removed

The total number of databases that were removed as compared to the previous backup.

Time Taken for Estimation

The approximate time taken to scan the data. The time taken for estimation does not include network retry time.

3. Data Transfer

The Data Estimation section has the following fields:

Field

Description

Data Exported

The volume of data exported.

Data Transferred to Cloud

Total data backedup to the Cloud after compression and deduplication.

Export Duration

Total time taken to export the data.

Data Transfer Duration

Total time taken to backup data to the Cloud. This excludes the estimation time, network retry time, and the waiting for retry time.

Job Speed

The rate at which the data is uploaded to Druva Storage.

Logs

Administrators and DBAs can monitor progress of the backup and restore jobs using the progress logs and detailed logs generated during the job.

The Logs tab displays the following information:

  • Progress Logs: Displays the summary of the progress of the backup and restore jobs triggered for the SQL resources.

Log files help analyze and troubleshoot issues encountered while performing a task. You can share the logs with the Support team to aid in issue resolution.

  • Detailed Logs: The Detailed Logs section gives you the option to Request Detailed Logs. Detailed logs are available only after the upload job completes. Till then, the Request Detailed Logs button remains disabled. The logs are available for download till a certain date and time specified under the Available for download till field. The Requested on field shows you when the request for detailed logs was made.


Notes:

  • The Download Detail Logs button remains disabled till the time download is in progress or the user refreshes the page.

  • The Download Detail Logs button is not available for jobs that are in-progress.

Did this answer your question?