There is also Exchange server clustering that provides another method for failover; however, it is not able to...
prevent logical corruption.
The ESE backup API, when running on Exchange 2003 and Windows 2003, provides new functionality in VSS (Volume Shadow Copy Services).
"The Volume Shadow Copy service coordinates communication between Requestors (backup applications), Writers (applications in Windows services like Exchange Server 2003, and SQL Server 2000), and Providers (system, software or hardware components that create the shadow copies). To use the Volume Shadow Copy service feature to backup Exchange Server 2003, the backup program must include an Exchange Server 2003 aware Volume Shadow Copy service requestor. Because the backup program that is bundled with Windows Server has no such requestor, organizations must use third-party backup applications."
These VSS hardware and software requestors can provide the appropriate calls to create an Exchange consumable snapshot, as it was properly quiesced, and move the data appropriately. For more information see KB article 822896. .
Bottom line: Without the use of this API, there is no Microsoft supported way of moving the file-level data safely. Be wary of third mirror break-off solutions that do not utilize the aforementioned technology. These would provide data that is application-inconsistent and would require both physical (ESEUTIL) and logical (ISINTEG) repair prior to use, and cannot guarantee data preservation.
Do you have comments on this Ask the Expert Q&A? Let us know.
More information from SearchExchange.com:
Dig Deeper on Microsoft Exchange Server Backup and Disaster Recovery
Related Q&A from SearchExchange Staff
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.