Unable to apply KB4704

[matteu]

Hello,

I need to apply this KB : https://www.veeam.com/kb4704

However, the cmdlet Test-VBORepository doesn't exist when I try to execute it.
I tried it on my lab and I have the same issue. The cmdlet doesn't exist anymore. How to do because it's in the documentation : https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80 ?

Case : 07632024

[DaStivi]

hi, are you on of the fixed versions above 8.0.4.29 ? and are you running the command on the vb365 server?

[matteu]

I'm on the last version and I'm running the command on the all in one vb365 server yes.
I'm affected because I'm in this situation : If at any point during the Veeam Backup for Microsoft 365 deployment history it was running version 7 or 7a (builds 7.x) and subsequently upgraded to 8.0.2.159, 8.0.2.200, 8.0.3.1044, or 8.0.3.1073, it is affected, even if later upgraded to 8.0.4.29 or higher.

[DaStivi]

and the command isn't available at all? or just errors because parameter issues?
what does "get-command *vbo*" list you as available commands?

[matteu]

OK I understand the issue...
I'm on the last version when I use the menu -> upgrade but this doesn't install the latest one...
I'm on 8.0.5 and not 8.1.X
I'm installing the latest one with the ISO now and I guess it will work

Why doesn't install the latest version with Upgrade menu ? It should right ?

[matteu]

So after update the cmdlet is working except for 1 repository I have a timeout.
I will continue with support to know how to help about it !

[matteu]

And the other issue is after applying a full on the backup, the result of test-vborepository is exactly the same... It says there are issues. Is it normal ?

[DaStivi]

i would guess even after running a full, (and maybe changing the settings in proxy xml and restart of proxy service) the repo is still flaged as "issue" because there is still the problematic restore points in there... its just fixed for future.

only running full fixes the issue for the restorepoints after that... but without the modification (<RepositoryConfig SPJetMissingParentItemsInRoot="true" />) you don't see the files that where affected by the bug in older restore points... hence it might make sense the repo is flagged with issue as long as there are restorepoints that have the bug, but please let my assumption be checked by support

[matteu]

It's what I guess too but I prefer also to have a confirmation
The other issue is the timeout I get for 1 repository :/
It's the repository containing all my sharepoints sites + teams !

[Polina]

Hi All,

1) You've spotted it - to use the cmdlet you need to be on v8.1 (builds 8.1.0.305 - 8.1.0.3503)

2)

Why doesn't install the latest version with Upgrade menu ? It should right ?

There was an issue with this auto update which was fixed only in one of the 8.1 patches. Because of this issue we were unable to send the information about newer available versions via the wizard. For the future, to be notified of the new versions and patches, you can subscribe to this thread on the forums and this KB - they are always updated on the day of the release.

3)

even after running a full, (and maybe changing the settings in proxy xml and restart of proxy service) the repo is still flaged as "issue" because there is still the problematic restore points in there

In such a case, please open a ticket with support to investigate it.

Thanks!

[matteu]

1) it couod be better to mention 8.1 instead of 8 in the kb.

2) ok good to know it

3) I m waiting the support answer about it.

[voksys-hastik]

Hi, I just want to assure you, that you are not alone - we had all of your's problems as well:

-Missing command - figured out just by noticing last change date in help website where the command was described (It would be nice if Veeam would just add a note that the command is available only since certain version...) so it sparked to me that there could be a newer version.

-timeout when checking repo - support was not helpfull with this for me, it was failing for most of my repos - I figured that if the timeout occured, I need to run the backup job associated with the repo and after the job was done, then run the test-vborepository (sometimes it time outs again but on second / third run it does the check)

-errors still present after the full backup - yeah.. that's another ticket that I will close without resolution.. I've collected so many logs to provide enough information to solve that, but only what I get back is that they don't know if the full backup command is doing a full backup and they want me to waste more of my time on this. Mean time I've checked few of the repos myself and it seems that the errors are for the items that are no longer available so they can't be downloaded/backed up.

Just to add - what is worrying for me, that few of the repos that I scanned initially showed me no problems, but when I scanned them again for curiosity after a week, the showed missing items as well (of course that is after aplyng the latest patch).

I'm fed up with this product and support for it. We are charged and charging our clients only to find out that our backups are incomplete and we can't rely on them. What should I now say to our clients? "Hey, the backups that you are paying for, those are incomplete and missing some files that are no longer available - dont expect to restore those. But thank you for paying."

I'mo not looking for help, therefore I'm not submitting the support cases - I don't have the nerves, just wanted to say that @matteu is not alone, and point out possible problem and maybe a solution for the timeout problem.

[Polina]

@matteu
I guess you were looking at the KB header which only contains a major - 8 - version, right? We'll try to fix it and make it more clear that you need to be on a later build; thanks for noticing.

@voksys-hastik
I regret that your experience with VB365 was disappointing. I quickly checked the history of your support cases, but could not find any related to the issues that you mentioned above. May I still ask you to share the ID of that case? I would be interested to see the details and potentially get some learnings from it.

Thanks!

[matteu]

@Polina

Thanks for your answer.
Yes, I'm talking about the build of Veeam in the Header. It will be really more clear with the exact version needed

@voksys
To be honest, I'm experiencing the exact same situation .... More than 1 week and not really good advices to solve it until now. Just give me log, give me the proxy.xml file and the support engeneer need to search. Let see how much time it take to solve it and not have any error when the test-vborepository is executed

[voksys-hastik]

@matteu I think that the results from the test-vborepository won't be without error - if you are in the same situation as we are - I think that those errors after the fullBackup run are because of those items are no longer online (those are deleted in the M365).
My only fight right now is to get help from support (Case # 07640046) to obtain the list of affected items and then have some sort of closure ..

[matteu]

Hello,

Just to give some updates :
-The issue with the users was because the user was deleted in M365 so there is no new backup to fix it. I removed the backup data associated with this user and I don't have error for the Onedrive job anymore.

-The issue with the timeout is not solved. The support engeneer said me it will be fixed in the next KB.

=> I installed the last KB 8.1.1.159 P20250328 now and the issue is not fixed. I have the timeout issue.

Can someone on Veeam team can say me when it will be fixed please ?

[Polina]

Hi @matteu

The timeline for the next update is not known yet - we have just rolled out a patch this week.
If timeouts get resolved, you will receive a private fix.

[matteu]

He said me on the next patch before this one comes so I believed it was on this one but no

I don't think I will have a private fix because I ask him to close the ticket when he said me on the next patch it will be fixed !

[Polina]

You can re-open your ticket, that's perfectly possible.
Will you please remind me its ID?

[matteu]

It s on my first message
07632024

[Polina]

Hm... Actually, I connected the dots now - apologies for my misleading response above.

The latest 8.1.1.159 indeed includes the following fix:

Data move from a Jet-based Repository to an Object Storage Repository using the script provided in the KB3067 may fail with the error:
Exception of type 'System.OutOfMemoryException' was thrown.

If it doesn't work for you, RnD has to check it again.
Please re-open the case, or create a new one, provide your logs and share your case ID here. I'll ensure it is escalated to RnD for further investigation.

[matteu]

I just reopened the case and attach the advanced logs