Is it possible to merge old backup data?

[Espert]

We have recently had an issue where we were getting Jet-database blank-page error for multiple backup jobs on a single Proxy. We tried fixing the databases in question, but failed and instead made new Repositories for these tenants. Due to this error we were not able to restore anything from 2025. We contacted support, which were very helpful, but it took to much time and we made new repositories and kept the old ones available.

Seeing as several of these repositories were old and contained a lot of data 3 years back, and when we started a new repository, we lost some history.
We are using "Backup to local disk", and are thinking about switching to Object Storage, but have not had time yet.

Is there a way we can merge the old backups, with new repositories? The only folder/year with issues was 2025.

[Mildur]

Hi Espen,

Unfortunately, you cannot "merge" two repositories into a single repository. The only way to move backups to another repository is by using Move-VBOEntityData, which requires the target repository to be empty. Therefore, it can't be utilized in your situation.

Are you currently receiving any error messages when you attempt to add the old repository to the backup server for "only restore scenarios"?

Best,
Fabian

[Espert]

ok, I guess we will just have to keep them around a couple of years.

We have kept the old repositories connected to server for future restore, but if we try to restore from one of the accounts that has the "jet database blank page" error, it fails. I don't remember the specific message right now, but something in the line of database read error. We have tried to use Microsoft own tool to fix the database, but both soft and hard recovery fail. Soft recovery fails immediately, and hard recovery fails when we try to restore mail or files afterwards. A support guru at Veeam sent us a very easy to follow guide with esentutl.

We are able to open databases from a specific year where the error is not present, so all is not lost. It appears we had a server-issue beginning of 2025 with one of our proxies, which led to corrupt jet-databases for a lot of 365-accounts.