Skip to main content
Solved

Stuck Copy Job in Veeam Backup for Microsoft 365


I have a backup copy job for OneDrive that has been running for over 60 hrs. and I am attempting to stop the job.  I stopped it in the GUI however the job still shows running with a status of “Queued” and the details show “Operation pending”.  The job status has not changed for 30-60 minutes.  

 

I have also attempted to stop the copy job with the Veeam Backup for Microsoft 365 Powershell Toolkit but I am running into syntax errors.

Best answer by kristofpoppe

Try to stop the services and clear the NATS queue by deleting the contents of the streams folder. 

Default location of the folder is "C:\ProgramData\Veeam\Backup365\nats\jetstream\$G"

View original
Did this topic help you find an answer to your question?

8 comments

Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8518 comments
  • February 13, 2025

Have you tried rebooting the server as well as the Proxy server (if not the VB365 itself)?  This tends to kill the jobs.


kristofpoppe
Forum|alt.badge.img+10
  • Veeam Vanguard
  • 118 comments
  • Answer
  • February 13, 2025

Try to stop the services and clear the NATS queue by deleting the contents of the streams folder. 

Default location of the folder is "C:\ProgramData\Veeam\Backup365\nats\jetstream\$G"


  • Author
  • Not a newbie anymore
  • 3 comments
  • February 13, 2025

Yes, I have rebooted the server (server/proxy server) and the job is still showing running.  I will try deleting the contents of the streams directory.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8518 comments
  • February 13, 2025
gcits4424 wrote:

Yes, I have rebooted the server (server/proxy server) and the job is still showing running.  I will try deleting the contents of the streams directory.

This is applicable if you are on v8 of VB365 otherwise you will not find the directory.  I assume you are on v8.  If that fails then you may need to contact support to get assistance.


  • Author
  • Not a newbie anymore
  • 3 comments
  • February 13, 2025

Deleting the contents of the streams directory worked.  Thank you.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8518 comments
  • February 13, 2025

Glad to hear you fixed the issue.  Nice that everything is much easier in v8.  😎

 
 
 

kristofpoppe
Forum|alt.badge.img+10
  • Veeam Vanguard
  • 118 comments
  • February 13, 2025
gcits4424 wrote:

Deleting the contents of the streams directory worked.  Thank you.

Good to hear this worked out !


  • New Here
  • 1 comment
  • March 25, 2025

This worked for me as well. Veeam support worked on this for 3 weeks and couldn’t resolve the issue. Thank you!!!


Comment