If you re-added the repositories you had previously and the Organization you should be able to restore again.  What version of VB365 are you working with?  I know it needs to index the repository when adding it so did that complete?

I’m working with Veeam Backup for Microsoft 365 Community Edition.

It should have completed the indexing.  Is there a way to check, or manually do the indexing?

If it did not complete you would see it in the tree where you add storage.  So CE edition but what version number?  7.x, 8.x?  That was what I meant by version.

Version 8.1.2.180 is what I am using

Ok.  Well if you added the same repos and indexing completed then you should have restore points.  I know it is hard getting support with CE edition but that might be the best route now.

Right-click on “Organization level” to see all the restore points of this organization.

Right-click on “Job level”, and you’ll only see restore points from this particular backup job.

Best,

Fabian

Mildur to the rescue as I forgot about this part.  

Thanks Fabian.

In the proxies it says the status is up to date.

I’m thinking now that the problem might be the hard drive itself.  I have nothing running on the drive except backups and when I check the status in task manager its clocking out at 95-100% usage and the read rate is only 5.4 MB and write is only a few hundred KB.

If I right-click at the organizational level, it still doesn’t allow me to look beyond yesterday.

read rate is only 5.4 MB and write is only a few hundred KB in Veeam that is.

That very well could be the problem.  Let us know how you get on and if you fix the issue.

Ensure that the steps you are performing are correct.

KB2649: How to Move Veeam Backup for Microsoft 365 to a New Server

So folks.  The short story is, putting in a new hard drive did not resolve the issue.  Basically what I have now is a mess of sub-repository folders.

I submitted a ticket yesterday.  Haven’t heard back from them yet.  I suspect it will be a while before I hear from Veeam.