resync error JetError -1069, JET_errVersionStoreOutOfMemory

[AlexL]

When adding an existing object repository I get an error message, this is for multiple object repositories. The errors come not immediately but after 30 min to a few hours.

for example:
Unable to access repository (C:\ObjectRepo02\PersistentCache\repository.adb) JetError -1069, JET_errVersionStoreOutOfMemory, Version store out of memory (cleanup already attempted)

This is NOT a physical memory issue, the server has 48GB memory and monitoring shows that there is 20GB or 30GB memory free or even more than 40GB after services have been restarted.

If I google for Jet / ESE and the above error message I find there is mention increasing a parameter MaxVerPages. I also find this mention of this parameter in the logs, apparently it's 8192. I have not found a way to increase this yet.

The eventviewer shows this:

ESENT eventid 623 ERROR
Veeam.Archiver.Proxy (8740,D,22) VEEAM_ARCHIVER_PROXY_c71bd0cc-0e24-4e08-bf12-5b5d2b8a2d3e: The version store for this instance (5) has reached its maximum size of 511Mb. It is likely that a long-running transaction is preventing cleanup of the version store and causing it to build up in size. Updates will be rejected until the long-running transaction has been completely committed or rolled back.

The object repositories are fairly large, 10 to 20k users per repo which roughly translates to 20 to 40k objects per repo.

I have a case open 07415056 but not much progression yet.

What happens is interesting, you add the repo, you need to resync because the persistentcache is non existent (or cleared after some testing), sync runs for a while, you get the above error, GUI shows invalid. When I try a restore, I get after a while either nothing or an error that data is missing. The cache size on disk is also much smaller than it was previously, like 5GB vs 50GB. But the invalid error under Backup Infrastructure on the repository somehow clears after a while, perhaps triggered by the restore?

Also, if I try to reuse the "old" persistant cache folder (copied from the old proxy), I get an error that it's in use and I cannot continue.

Anyone else seen this before? Any suggestions are very welcome.

[AlexL]

I'm using latest v7 build by the way.
Also, the message when reusing the old/previous persistant cache folder is this:

This object storage cannot be used with the specified local backup repository.
This backup repository is already synchronized with another object storage. Select another backup repository.

Perhaps if I got around that I'd also be good, might be worth a try but haven't found a way yet.

Anyone?

[dotdk]

Hi AlexL - Did you ever get this resolved? We are facing the same issue after adding an existing object repository.

We logged case 07468230 earlier today, but no resolution so far.

[AlexL]

If you have this exact error message, support will have some entries for you to add to the proxy.xml, this solved the sync issues for me but I still cannot restore because not mailboxes/metadata can be read properly, other errors, still working on that with support.

[dotdk]

I have the exact same error message, but still waiting for a resolution.

Could you perhaps share the entries with me? Perhaps in a PM so I can review.?

[Polina]

Hi All,

Thanks for sharing. I'll bring this issue to the attention of our RnD team to speed up the investigation.

[dotdk]

Hi Polina.

My issue has been resolved, repository problem resolved itself, but we were unable to browse any restore points. Support advised to start a "full* backup and the resolved the missing restore points.