adb with expired data still here

[giupri]

Dear all,
I am using Veeam for o365 since 2 years. Free space on repository disk is getting low. I set retention as 1 year.
It seems that management of adb files has still to be refined: I still have folder called "2016" with big adb file and its size decrease never. Same situation is for 2017 adb file (we are in 2018 and first 2017 months expired). Is already scheduled a new version with better management of repository?
Can I safely remove folder called "2016" where I have this big adb? Veeam Support suggested me to perform an ESEUTIL but it requires double space of adb file to run. Can I move this file to another machine and perform ESEUTIL from there?
Thank you in advance for your help.

[Mike Resseler]

Hi Guiseppe,

I haven't tested it out, so I would suggest to do the following:

Stop the veeam services. Copy the ADB to another location (that would mean the entire folder as we would need more than just the ADB file). Run the ESEUTIL and make it smaller, then copy it back and start the services. I would suggest though to keep a copy of the original in case something goes wrong.

And yes, you are correct that the shrinking is not done by us. Something we might need to look into

[giupri]

Thank you Mike for quick response! I will try and I will keep you posted.

[giupri]

Unfortunately Eseutil fails, this is error msg:
"Operation terminated with error -1504 (JET_errNullInvalid, Null not valid) after 36.859 seconds"

Performing Eseutil /g on the same adb it says "Integrity check completed. Database is CORRUPTED!" but it is the same even if I check ..\2018\repository.adb. Is it really possible ALL my adb are corrupted?

Note that I am trying to perform eseutil on Veeam server (so on a server without Exchange). Hence I followed instructions here at
https://support.microsoft.com/en-us/hel ... nge-server .
Consider that on my Exchange server 2010 I don't find 2 files mentioned so I am not able to move to Veeam server, they are: Jcb.dll, Exosal.dl . Maybe is here the problem?

Commands launched are:
eseutil /d D:\Backups\Office365\2016\repository.adb
eseutil /g D:\Backups\Office365\2016\repository.adb

Thank you in advance for your support.

[giupri]

I have another Exchange but with 2007 version so I copied into another directory of Veeam server these files:
Eseutil.exe, Ese.dll, Jcb.dll, and Exchmem.dll

Even so there is a problem, this is error msg I receive:
Operation terminated with error -1213 (JET_errPageSizeMismatch, The database page size does not match the engine) after 4.640 seconds.

So definitely it is not a problem of eseutil, problem is with adb files. How can I fix? I am still wondering how it is possible Veeam o365 create adb files without any way to handle directly with Veeam tools...

[Mike Resseler]

Hi Giuseppe,

You don't need the eseutil tools of Exchange, you need those of windows itself. (the versions are different). If you want to perform this procedure on a different server, make sure that server has the same OS as the one that holds your database (so proxy or VBO server).

Do note you need to copy more than just the ADB file, but all the other files in the folder also. It is the total of files that make up the database.

You should be able to find that eseutil under C:\windows\system32 or c:\windows\syswow64 but depending on your version it might be called esentutl.exe now (I can't test exactly as I have no server with me)
Do you have the possibility to try?

[giupri]

Hi Mike, thanks for reply. I just launched command as you suggested but nothing changed. This is output:
"
c:\Windows\SysWOW64>esentutl.exe /d D:\Backups\Office365\2016\repository.adb

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.3
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating DEFRAGMENTATION mode...
Database: D:\Backups\Office365\2016\repository.adb

Defragmentation Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
.................................................X



Operation terminated with error -1504 (JET_errNullInvalid, Null not valid) after
57.547 seconds.
"

[Mike Resseler]

Did you try it with the C:\windows\system32 version? (Just checking first)

[giupri]

Still same story:
"C:\Windows\System32>esentutl.exe /d D:\Backups\Office365\2016\repository.adb

Extensible Storage Engine Utilities for Microsoft(R) Windows(R)
Version 6.3
Copyright (C) Microsoft Corporation. All Rights Reserved.

Initiating DEFRAGMENTATION mode...
Database: D:\Backups\Office365\2016\repository.adb

Defragmentation Status (% complete)

0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
.................................................X



Operation terminated with error -1504 (JET_errNullInvalid, Null not valid) after
54.203 seconds.

"

[Mike Resseler]

Hmmm. Let me talk to my team and I will get back to you.

[giupri]

Mike, Vicktoriia of Veeam support called me and she discovered eseutil issue may be depends to these:
1- other Veeam services. On Veeam o365 server we have Veeam Backup too, So it is needed to stop other Veeam services (especially Veeam Backup Service and Veeam Mount Service need to be stopped).
2- Sophos . We added Veeam o365's repository in the exclusion list

In the meanwhile, browsing 2016 edb file with Veeam Explorer (I loaded manually) I saw there were no mail there so I deleted directly.

If possibile, in the next future, I ask to Veeam o365 developer team to add shrinking feature of edb file directly from Veeam o365. It has no sense to have big edb file with all mails removed logically only. It requires a lot of space for nothing.

Thank you for your support.

[Mike Resseler]

Giuseppe,

It is on our list, but it won't make the next version I'm afraid. We are already on feature lock for the next version. But definitely on our list

Cheers
Mike

[SamiE]

Hi,

Sorry to raise this old thread but do we still have to manually shrink the repository.adb files manually or does VBO shrink them automatically now (VBO 5.*)?

[Polina]

Hi Sami,

There're no changes in v5, and they are not foreseen in v6. You still need to do it manually.

[weeam]

Hello,

I have the same issue with error code "-1504 (JET_errNullInvalid, Null not valid)".

Any idea?

Veeam case 05495317

Thank you for your support.