-
- Service Provider
- Posts: 12
- Liked: 1 time
- Joined: Feb 05, 2020 3:10 pm
- Contact:
[Feature Request] log 'Bad Request (400)' warnings and continue job.
Dear,
We have a customer for whom we backup OneDrive, SharePoint and Exchange.But the OneDrive part is giving us headaches.
There are about 400 users in the job and for 99% of these users the daily incremental backup is completed within 10 minutes.
But one of 2 users keep stalling the job because they have files that are (correct or not) blocked by SharePoint online antivirus.
Because of these users the job is stalling for hours (yesterday almost 12 hours) and afterwards it ends with a warning 'Bad request (400)'.
I have opened a support case (04233172) for this but I would be nice if there's a structural solution for this.
For instance, the possilibity to lower the 'bad request' timeout on thise loced files so the job fails a lot sooner then 12 hours so the potentionaly infected files can be deleted faster.
Another, and even better, solution would be that Veeam keeps a log of files that give a bad request warning but continuous with the backup. When the job completes with a warning Veeam writes the log to a specified location where the administrator can check the list of files.
Also, when a user has for instance 1000 OneDrive files and the job hangs at lets say file 600. Does Veeam backup the other 400 files or are they missing in the backup?
Thanks in advance.
Kind regards,
We have a customer for whom we backup OneDrive, SharePoint and Exchange.But the OneDrive part is giving us headaches.
There are about 400 users in the job and for 99% of these users the daily incremental backup is completed within 10 minutes.
But one of 2 users keep stalling the job because they have files that are (correct or not) blocked by SharePoint online antivirus.
Because of these users the job is stalling for hours (yesterday almost 12 hours) and afterwards it ends with a warning 'Bad request (400)'.
I have opened a support case (04233172) for this but I would be nice if there's a structural solution for this.
For instance, the possilibity to lower the 'bad request' timeout on thise loced files so the job fails a lot sooner then 12 hours so the potentionaly infected files can be deleted faster.
Another, and even better, solution would be that Veeam keeps a log of files that give a bad request warning but continuous with the backup. When the job completes with a warning Veeam writes the log to a specified location where the administrator can check the list of files.
Also, when a user has for instance 1000 OneDrive files and the job hangs at lets say file 600. Does Veeam backup the other 400 files or are they missing in the backup?
Thanks in advance.
Kind regards,
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Feature request: log 'Bad Request (400)' warnings and continue job.
Hi @gvo91
What version is the customer running? If I am not mistaken this is solved in version 4c. We skip the file and put a message in the corresponding log.
What version is the customer running? If I am not mistaken this is solved in version 4c. We skip the file and put a message in the corresponding log.
-
- Service Provider
- Posts: 12
- Liked: 1 time
- Joined: Feb 05, 2020 3:10 pm
- Contact:
Re: Feature request: log 'Bad Request (400)' warnings and continue job.
Hi Mike,
Thanks for your prompt reply.
The production environment is at 4.0.0.2566 so that's 4b. We upgraded staging today to 4c and filed a request to upgrade production.
Kind regards
Thanks for your prompt reply.
The production environment is at 4.0.0.2566 so that's 4b. We upgraded staging today to 4c and filed a request to upgrade production.
Kind regards
-
- Product Manager
- Posts: 8191
- Liked: 1322 times
- Joined: Feb 08, 2013 3:08 pm
- Full Name: Mike Resseler
- Location: Belgium
- Contact:
Re: Feature request: log 'Bad Request (400)' warnings and continue job.
Perfect!
Let us know if this solves your issue
Cheers
Mike
Let us know if this solves your issue
Cheers
Mike
-
- Service Provider
- Posts: 12
- Liked: 1 time
- Joined: Feb 05, 2020 3:10 pm
- Contact:
Re: Feature request: log 'Bad Request (400)' warnings and continue job.
Hi Mike,
We installed 4c yesterday and did a rerun of the job. The particular user is still having issues because of the 'virus' files.
The OneDrive job, with 339 objects processed processes 338 objects withing minutes and one user stalled the job for 12hours abd 38 minutes before ending with warning:
Processing OneDrive Name (https://tenantname-my.sharepoint.com/personal/username) finished with warning: Failed to backup item: /personal/username/Documents/Documents/path/to/file.eml, Item may have a virus reported by the virus scanner plug-in :: 12:38:29
Also the retry job is already taking almost 4 hours at this moment.
Kind regards,
We installed 4c yesterday and did a rerun of the job. The particular user is still having issues because of the 'virus' files.
The OneDrive job, with 339 objects processed processes 338 objects withing minutes and one user stalled the job for 12hours abd 38 minutes before ending with warning:
Processing OneDrive Name (https://tenantname-my.sharepoint.com/personal/username) finished with warning: Failed to backup item: /personal/username/Documents/Documents/path/to/file.eml, Item may have a virus reported by the virus scanner plug-in :: 12:38:29
Also the retry job is already taking almost 4 hours at this moment.
Kind regards,
-
- Veeam Software
- Posts: 3195
- Liked: 774 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: Feature request: log 'Bad Request (400)' warnings and continue job.
@gvo91 ,
This certainly doesn't look normal and we'll escalate your case to RnD.
This certainly doesn't look normal and we'll escalate your case to RnD.
-
- Service Provider
- Posts: 12
- Liked: 1 time
- Joined: Feb 05, 2020 3:10 pm
- Contact:
Re: Feature request: log 'Bad Request (400)' warnings and continue job.
Hi Mike,
Thank you for escalating.
In the meantime i'm contacted by one of your support colleagues and uploaded the requested logs to the case.
FYI, the case number is 04233172.
Kind regards,
Thank you for escalating.
In the meantime i'm contacted by one of your support colleagues and uploaded the requested logs to the case.
FYI, the case number is 04233172.
Kind regards,
Who is online
Users browsing this forum: No registered users and 26 guests