Failed job is marked as Successful on the Cloud Provider side

KB ID:
2161
Product:
Veeam Backup & Replication;Veeam Cloud Connect
Version:
9.x
Published:
Last Modified:
2019-05-02

Challenge

In some cases a SP backup server receives "Success" status of a tenant job even when the job has failed on the Tenant's server.

Cause

Generally, cloud job sessions are marked failed on the SP backup server in the following cases:

  • All cloud gateways are unavailable
  • There is not enough space on the disk
  • An existing connection was forcibly closed by the remote host
  • Repository quota exceeded
All issues above should be corrected by a SP, and therefore Veeam reports such jobs as failed. For other types of issues, a failed job may be marked successful because it cannot be fixed on the SP side and requires involving a tenant.

NOTE: Direct Agent to Cloud job sessions are always marked as successful in the SP's console.
 

Solution

Rate the quality of this KB article: 
2.5 out of 5 based on 18 ratings

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.

Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text:

Submit