Public Folder Backup Hangs

[Celine]

Hello,
we've got an issue with public folder backups, which hangs and don't complete.
We've got a veeam case (Case #07377218 and Case #07346656) and the support sent us following knowledge base article: https://www.veeam.com/kb4577
It says that we need to change the "PerUserReadStateEnabled" Value to "False".
We did this for one of our customers but this has affect for our customer! When one person clicked on an E-Mail it is displayed for everyone as readed.
This is a big problem for our customer.
We needed to change the value back for this customer.

So Veean Support told us : only if this vaule is false the backup is working. We really need to fix this without changing the attribute in Exchange Online.
Anyone out there facing the same issue? and has a better solution for this issue?

Thank you!
Kind Regards,
Celine

[Polina]

Hi Celine,

Unfortunately, Veeam cannot change or fix this, and there're no other workarounds.
I'm sorry for the inconvenience with your customer, however, you may notice that the downside of the attribute change is highlighted in the KB.

[t7MevELx0]

Veeam Case #07379532
Veeam Case #07341926

Is there a hotfix being worked on for this issue? We are an MSP and I keep seeing clients with this issue. It would be best to have a solution from Microsoft/Veeam that doesn't involve having the client run scripts before backups work.

KB:
https://www.veeam.com/kb4577



Thanks!

[Mildur]

Hello t7MevELx0

Please see Polina's comment in this topic.

Best,
Fabian

[t7MevELx0]

Does anyone know why it just now started breaking and only for certain clients? The Microsoft KB article states "This is a known issue that affects read receipts from public folders. Microsoft is researching this problem and will post more information in this article when the information becomes available."

That Microsoft article was written back in January.

Does Veeam have a working relationship with Microsoft?

I've started to ask my clients to open tickets with Microsoft support.

[eikee]

Upvote on a fix by Veeam&Microsoft. Not a year is gone since veeam-backup-for-microsoft-365-f47/publ ... 13-60.html was fixed and again backup of PF is broken. Please get in touch with MS and work on a solution, changing the PerUserReadState is not an applicable fix for all customers.

[svenheu]

Hi,

It looks like data is being transferred before the job hangs. Is there a way to identify the affected public folder and adjust only that one?

[t7MevELx0]

This issue is happening on multiple clients. I would suggest Veeam R&D reach out to Microsoft to fix this issue before it balloons.

One of my clients deleted their public folders to try and resolve this issue. They still have the issue even without public folders. It's happening on a shared mailbox now.

[fractalenergy]

+1 for that request. I know there a way to change the PerUserReadStateEnabled for all public folder, but for many customer it's hundred/thousand of folder which take forever to run the script. There is a way to make backup works correctly with Microsoft help on your side.

Thnx

[fra1198s]

I also have a customer with a lots of public folders and they rely on the individual read state of the folder for the workflow processes
If this permission is really necessary to be false in such scenarios, could this not be done by the Veeam software during the backup job: check the peruserreadstate status, temporarily change it if required and then change it back again?
Is there some change in version 8?

[AlexACS]

+1 please

[Polina]

@t7MevELx0, Veeam is already in contact with Microsoft, but unfortunately, this doesn't help resolve the inconvenience with PFs protection. We do our best to allow the protection of these legacy folders for as long as it's technically possible.

@fra1198s, silently changing the setting even for a short while may (and will) result in significant consequences for many customers. And on top of that, let's not forget that sometimes jobs run for hours, or even days in case of first full backups.

[chumkeeves]

I encountered this issue for the first time today after upgrading yesterday from 7.1.0.2031 to 8.1.

The steps in the kb were no problem for me to implement, and doing so resolved the issue, however I find it strange that the issue (from my perspective at least) was introduced by a change in Veeam code, as I'm unsure what would have changed at the same time on the Microsoft side.

[karsten123]

I had problems with the script because folder names weren’t unique.
I changed it to compare identity instead. cheers

[eikee]

For me, the issue seems to be fixed upgrading from 7.x to 8.1.1.159. I did find nothing in the change log, is there any information on that?

[Mildur]

Hi Eikee,

Unfortunately, we cannot verify your specific situation without the case number and a confirmed bug ID. Upgrading from version 7.x to 8.1.1.159 is a significant step involving an architectural redesign of the product and hundreds of fixed issues, and we don't list every single bug fix in our release notes.

Regarding the "PerUserReadStateEnabled" workaround mentioned in KB4577, our internal notes indicate that it is still required if the backup of public folders is failing.

Best,
Fabian

[eikee]

The case numbers were #07377524 and #07390431 and the public folder backup is working again without "PerUserReadStateEnabled" workaround mentioned in KB4577.