Skip to main content

How can we help you?

Druva Documentation

Monitoring VMware jobs

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

 

Jobs

The Jobs page within the Protect > VMware page in the Phoenix Management Console displays a list of all backup, restore, log request, and backup proxy deployment jobs. The Jobs page shows the progress of each VMware job. Job details are available for all jobs. In the job details page you can see the job details and the logs.

Jobs_page.png

To access the VMware Jobs page, perform the following tasks:

  1. Log in to the Phoenix Management Console. 
  2. Under Product & Services > Phoenix, click VMware.
  3. Select your organization.
  4. In the left navigation pane, click Jobs

Note: You can still monitor VMware jobs from the Jobs page. Click Jobs > VMware tab to access the Jobs page.

 The following table lists the fields on the 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 job operation, such as Backup, Restore, Log Request, and Backup Proxy Deployment. You can also filter the jobs based on the type of the operation.

VM Name The name of the virtual machine, for which Phoenix initiates the job.
vCenter/ESXi

The name of vCenter/ESXi on which the virtual machine resides.

Note: You can filter the VMware Jobs page by vCenter/ESXi to display all jobs specific to a vCenter or ESXi server.

Start Time The time when the job operation starts.
End Time The time when the job operations complete.
Status

The status of the triggered job. 

  • Queued: The triggered jobs that are waiting to be processed.
  • Running: The jobs that are being processed.
    After the estimation is completed, the percentage of data uploaded to the cloud is displayed.
  • Successful: The jobs processed without any errors.
  • Successful with errors: The jobs that are processed but have some errors.
  • Failed: The jobs that were not processed successfully.

Note: A failed job is displayed with an error code. Hover on the error code to view the error message. The error code hyperlink redirects to the exact error message description on the documentation portal.

  • Canceled: The jobs that were canceled.
  • Waiting for Retry: The jobs that failed in the previous attempt and waiting to be processed again. For more information on Automatic retry, see Backup retry.
  • Skipped: The jobs that did not start within the scheduled window because another job was in progress or the Phoenix agent or proxy picked the job after the scheduled backup window. 
  • Backup window expired: The list of 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.

View job summary

  1. Log in to the Phoenix Management Console. 
  2. Under Product & Services > Phoenix, click VMware.
  3. Select your organization.
  4. In the left navigation pane, click Jobs
  5. Click on the Job ID and click on the Summary tab. Based on the type of the operation, the job summary is displayed.

Job_Summary.png

Backup job summary

Field Description
Job ID The unique identification number associated with the job.
Job Type The type of operation. For a backup job, the Job Type field displays Backup.
VM Name The virtual machine that initiated the backup.
vCenter/Hypervisor The vCenter/Hypervisor on which the virtual machine resides.
Backup Policy The backup policy associated with the server or virtual machine.
App Aware Processing Indicates if application aware backup was taken for the MS SQL database.
Backup Proxy used for job The backup proxy used by the backup job.
Start Time The time when the backup operation started.
End Time The time when the backup operation finished.
CBT Status Indicates if CBT is enabled.
Status
  • Queued: The triggered jobs that are waiting to be processed.
  • Running: The jobs that are being processed.

After the estimation is completed, the percentage of data uploaded to the cloud is displayed.

  • Successful: The jobs processed without any errors. 
  • Successful with errors: The jobs that are processed but have some errors. 
  • Failed: The jobs that were not processed successfully.

Note: A failed job is displayed with an error code. Hover on the error code to view the error message. The error code hyperlink redirects to the exact error message description on the documentation portal.

  •  Canceled: The jobs that were canceled.
  • Waiting for Retry: The jobs that failed in the previous attempt and waiting to be processed again. For more information on Automatic retry, see Backup retry.
  • Skipped: The jobs that did not start within the scheduled window because another job is in progress.
  • Backup window expired: The list of 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.
Error Code The error code displayed if the backup operation fails. You can click the error code to open the troubleshooting documentation.
Error Message The error message displayed if the backup operation fails.
Data Estimation
Source Data Scanned The scanned source data in order to backup.
# VMDK(s) Changed

The total number of virtual machine disks (VMDKs) that were changed with respect to the previous backup.

# VMDK(s) Removed The total number of virtual machine disks (VMDKs) that were removed with respect to the previous backup.
# VMDK(s) Added The total number of virtual machine disks (VMDKs) that were added with respect 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.
Data Transfer
Data Transferred to Cloud The data that is directly uploaded to Cloud after deduplication and compression.
Data Transferred to CloudCache The incremental data that is directly uploaded to CloudCache after deduplication and compression.
Backup Duration The total time taken to upload data to Cloud and CloudCache. Backup duration excludes the estimation time, network retry time, and the waiting for retry time.
Backup Speed The ratio of source data scanned and uploaded to the backup duration.
Bandwidth Consumed The bit rate to transfer data to cloud and CloudCache.
Environment Details
Disk Read Rate

The bit rate for reading I/O by the agent. The Disk Read Rate is an average of the total data read with respect to the total time taken to read data at various intervals for all drives where data is distributed.  For VMware, the Disk Read Rate is the average value across data store(s) where data is spanning.

# Network Retries The number of network retry attempts made within a job session.
Network Retry Duration The total time spent in the network retries. It represents the cumulative of all network disconnection duration.

Restore job summary

The following table lists the details displayed on the Job Details page.

