Skip to main content
Question

Agent backup is started failing after cancellation from VBR. error "Job finished unexpectedly"

  • April 9, 2026
  • 3 comments
  • 20 views
D

Hello Expert, I am getting below error during windows agent backup. Basically job was in hung stat on VBR so i stopped the job and restarted the services on agent servers. we tried to recover the backup but its failed with error "Job unexpected failed" in error log i could see below error. These nodes backup was running fine since last few years. Since this node belongs to DB we cant reboot it. Any suggestion or guidance is highly appreciated.

Info (3)    [RPC] RPC confirm session has been created. Id: {7a87b}
Info (3)    [RPC] Destroying RPC confirm session. Id: {7a87b}
Info (3)    [RPC] RPC confirm session has been created. Id: {52fb05}
Info (3)    [RPC] Destroying RPC confirm session. Id: {52fb05}
Info (3)    [RPC] RPC confirm session has been created. Id: {898fab}
Info (3)    [RPC] RPC confirm session has been created. Id: {0fc04}
Info (3)    [RPC] Destroying RPC confirm session. Id: {0fc04}

      3 comments

      coolsport00
      Forum|alt.badge.img+22
      • coolsport00
      • Veeam Legend
      • April 9, 2026

      Hi ​@dkumar - Welcome to the Community!

      Keep in mind, this site isn’t “official” Veeam Support. As such, we always recommend contacting Support and opening a case for any issues encountered.

      That said, I was going to suggest looking at logs on the Veeam server, but it looks like you’ve looked at the Logs as you’ve shared some snippets. It’s best to speak with Support on what your RPC statements mean, if in fact those are the core of your issue.

      Best.

      Shane Williford - Veeam VMCA/VMCE | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
        Chris.Childerhose
        Forum|alt.badge.img+21

        Some other tips when posting -

        • Post the Veeam version numbers
        • Post OS details
        • Check the logs (which you did) - C:\ProgramData\Veeam\Backup
        • What is the process you are doing - backup, agent backup, replication, etc.
        • Any other details or messages

        Like Shane said this is not “technical support” here so we may end up telling you to open a support case, but that is not because we don’t want to help, just that we have given suggestions and the problem is now beyond our means of helping.

         
         
         
        Chris Childerhose (Enterprise Architect) - VMCA | VMCE | VMCE-SP | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 7* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
          eblack
          Forum|alt.badge.img+2
          • eblack
          • Influencer
          • April 10, 2026

          When you killed a hung job and restarted the agent services, the previous session didn't clean up properly. I’m willing to bet its a VSS/shadow issue. 

          You can look for failures by using a cmd prompt on the agent box. 

          vssadmin list shadows

          vssadmin list writers

          Look for anything Veeam owned and failed out. 

          You can restart vss writers and remove orphaned shadows but I’d agree with the others that Support should be engaged if you haven’t done this before. 

           

           

           

           

           

            Terms & ConditionsAccessibility statement