Processing VMNAME Error: Job was stopped due to backup window setting - Case # 01078050. We do want to be notified of all errors(Failures), but this event is self induced because of the backup window.
Can the status of this notification be changed from an error to a warning?
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Mar 16, 2015 9:14 pm
- Contact:
-
- Veteran
- Posts: 7328
- Liked: 781 times
- Joined: May 21, 2014 11:03 am
- Full Name: Nikita Shestakov
- Location: Prague
- Contact:
Re: Feature Request - Backup Window Error
Hello,
I don`t think there is an easy way to change the severity from error to warning.
Could you please, describe your use case, why you need it to be done?
Thanks!
I don`t think there is an easy way to change the severity from error to warning.
Could you please, describe your use case, why you need it to be done?
Thanks!
-
- Novice
- Posts: 4
- Liked: 2 times
- Joined: Sep 06, 2019 4:10 pm
- Full Name: Eugen Fournes
- Contact:
Re: Feature Request - Backup Window Error
Looks like this error message was removed from Veeam B&R for a while, then added back again in v10a. Submitted case #04603755.
Just like groach, above, we want to know about actual errors/failures, but would like to suppress this one, or change it to a warning at least, when we *know* a backup copy job is going to be delayed by a restrictive upload window.
Use case: (we're an MSP) and a number of our clients have slow Internet connections and we have to limit the upload window to only run overnight. The off-site backups sometimes take longer than overnight to complete.
In conjunction with this, we're also receiving the error:
Job finished with error. Job has failed unexpectedly Details: Error: Data transfer is currently restricted.
This is because we've restricted the cloud connection for this client to a single data stream, since that one stream pretty much saturates their Internet connection. Increasing the concurrent connections makes all of the off-site backup jobs take longer.
When we upgraded to Veeam B&R v10a, instead of a single warning, we're now receiving three errors for a cloud repository backup job that takes more than a day to complete: the above two errors, plus the RPO error because the default is set to one day.
At least the RPO error we could suppress by raising it to three days. Isn't this what the RPO is supposed to be for--to notify us if the on-site backup isn't sync'd to the off-site within the specified amount of time? Why would we need three separate errors?
We request that the "backup window" error and the "data transfer is currently restricted" error either be removed altogether, switched to warnings, or given the ability to be suppressed through the Veeam Service Provider Console. Or, another thought, combine all three into the RPO error:
Backup copy job failed to meet RPO (2 days): data transfer restricted to 1 concurrent connections, job stopped due to backup window settings. %jobname% %VMname%, etc. Possible solutions: Check other jobs that may be tying up the connections or allow more concurrent connections; expand the data transfer window; increase network speed.
Thanks!
Just like groach, above, we want to know about actual errors/failures, but would like to suppress this one, or change it to a warning at least, when we *know* a backup copy job is going to be delayed by a restrictive upload window.
Use case: (we're an MSP) and a number of our clients have slow Internet connections and we have to limit the upload window to only run overnight. The off-site backups sometimes take longer than overnight to complete.
In conjunction with this, we're also receiving the error:
Job finished with error. Job has failed unexpectedly Details: Error: Data transfer is currently restricted.
This is because we've restricted the cloud connection for this client to a single data stream, since that one stream pretty much saturates their Internet connection. Increasing the concurrent connections makes all of the off-site backup jobs take longer.
When we upgraded to Veeam B&R v10a, instead of a single warning, we're now receiving three errors for a cloud repository backup job that takes more than a day to complete: the above two errors, plus the RPO error because the default is set to one day.
At least the RPO error we could suppress by raising it to three days. Isn't this what the RPO is supposed to be for--to notify us if the on-site backup isn't sync'd to the off-site within the specified amount of time? Why would we need three separate errors?
We request that the "backup window" error and the "data transfer is currently restricted" error either be removed altogether, switched to warnings, or given the ability to be suppressed through the Veeam Service Provider Console. Or, another thought, combine all three into the RPO error:
Backup copy job failed to meet RPO (2 days): data transfer restricted to 1 concurrent connections, job stopped due to backup window settings. %jobname% %VMname%, etc. Possible solutions: Check other jobs that may be tying up the connections or allow more concurrent connections; expand the data transfer window; increase network speed.
Thanks!
Who is online
Users browsing this forum: Bing [Bot] and 91 guests