Field Description
Job ID A unique identification number associated with the job.
Job Type The type of operation. For the restore job, the Job Type field displays Restore, Restore (MS-SQL- Snapshot), Restore (MS-SQL- Transaction Mark), and Restore (MS-SQL- Point in Time)
VM Name The server or virtual machine on which a restore is initiated.
vCenter/Hypervisor The vCenter/Hypervisor on which the virtual machine resides.
Backup Proxy used for job The Backup Proxy used by the restore job.
Start Time The time when the restore starts.
End Time The time when the restore operation completes.
Status The status of the restore operation.
Error Code The error code of the failed restore operation. You can click the error code to open the troubleshooting documentation.
Error Message The error message displayed if the restore operation fails.
Restore Location
Snapshot The snapshot used to restore.
Destination VMware setup The name of the virtual machine to restore data.

Destination Hypervisor

The location of the destination hypervisor to restore data.
After Restore, maintain database in The recovery mode in which the MS-SQL databases need to be maintained once the recovery is complete. If the databases are left in the Recovery mode, you cannot perform any further restores. The databases are accessible to users post the restore. If the databases are left in the Non Recovery mode, you can perform further restores. The databases are inaccessible to users until the final restore.
MS-SQL Instances The name of the instance you want to restore.
Staging VM The name of the staging VM used for restore.
Target Instance The name of the restore target instance.
MDF, LDF, NDF Location The location where you want to restore the files.
Point in Time (Specified) The point in time from when the data is restored.
Transaction Mark The transaction mark from when the data is restored.
Restore Type In case of restore from transaction mark, specifies if the restore must exclude or include  the marked transaction in the restore job.
Data Transfer
Restored Data The total amount of data restored.
Job Speed The rate at which the data is restored. The restore speed is specified in GB/Hr.
Bandwidth Consumed The bit rate to transfer data from cloud and CloudCache.
Environment Details
Disk Write Rate The bit rate for writing I/O by the agent. The Disk Write Rate is the average of the total data written with respect to the total time taken to write data at various intervals.
# Network Retries The number of network retry attempts made within a job session.
Network Retry Duration The total time spent in the network retries. It represents the cumulative of all network session duration.

Log Request job summary

The following table lists the details displayed on the Job Details page.

Field Description
Job ID A unique identification number associated with the job.
Job Type The type of operation. For log request job, the Job Type field displays Log Request.
VM Name The name of the virtual machine for which the log is requested.
vCenter/Hypervisor The vCenter/Hypervisor to which the virtual machine belongs to.
Job ID for requested logs The job identification number for which the log request is generated.
Start Time The time when the log request initiates.
End Time The time when the log request completes.

Status

The status of the log request.

  • Successful: The job completes successfully.
  • Failed: The job fails.
Log Size The size of the extracted log files.
Logs The time of log request with the option to download log files.
Error Message The error message displayed if the log request operation fails.

Backup proxy deployment job summary

The following table lists the details displayed on the Job Details page.

Field Description
Job ID The unique identification number associated with the job.
Job Type The type of operation. For a proxy deployment job, the Job Type field displays Backup Proxy Deployment.
vCenter/ESXi The vCenter/ESXi on which the backup proxy is deployed.
Datacenter The datacenter the backup proxy pools and the vCenter/ESXi is part of.
Backup Proxy Pool used for job The backup proxy pool the backup proxy will be added to.
Start Time The time when the deployment operation starts.
End Time The time when the deployment operation completes.
Backup Proxy Deployed Current status of the number of backup proxies deployed
Backup proxy used for job Backup proxy used for deployment of additional backup proxy.
Status

The status of the deployment job. The status can be one of the following:

  • Running
  • Successful
  • Successful with errors  
  • Failed
Backup proxy details
Backup Proxy Name Name of the backup proxy that is being deployed.
ESXi Host The ESXi host on which the backup proxy is deployed.
Datastore The datastore to which the backup proxy is deployed
IP Address IP address of the backup proxy.
Status

Following statuses are displayed for each proxy:

  • In Progress
  • Successful 
  • Failed

View job logs

The Logs page displays the following information in each section:

Section Description
Progress Logs

Displays the progress logs for the selected job. 

Note: The progress log will contain the information  about automatic backup retries.

Detailed Logs

The detailed logs for the selected job. You can download the logs within seven days of the request.

Note: The detailed logs and client logs follow the backup proxy time zone.

By default, Druva Phoenix displays the timestamps for each job following the administrator time zone. If you set a time zone when updating your account details, the timestamps follow the changed time zone. Both system and progress logs will follow the administrator's time zone.

  1. Log in to the Phoenix Management Console. 
  2. Under Product & Services > Phoenix, click VMware.
  3. Select your organization.
  4. In the left navigation pane, click Jobs
  5. Click on the Job ID and click on the Logs tab. 
  6. You can view the progress logs of the respective operation for a job.
  7. To download the detailed logs for the job, click Request Log Jobs
  8. After you receive an email, the Download Detailed log button is activated. Click the button to download the log zip file.

    Job_logs.png

Upload requested logs

The log files are used to analyze and troubleshoot the issues you might encounter while performing a task. For assistance in resolving the issues, you can share the log files with technical support.

Note Process logs are only available for backup and restore jobs.

The detailed logs include the following:

Common logs for Window, Linux, and backup proxy Window logs Linux logs Backup proxy logs
Druva Phoenix Config Window event/Application logs Dmesg logs VMware logs
Agent-specific Logs VSS information System information  
Main Service logs      

You can request job logs within 30 days of triggering the job. You must download the requested logs within 7 days of triggering the request.If the log file is 4.5 MB or smaller, you can send it to technical support as an email attachment.  If the log file exceeds 4.5 MB in size, perform the following tasks to send the logs to support:

  1. Go to https://upload.druva.com/ 
  2. Enter the case number in the Ticket Number field.
  3. Click Choose File, and add the compressed files to upload.
  4. Click Upload. Notify the support engineer that the logs have been uploaded on the portal by responding to the ongoing support ticket email.