Export Running for hours with no data processed

[Shocker]

Hi everyone

Just wanted to ask if anyone else has come across this.

We recently upgraded our Veeam backup for Microsoft office 365 community edition to version 3.0.0.422 and with the help of this forum as well we requested the DLL to fix the checking error. From we have upgraded when we try to run an export it just runs for hours and hours with no processing data and nothing transferred. When you try to stop the process it doesn't work until you stop the service but I don't see what is wrong at the moment and wondered if anyone else has come across this before?

[nielsengelen]

I would suggest contacting support to see if this is a known issue or if there is something else wrong causing this.

[Polina]

Aaron,

Which exactly "checking" error was it?

If you decide to go with the support case, please share its ID here, so that we could follow it up.

Thanks!

[Shocker]

thank you for the replies I will log a call with support now.

[Shocker]

it looks to sit in Operation Pending until I go into the Backup Infrastructure and then Backup Proxies and edit the proxy (make no changes) just edit and save then the job starts or changes to running but never actually does anything.

[Shocker]

Case number is #03728245

[Shocker]

so just to follow up on this it looks to be a problem with the backup proxy being itself (which didn't seem to be an issue before) I have just added another backup proxy and the job started first time.

[Polina]

Hi Aaron,

I moved your latest post to this thread, as it seems to fit the topic, right?
I'm glad that your problem is now resolved, though please continue working with support engineers to investigate the root cause.

And thank you for the updates on this!

[infused]

Just posting to this as I've found this an issue. It appears that Sharepoint jobs use all the available threads, so when starting new jobs it will sit as pending until threads become available. Increasing the threads will solve the issue.

[Mike Resseler]

Infused, just to be sure, so a sharepoint job was running at the time of restore?