BUG REPORT: Microsoft Exchange 2010 DAG backups fail with a status 26 or Microsoft Exchange 2010 standalone backups fail with a status 103.

  • Modified Date:
  • Article ID:000005583


BUG REPORT: Microsoft Exchange 2010 DAG backups fail with a status 26 or Microsoft Exchange 2010 standalone backups fail with a status 103.


Bug: 1955375

For an Exchange 2010 standalone backup attempt, the following message is logged in the Activity Monitor. (See the detailed status for the backup job.):

Critical bpbrm(pid=11304) from client ExchSrvr2010: FTL - snapshot preparation failed - Unable to determine Exchange version., status 103

For an Exchange 2010 DAG backup attempt, the following messages are logged in the Activity Monitor. (See the detailed status for the backup job.):

Error bpbrm(pid=20332) This type of backup is not supported on this version of Exchange
Error bpbrm(pid=20332) cannot run bpresolver or it failed on client  DAG2010001 Status 26

Messages similar to the following can be found in the bpcd log of the active/standalone client.

<2> process_requests: Not using VxSS authentication with DAG123.symantec.local
<2> process_requests: BPCD_GET_VERSION_RQST
<2> process_requests: BPCD_GET_EXCH_VERSION_RQST
<16> get_exch_version: ubsGetVersion failed: 11
<16> process_requests: bpcd get_exch_version failed: 11

On some Exchange 2010 servers, the following registry key exists, with no values for it:


This key was used for Exchange 2003 and 2007 installations and contained a value that indicated the Exchange version. For Exchange 2010, the registry key that contains the Exchange version is as follows:


NetBackup looks for the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Setup key on the Exchange 2010 server, but cannot locate the Exchange version value under the key.  NetBackup returns an error that indicates that it cannot determine the Exchange version.

If this condition is encountered, please contact Symantec technical support, referencing this document ID and Etrack 1955367 to obtain a fix for this issue.

A fix for this issue for NetBackup 7.0 can be obtained by accessing this TechFile:

The workaround for this issue is:
Remove the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Setup key from the Exchange 2010 server.

Note: Only perform this workaround on an Exchange 2010 server. Do not perform this workaround if any values exist within the registry key.
Warning: Incorrect use of the Windows registry editor can have disastrous results on a server operating system. 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 highly recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

ETA of Fix:
Symantec has acknowledged that the above mentioned issue (Etrack 1955375) is present in the current version(s) of the product(s) mentioned at the end of this article. Symantec is committed to product quality and satisfied customers. This issue was scheduled to be addressed in the following release:
  • NetBackup 7.0 Release Update 1 (7.0.1)
When NetBackup 7.0.1 is released, please visit the following link for download and readme information:

Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests or introduces new risks to overall code stability. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

*** Please also note that this fix is installed on the client -- the 2010 Exchange server and not on the Netbackup server(s). ***


Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)