The Job Monitor page is where you can find an overview of all connector activity. Here you can view all of the connectors' past, current, and scheduled jobs (Keepit's backup or restore operations).

On this page you can:

  • Follow the progress of your jobs
  • View reasons for failed jobs, along with information to help you troubleshoot in case of errors
  • See statistics about each job, such as the number of items and amount of data that was backed up or restored
  • Find a list of skipped items in backups and restores and download a detailed CSV report

Viewing the Job Monitor

To view the Job Monitor page:

1. To open the Job Monitor page for all connectors, select the menu icon in the upper-right corner, and then select Job Monitor.

Or, if you want to open the Job Monitor page for a specific connector, select the Job Monitor icon next to the right of your connector. This will preset the filter to the selected connector. 

2. Filter jobs by connector, status, type, time span, start and end date, and then select the Refresh button. Details about each job will be displayed for the selected connector(s). You can also use the free text filter to locate specific information in the entries you are viewing. 

Note: When a job is in progress, the statistics are updated every 5 minutes. Refresh the page to see the new results.

3. In the Description column you will find an overview of the job. Select Show more to find a summary, and if applicable, statistics about the job as well as a list of skipped items that can be downloaded as a CSV report.

Note: If the job was cancelled or failed, the entry will be highlighted in red.

Example of a successful summary:

Example of a failed job summary: 

4. To download a job report as a CVS file, click Download as CSV. 

Understanding the Job Monitor page


Job Types

  • Backup job - The Keepit operation that performs a backup. The result is a snapshot that contains copies of data.    
  • Restore job - The Keepit operation that restores a data type or data types across accounts. Imports are found under this job type. 
  • Item restore job - The Keepit operation that restores an individual item or folder. 

Job Statuses

  • Failed
    A backup job will be marked as failed if the entire backup attempt fails. 
    A restore job will be marked as failed if the entire restore attempt fails, if all items are skipped, or if one or more items are skipped.
    The reason for failed jobs and possible actions to take can be found by selection See more on the Job Monitor page next to the job.
  • Cancelled
    A job can be cancelled only by Support at the request of the customer.
  • In progress
    The job is still being performed.
  • Scheduled
    Scheduled backup jobs can be seen by setting the "End date" onе day ahead of the current day.
    Scheduled restore and item restore jobs will be immediately displayed in the Job Monitor.
  • Succeeded
    Jobs that completed successfully.
    A backup job will be marked as succeeded if at least one or more items are successfully backed up. This means that a backup will be marked succeeded even if some items were not backed up. The system will mark these items as skipped and will attempt to back them up during the next job. A backup job will also be marked succeeded if nothing changed from the last snapshot. In this case you will see 0 MB and 0 items backed up.
    A restore or item restore will be marked succeeded only if all items are successfully restored.


Reasons for Failed Jobs and Possible Resolutions

Reasons for Failed Backup Jobs

  • Job aborted
    If a backup job is aborted, you do not need to take any action in this case. A new job will automatically be scheduled. 
  • Error
    If an error occurs, contact Support so we can take a deeper look into it and make sure everything is OK.
  • User not Global admin
    The job will fail if the account used for the backup is not a Global admin. It is possible that after you set up your backup, the Global admin was changed to a different user and so a new backup cannot begin. Assign your Office 365 service account the Global admin role and then try re-authenticating. For more information, see Prepare your Office 365 account  
  • Authentication failed
    The job will fail if the backup could not start because authentication failed. Re-authenticate your connector by selecting the "Credentials no longer valid, please update" next to your connector. For more information, see Why are my credentials no longer valid?
  • API request usage limit reached
    The backup could not start because we reached the API request usage limit that is set for your Salesforce connector. If you want your backup to complete sooner, you can increase the percentage of API requests that we use, but keep in mind that this can affect performance. For more information, see Your Salesforce API Request Usage
  • Configuration corrupted
    If your backup configuration is corrupted, contact Support so we can fix the configuration and start your backup.
  • Incident occurred
    When an incident occurs on the server, we immediately work to fix the issue. You don't need to contact support unless this continues to occur. 

Reasons for Failed Restore Jobs

  • At least one item skipped
    A restore job is marked as failed if one or more items were not restored. To see which exact items were skipped, download a skipped files report. If necessary, start a restore of these files individually.
    If many items were skipped, you can start the same restore again. Or if a small amount of items were skipped, you can restore these files individually.
    If you are restoring a SharePoint site, be aware that certain metadata, column and content types, or permissions may not restore. In most of these cases, your actual data will be returned. Please check in SharePoint and see if you have the necessary data. If not, please try again.
  • All items skipped
    A restore job is marked as failed if the job completed but no items were restored. Please try to restore again. If this continues to occur, contact Support so we can help you identify and solve the problem.
  • Job aborted
    If the restore job is aborted, you do not need to take any action. A new job will be automatically scheduled. 
  • Error
    If an error occurs, contact Support so we can take a deeper look into it and make sure everything is OK. 
  • User not Global admin
    The job will fail if the Microsoft account used for backups and restores is not a Global admin. Assign your service account the Global admin role and then try re-authenticating. For more information, see Prepare your Office 365 account
  • Authentication failed
    The job will fail if the restore could not start because authentication failed. Re-authenticate your connector by selecting the "Credentials no longer valid, please update" next to your connector. For more information, see Why are my credentials no longer valid?
  • API request usage limit reached
    The restore could not start because we reached the API request usage limit that is set for your Salesforce connector. You can increase your Salesforce API request and then try restoring again. For more information, see Your Salesforce API Request Usage  
  • Invalid restore configuration
    If the restore configuration generated in the web client is invalid, contact Support so we can fix the configuration and start your restore.
  • Incident occurred
    When an incident occurs on the server, we immediately work to fix the issue. You don't need to contact support unless this continues to occur.

Backup Job Statistics

  • Added – items added and/or changed since the last backup.
  • Removed – items removed from the backup because they no longer exist in the could service. For example, if an email or file is deleted, then it is removed from the current snapshot, but it will still exist in older snapshots.
  • Skipped – items that could not be reached due to such reasons as throttling, API failures, or inaccessibility from Microsoft’s side. The system will tag these items as skipped and try again to reach them during the next backup.
    The number of skipped items includes the total number of all items and folders that were skipped. The size of skipped items includes only the size of items that were skipped (not of folders)

Note: For Salesforce and Dynamics connectors, skipped items during a backup may be system files that do not contain your data and are not needed for restore. 


Restore Job Statistics

  • Restored - items that were successfully restored.
  • Overwritten - items in the target location that were replaced by files from the snapshot. This occurs when an item is in found in the snapshot and in the target location, but the contents are different. In this case we overwrite the item in the target location with the item in the snapshot.
  • Skipped - items that failed to be restored due to such reasons as throttling, a bad request, or a bad token.
    Number and size of skipped items includes total of all items and folders that were skipped.


Skipped Items

Skipped items are listed for each backup and restore job. A report with a list of logs that show which files were skipped can be generated and downloaded as a CSV file.

In most cases, if a file is skipped during a job, it will be backed up or restored in the next job.

The reports can be used to check whether there are certain files that are skipped continuously. CSV files from multiple jobs can be compared to track such possible items. 

If more than 100 items were skipped, the list can only be downloaded as a CSV file. 

Note: Skipped items lists and CSV file reports are only available for one month after the completion of the job.