ExChange databases not visible in backup explorer

[HansMeiser]

Hello,

we use Veeam 12.3.1.1139 on Windows Server 2019 datacenter.

We have a bunch of ExChange2016 servers, backup&restore works for years. Now we want to backup new 2022 Exchangeservers in a separat job. backup works also without problems, no warnings etc.
Testing an item-restore with new ExChangeservers currently not possible. we open the backup but in exchangebrowser none of the exchangedatabases is visible.

The restorejob itself results in a Warning:

Code: Select all

28.03.2025 11:38:28          Application item level restore started
28.03.2025 11:38:37          Mounting restore point to host: [Backupserver]
28.03.2025 11:39:01          VHD mounted as 'C:\VeeamFLR\ExChangeserver_80118e7a\Volume{1a74d547-3518-4bfb-97be-f96465cc18c0}'
28.03.2025 11:39:01          VHD mounted as 'C:\VeeamFLR\ExChangeserver_80118e7a\Volume{7fec9100-ece2-4de4-99c7-91809be413f9}'
28.03.2025 11:39:06          VHD mounted as 'C:\VeeamFLR\ExChangeserver_80118e7a\Volume{053a3155-8732-4193-b15b-dbeb26526135}'
28.03.2025 11:39:11 Warning    Failed to mount volume \\?\Volume{7f577ad1-01e9-4159-827c-45d18b1d4d42}\: The parameter is incorrect.

So it seems that the disc which is holding the ExChangedatabases can not mounted and is most likely the reason that we dont see any database.

We tried to restore entire VM and this was working.
So what may be the reason for this?

We checked that ExChangebrowser is able to use fitting ese.dll and that seems to be ok.

Code: Select all

[28.03.2025 12:05:07.246] 13 (24196) ESE.DLL path: C:\VeeamFLR\ExChangeserver_e16d8738\Volume{60c8b6c2-af9d-4f31-ba1e-ac041419cb4a}\Program Files\Microsoft\Exchange Server\V15\Bin

So may be we have a problem independent from ese.ddl.
My mate told me, that there may be a problem, when Refs is in use. Backupserver 2019 and New ExChangeserver 2022 may be incompatible in that way. So if this is true, ist there a workaround to run the backupbrowsers on a new server 2022 independent from backupserver?

What do you think?

Thanks,
Hans

[Mildur]

Hi Hans

If the Exchange Server runs on Server 2022 with reFS volumes, then your mount server and machine where backup console was started must also be on Server 2022 or later. Or Veeam Explorers will not be able to read jet databases on the protected reFS volumes.

You can try the restore your Exchange data with a remote backup console running on a Windows 2022 server (with all Microsoft patches installed). Or migrate your entire backup server to a Windows Server 2025 machine, if you like to start restores directly on the backup server.

Best,
Fabian

[HansMeiser]

Hello Fabian,

running backupconsole on a windows 2022 server without moving whole backupserver is an option for us. I did not know this is possible.
Thanks, i try to figure out how this installation can be performed.

Thanks,
Hans