Microsoft Knowledge Base Email Alertz

You receive an 0x800423f0 error message when you perform system state backups on the passive node of Windows Server 2008-based Exchange Server 2007 CCR clusters

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 977179 - Last Review: September 11, 2010 - Revision: 1.1

You receive an "0x800423f0" error message when you perform system state backups on the passive node of Windows Server 2008-based Exchange Server 2007 CCR clusters

SYMPTOMS

In a Windows Server 2008-based Exchange Server 2007 Cluster Continuous Replication (CCR) clusters environment, the log file path for the storage groups points to the root of a mount point. When you try to perform system state backups on the passive node of the CCR clusters, you receive the following error message:

"Backup of System State failed [Date Time]
Log of files successfully backed up
'<path of Log-File>'
Log of files for which backup failed
'<path of Log-File>'
Failure in a Volume Shadow Copy Service operation.
ERROR - Volume Shadow Copy Service operation error <0x800423f0> the shadow copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer."

After you receive this error message, you run the Vssadmin list writers command. Then, the Microsoft Exchange writer is in the following state:

"State: [8] Failed
Last error: Inconsistent shadow copy"

CAUSE

This problem occurs because the XML metadata that is created by the Exchange writer on the passive node of the CCR clusters differs from the metadata that the Windows Backup engine expects. If the file path for the log files points to the root of a mount point, the Windows Backup engine expects the physical path for the log files to end with a trailing backslash. However, Exchange Server 2007 writes the physical path information without a trailing backslash. Then, Exchange Server 2007 passes the physical path information to the Windows Backup engine.

RESOLUTION

To fix this problem, install the following update rollup:
979784  (http://kbalertz.com/Feedback.aspx?kbNumber=979784/ ) Description of Update Rollup 3 for Exchange Server 2007 Service Pack 2
After you apply this hotfix, you must restart the Exchange Server 2007 servers for the change take effect.

WORKAROUND

To work around this problem, follow these steps:
  1. Create a subdirectory in the root of the mount point that holds the log files for the storage groups.
  2. Reconfigure the CCR clusters so that the path of the log files for the storage groups points to the subdirectory.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about how to configure volume mount points on a server cluster in Windows Server 2008, visit the following Microsoft Web site:
How to configure volume mount points on a server cluster in Windows Server 2008 (http://kbalertz.com/Feedback.aspx?kbNumber=947021)

APPLIES TO
  • Microsoft Exchange Server 2007 Service Pack 2, when used with:
    • Microsoft Exchange Server 2007 Enterprise Edition
    • Microsoft Exchange Server 2007 Standard Edition
Keywords: 
kbclustering kbfix kbhotfixrollup kbsurveynew kbexpertiseinter kbqfe KB977179
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate