ESEBackup: failure getting log and patch files: c8000232 - Some log or patch files are missing c8000230 - The database missed a previous full backup before the incremental backup <p>Symptom:</p> <div> <ul> <li>Exchange backup fails.</li> <li>You see something like the following error message in the Message Logs of the backup:
“FileIO JobId 1422: ESEBackup: failure getting log andamp; patch files: c8000232/Some log or patch files are missing.Error reading data header from FD. ERR=Connection reset by peer”</li> <li>OR”c8000230: The database missed a previous full backup before the incremental backup”</li> <li>OR”c800020e: An incremental backup cannot be performed when circular logging is enabled”</li> </ul> </div> <div> <div> Possible Causes: <ul> <li>Circular Logging is enabled. (This is specifically recommended to be disabled for Exchange 2010, but appears to cause issues when backing up other versions of Exchange as well.)</li> <li>Circular logging has been enabled in the past but has since been disabled.</li> <li>Another system is using VSS, backing up data and/or truncating logs.</li> <li>Transaction logs have been manually deleted.</li> </ul> </div> <div> </div> <div> Resolution: <ol> <li>Disable circular logging if enabled.</li> <li>Make sure you have disabled whatever else may be using VSS, backing up data and/or truncating logs.</li> <li>Perform a full exchange backup using NTbackup. This will rearrange the transaction logs making sure you will backup the correct ones in your next transaction log backup.</li> </ol> </div> <div> </div> <div> How to Disable Circular Logging for Exchange 2000/2003: </div> <div> http://support.microsoft.com/kb/314605
</div> <div> <ol> <li>Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager. </li> <li>If the Administrative Groups branch exists in the left pane, expand it, expand the appropriate administrative groups branch, expand the Servers branch, and then expand the appropriate servers branch.
If the Administrative Groups branch does not exist, expand the Servers branch in the left pane, and then expand the appropriate servers branch. To expand a branch, double-click the branch or click the plus sign (+) to the left of the branch. </li> <li>Right-click the storage group you want, and then click Properties. </li> <li>To disable circular logging, click to clear the Enable circular logging check box, and then click OK.</li> <li>5. Restart the information store. To do so: </li> <li>Click Start, point to Programs, point to Administrative Tools, and then click Services. </li> <li>Click Microsoft Exchange Information Store in the right pane, and then on the Action menu, click Restart. If a dialog box appears stating that additional services will be restarted, click Yes. </li> </ol> NOTE: The information store must be restarted because when it starts, it reads configuration information from Microsoft Windows 2000 Active Directory. The Active Directory attribute associated with the circular logging setting is called MSExchESEParamCircularLog. </div> <div> When circular logging is enabled, this attribute is set to 1. When circular logging is disabled, it is set to 0. </div> <div> </div> <div> How to disable Circular Logging For Exchange 2007: </div> <div> </div> <div> <ol> <li>Start the Exchange Management Console.</li> <li>In the console tree, expand Server Configuration, and then click Mailbox.</li> <li>In the work pane, right-click the storage group for which you want to enable or disable circular logging, and then click Properties. The Properties dialog box appears.</li> <li>Select or clear the Enable circular logging check box.</li> <li>Click OK.</li> <li>To make your changes to the circular logging settings effective, restart the Microsoft Exchange Information Store service, or dismount and then mount all of the databases in the storage group.</li> </ol>

How to Perform a Full Exchange Backup Using NTbackup on Exchange 2003: </div> <div> This will rearrange the transaction logs making sure you will backup the correct ones in your next transaction log backup. Please make sure all scheduled backups for this server are disabled while the NTbackup is running on this server. (Go to Clients > Edit. There is a dropdown for "Schedule" > Select [None])
<ul> <li>Click Start > Run, type NTBACKUP and click Ok. </li> <li>The backup/restore wizard appears. Click advanced mode on the welcome page. </li> <li>Click on the backup tab. </li> <li>On the backup tab expand server, expand [servername], expand information store and select the correct storage group or entire information store</li> <li>Select file as desttination, and name it so you can easily find and delete it later. </li> <li>Click start backup. </li> <li>This process will purge old transaction logs, making sure the errors above will be solved </li> </ul> If you are able to get a successful backup via NTBackup, you should be able to get a backup via the CFA. It is recommended to get a Full backup immediately following the successful NTBackup.
</div> </div> <div> How to Perform a Full Exchange Backup Using NTbackup on Exchange 2007: </div> <div> This will rearrange the transaction logs making sure you will backup the correct ones in your next transaction log backup. Please make sure all scheduled backups for this server are disabled while the NTbackup is running on this server. (Go to Clients > Edit. There is a dropdown for "Schedule" > Select [None]) </div> <div> <ul> <li>Click start > administrative tools > windows server backup.</li> <li>In the actions pane, click backup once. The backup once wizard will appear.</li> <li>On the backup options page, select different options and click next.</li> <li>On the select backup configuration page, select full server and click next. (Use custom if you want to select individual volumes).</li> <li>On the specify advanced options page, select VSS full backup, and then click next.</li> <li>On the Confirmation page, review the backup settings, and then click Backup.</li> <li>On the Backup progress page, you can view the status and progress of the backup operation. Click close when the backup operation has completed.</li> </ul> If you are able to get a successful backup via NTBackup, you should be able to get a backup via the CFA. It is recommended to get a Full backup immediately following the successful NTBackup. </div>