Manual Disaster Recovery of a Windows 2008 R2 Domain Controller fails with error "0xe000fed7 - A failure occurred performing custom restore”

  • Article ID:100027875
  • Modified Date:
  • Product(s):

Problem

Manual Disaster Recovery of a Windows server 2008 R2 Domain Controller fails with error "0xe000fed7 - A failure occurred performing custom restore”

Error Message

Error in the job log:

0xe000fed7 - A failure occurred performing custom restore operation

SGMON debug log show errors as below:

BEREMOTE:      [fsys\shadow]        - Informational: Creating Component 'BCD'
BEREMOTE:      [fsys\shadow]        - NTFS_GetBootDrive function failed to find the boot path: 0x57
BEREMOTE:      [fsys\shadow]        - Status FS_UNDEFINED_TYPE (0xE000FE18) setting the BCD restore path for Component BCD in SHADOW::PeformNt6PreCustomRestoreMethods
BEREMOTE:      [fsys\shadow]        - Status FS_CUSTOM_RESTORE_FAILURE (0xE000FED7) performing pre-restore custom methods for Component BCD in SHADOW::CreateComponent

Solution

Workaround:

Create following registry entry before running the restore:

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

key: HKLM\Software\veritas\Backup Exec For Windows\Backup Exec\Engine\NTFS
value: ForceBootDrive
type: REG_SZ
data: C:

It will override the default boot drive reported by NTFS_GetBootDrive() function.

Note:- Please replace "C:" with actual boot drive letter if different.

 

Veritas Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned at the end of this article. Veritas Corporation is committed to product quality and satisfied customers.
There are currently no plans to address this issue by way of a patch or hotfix in the current or previous versions of the software at the present time. This issue may be resolved in a future major revision of the software at a later time. However, this particular issue is not currently scheduled for any release.  If you feel this issue has a direct business impact for you and your continued use of the product, please contact your Veritas Sales representative or the Veritas Sales group to discuss these concerns.  For information on how to contact Veritas Sales, please see
www.veritas.com 

Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here.

 

 

Was this content helpful?

Get Support