VBO explorer for Onedrive doesn't show any content

[Peejay62]

Hi,

In our VBO365 environment we make a backup for some onedrives. Item level retention, 3 years. We make a VBR backup of the system/repository on which this backup data resides. In another VBR only environment I perform a guest restore of this system/repository backup and then connect with the installed Explorer for Sharepoint/Onedrive and connect to a Veeam backup for MS365 database (*.adb running inside the veeamflr). This works well,the database gets mounted and the browser displays the onedrive information. But then, no content is displayed, only the onedrives root and underlying folders. No files appear, as it should. Is there something I am missing here or do I need some additional settings or whatever to have this working? I am sure that any data should be displayed because browsing on the VBO365 server does display data for the same adb file.

thanks

[Mildur]

Hi Peter

Was that for a user you have removed from the production environment? Or is every users OneDrive empty?
Do you also see empty folders if you use the VB365 server for the restore?

Also please open a case with our customer support team, if VB365 also doesn't show the content. Our customer support team can check your job and restore settings and the logs.
Please don't forget to provide the case number with us.

Best,
Fabian

[ACrispiels]

Same issue for me, with the latest release 8.0.3.
It is by chance that I discover it because there is no error message in the jobs.
It is very scary and makes you lose confidence in the product...
I will still do one or the other test but after I will open a case at the tech support because it is clearly too important to let this pass.

[Mildur]

Hi Alain

Please share the case number with me.
Unfortunately we never got one from Peter, so I can't verify if the issue has resolved for him.

Best,
Fabian

[ACrispiels]

I'll do that asap, Fabian.
First, I'm reinstalling from crash a new VBO server, making tests with two-three small organizations and after that I'll send a feed-back and the case number.
It takes some times to do that...
Currently, following my first investigations, no problem with Exchange.
For OneDrive, all the folders are present, but empty.
For Sharepoint, I'm afraid (but not yet 100% sure) it's like OneDrive...

[ACrispiels]

Backup tests with three small tenants were faster than expected since the contents of the folders are empty !!!
All is green, but it's empty.
Case id #07456768.
By the way, Fabian, it would be nice if there was a system equivalent to the Veeam B&R .bco file because it is cumbersome to have to reimport all the application id's and all the certificates to the new fresh server I just installed

[Mildur]

Thank you for the case number. I saw your comment in the case:

In fact, in the Veeam Explorer for OneDrive, I can still just see recent files. Recent means no more than one month.
PS. : the repository is item-level type with 33 days retention

With Item-Level retention, you only have files and folders protected that were created or modified in the last 33 days. Older items are removed from the backup repository according to this policy. If you want to protect an entire OneDrive, including all the data inside it, you need to use snapshot-based retention.

To me everything seems to be working as expected with the configured retention policy. Older data (creation time/last modification time older than 33 days) are not protected anymore, as specified by your retention policy. That's why you cannot see them.

Our retention policy types are explained in our help center:
https://helpcenter.veeam.com/docs/vbo36 ... tml?ver=80

By the way, Fabian, it would be nice if there was a system equivalent to the Veeam B&R .bco file because it is cumbersome to have to reimport all the application id's and all the certificates to the new fresh server I just installed

Yes, configuration backup is on our roadmap. We do have plans to introduce this feature in a future update. However, we cannot yet provide more information about an ETA or the expected version.

Best,
Fabian

[ACrispiels]

Thx for the .bco info.
For the repository file, sorry, misconfiguration from my side on the new server.
Jobs have now been reconfigured with snapshot-based repositories.
In the old VBO server (my prod server until this morning), all is snapshot-based and the problem is indeed present.

[Mildur]

Hi Alain

Thank you for the update.
From your most recent case notes, it appears that everything works as expected for the first two tenants on the new server. To check the third tenant, we need to wait for the initial backup to be completed.
Please continue to work with our customer support engineer to investigate why you can't see the protected files on your primary backup server.

Best,
Fabian

[ACrispiels]

Thank you Fabian.
Screenshots and logs have just been sent a few seconds ago.
So the comparison between both servers is easyer to understand.

[ACrispiels]

Because I'm afraid it will take time...
And because I can't stay without any backup.
I'm refocusing on the production server.
I'm deleting some jobs and some repositories.
I'm recreating them with the same parameters.
And once these backups are finished (this takes time because Microsoft voluntarily limits the flow rates), I can review and restore the contents with the OneDrive and SharePoint explorers.
Could it be an index problem in the repositories ?
I'll wait for a response from the engineer assigned to this case id #07456768 (Cesar or Hari ?).
In any case, Fabian, what is certain is that I must regain total confidence in the product because what I discovered at the beginning of the week scares me a lot.
I don't dare imagine if I have to restore something right now...

[ACrispiels]

In this forum, indeed, we unfortunately do not see the resolution for Peter.

In my case, I repeat, it was by chance that I discovered the problem because no error or warning message appeared anywhere.
And that is necessarily scary and it also makes you lose confidence in a strategic product.

@Fabian, I had the case id #07456768 closed because the various engineers (at least three !), in addition to being slow to react, brought me nothing except wasted time.
You can read all my comments there.
To move forward, alone, without the help of this support, I therefore deleted and recreated all the jobs and repositories, losing at the same time all the retentions and the possibility of analyzing possible corruptions (I suspected indexing problems but I did not have a reaction to this question).
I had no choice, I had to move forward after more than a week without backups.
So I am not at all reassured because 1) not knowing what happened and 2) how can I be sure that it will not happen again ?
Finally, hoping that this message will not be censored (…), it was the first time I think that I opened a severity 2 case, and I was clearly not taken seriously.