Cannot Find or Open Application Databases During Object Recovery

Product version: 11.2

Last modified: 17 August 2026

Problem

When you recover objects of Microsoft Active Directory, Microsoft Exchange, or Microsoft SQL Server with NAKIVO Backup & Replication, the Objects step of the object recovery wizard fails in one of the following ways:

The database scan finds no databases, and the following error message is displayed:

No application databases were found

Alternatively, the scan finds the databases, but they cannot be opened. For Microsoft Active Directory, the error message is "Cannot mount Microsoft Active Directory Instance". For Microsoft Exchange, it is "The database cannot be opened" with the following line in the error details:

Operation terminated with error -1022 (JET_errDiskIO, Disk IO error).

In addition, the Event Viewer on the recovery server contains iScsiPrt errors similar to the following:

Target did not respond in time for a SCSI request. The CDB is given in the dump data.

Target failed to respond in time to a Task Management request.

Cannot reset the target or LUN. Will attempt session recovery.

Background

During object recovery, NAKIVO Backup & Replication attaches the disks from the selected recovery point to the recovery server via iSCSI and scans them for application databases. If the Backup Repository is located on slow storage, for example, a deduplication appliance, read requests to the attached disks can take longer than the default Windows iSCSI and disk timeouts allow. In this case, Windows fails the pending read requests. As a result, the database scan ends without results, or the databases that were found cannot be opened and are reported as corrupt.

The error -1022 (JET_errDiskIO) indicates a failed read operation, not actual database corruption. The databases in the recovery point are intact. The possible causes listed in the Microsoft Active Directory error message, such as a busy TCP port 5000 or a running dsamain.exe utility, do not apply in this case either.

Solution

Increase the iSCSI and disk timeouts on the recovery server, that is, the machine selected as the recovery server in the Object Recovery Wizard:

  1. On the recovery server, open Registry Editor.

  2. Go to the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\NNNN\Parameters

    where NNNN is the 4-digit instance number corresponding to the Microsoft iSCSI Initiator driver, for example 0000.

  3. Set the MaxRequestHoldTime value to 1800 (decimal). This value sets the iSCSI request hold time in seconds.

  4. Go to the following registry key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Disk

  5. Set the TimeOutValue value to 600 (decimal). This value sets the disk I/O timeout in seconds.

  6. Restart the recovery server.

  7. Run the object recovery again.

Note

Increase both values. If you increase only MaxRequestHoldTime, the database scan succeeds, but Microsoft Active Directory and Microsoft Exchange databases can still fail to open with the error -1022 (JET_errDiskIO).

See Also