Failed job is marked as Successful on the Cloud Provider side

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.