Direkt zum Inhalt

cannot restore Exchange (2019) DB from backup; fails with command failed/JET_errFileNotFound

Thread needs solution

I cannot restore anything (either Mailboxes or the whole Exchange DB) from any backup of my Exchange 2019 Server (on Windows 2019 std) using Acronis Agent for Exchange (Acronis Cyber Backup 12.5). The full error details are attached to this, and the short error is: 

Command has failed. Command=Recovering data; tenantID=00000000-0000-0000-0000-000000000000
Windows error: (0x8E5E0713) JET_errFileNotFound, File not found

I have tried re-installing the Agent, checking the Exchange DB integrity etc., and doing the back-up to different locations...nothing works;  There is nothing wrong with Exchange itself, and everything is performing normally. I have also upgraded the Exchange installation to CU8, but the problem existed before I did that (an original Exch 2019 installation). The Exchange DB is only about 1.7GB. 

When attempting to restore, Acronis can & does recognize the backup files, and I can select individual mailboxes to restore...however, both types of restore (either mailbox or entire DB) fail with the above error. 

There is nothing I can see in Acronis Knowledgebase remotely similar to this issue. 

Other Backups (e.g. of the local Hard drives C:, F:), and of a local network workstation (using the Workstation Agent) all work properly and I can restore from backups. 

I'm just posting here in case anyone can shed any light on this. 

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 0
Kommentare: 2016

Hello Jim,

Welcome to Acronis forums!

I have found similar issues in previously opened cases. Please try a workaround advised by our developers:

The workaround is to change TempPath in the registry as per https://kb.acronis.com/content/40040 and make sure the path does not contain mount points.
For example, you can assign a drive letter to the volume ARCHIVE, then change the TempPath so it's, e.g. X:\AcronisTemp instead of C:\ARCHIVE\AcronisTemp.

Thanks....this seems to have worked....though it is surprising, because the Server has more than enough (>90GB) of free space, so the default Temp directory (C:\ProgramData\Acronis\Temp) should have been fine to use.   

I did have one further minor problem when testing the workaround....but this was an InternalURL config issue on the Exchange Web Services IIS Virtual Directory. The problem was solved (accordintg to https://kb.acronis.com/content/65653) by correcting to the true InternalURL, and not using the External FQDN of the Exchange Server. 

thank you again 

 

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 0
Kommentare: 2016

Hello Jim,

thank you for sharing the outcome and your user experience with other forum users!