https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMTYxIiwiaGFzaCI6ImQ2NDJmNjMzLTk1MWItNDYwYy04OWI0LTI2MmExNWE3NTU4NyJ9
1-800-691-1991 | 9am - 8pm ET
EN

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.
 
KB ID:
2161
Product:
Veeam Backup & Replication, Veeam Cloud Connect
Version:
9.x
Published:
2016-09-02
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

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

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.