Veeam VSS Agent and PendingFileRenameOperations Registry Key

[ChuckS42]

One of my SharePoint admins tells me that her servers are in a pending-reboot state after a Veeam backup. It seems that the registry key "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager| PendingFileRenameOperations" is being set with one or more instances of "\??\C:\Windows\system32\config\SYSTEM.{76084AB0-E15A-44A4-8E9E-1B8D82698635}". I can't track this GUID down so I don't know for sure, but the timing of the key being written/updated corresponds with the start of a Veeam backup job, when the VSS agent is installed. I have seen this on multiple servers, not just SharePoint. I suspect this is normal and harmless, and not indicative of an actual pending reboot. Anyone else see this?

[csydas]

Hey Chuck,

Had something similar once, turns out it was just that there was something that had a pending reboot after the file-name was updated. I forget the full explanation, but more or less the VSS service triggered it.

I think it was this powershell script that showed us what was up: https://gallery.technet.microsoft.com/s ... y-bdb79542

Does that help out?

The pending rename stuff isn't super important, and you can just stall until it's at a natural maintenance window for this VM.

[ChuckS42]

Yah, I don't see it as a problem, just an oddity. And I don't think its something else - the key is multi-string, and a new iteration of the same file gets added to the list every night, and it accumulates until the server is rebooted. Very odd.

[ChuckS42]

Veeam support (case 02719214) validated that this is actually the adding/removing of the Veeam VSS agent that's writing the keys. Generally safe to ignore (though you may need to reboot the server before installing something that checks this key).

[sandsturm]

Hi

We experience the same issue for our exchange servers, we see the "Pending reboot" message after each daily backup. We created a supportcase with veeam (Case # 05585174) and learned that this is a known and designed behavior of Veeam. Our Exchange server admins are quite unhappy, that they see this message every day after each backup. It cannot be, that a daily backup is the reason for a reboot of as server, I'm sorry! Can you think about that and maybe redesign this process, please?

thx
sandsturm

[Brad-Translucent]

I am now seeing this with the infrastructure I manage. I have been chasing my tail wondering why all these servers that I just restarted are showing a reboot required the next day. I too cannot understand why this is "by design".

[PetrM]

Hi Brad,

I think you should let our support engineers analyze this behavior, if it is by design, we'll add a corresponding note to our help center. Please share a support case ID for our reference.

Thanks!

[ChuckS42]

Kinda surprised this is still a thing.

[DFEX]

+1

[Sam62]

still ongoing..
Daily backup fails because of this.
We have a lot of customers and I need to restart at least 1-2 servers every second day.
Upgraded some Veeam to v12, we'll see if it continues there.

[PetrM]

Hello,

If the issue persists after upgrade to v12, please contact our support team and share a case ID, I'm still not sure that this is a behavior by design.

Thanks!

[Sam62]

The issue is only present in Veeam Agent and in backup type "windows agent backup" in B&R.
Can't remember ever having this problem with copy jobs or VMware Backups.

[TropicOasis]

This is still an issue after 5+ years and is currently happening during hourly backups to servers (physical and VM) for one of the largest applications at one of the largest auto manufacturers in the world! How has this not been fixed! We do have a case open and I'm escalating. We've asked Veeam to fix their agent before and now I hope they'll listen.

[PetrM]

Hi Adam,

May I ask you to share a support case ID?

Thanks!

[TropicOasis]

@PetrM

Case #06109085 — Potential Performance Issue.

[PetrM]

Hi Adam,

I requested an escalation of the support case. Let's see what our senior engineers can find out.

Thanks!