EDIT: This post was updated on 4/29/2008 to add more detail about the Exchange-aware backup on next version of SBS.
In a previous blog post, we wrote about the various versions of Exchange Server and...
Updated Jul 01, 2019
Version 2.0
Blog Post
We are having a panic attack about this over in ars. This is the fail safe software we use when all else fails and exchange needs to be backed up.
Example: Say an Exchange aware backup failed and mail filled the disk array that held the stream. Normally we'd be able do a quick NT backup of the store files to write out to the disk array holding the database. Now with this lovely removal of exchange aware NTbackup we have to first move the stream data from the array to a secondary attached disk (after of course installing a secondary external scsi array) (even if we have one) and then run a backup on that then move the setup back. That more then doubles recovery time of the exchange server and adds DOWNTIME. Who's the rocket scientist who suggested it was worth it to drop this feature from development?
Example: Say an Exchange aware backup failed and mail filled the disk array that held the stream. Normally we'd be able do a quick NT backup of the store files to write out to the disk array holding the database. Now with this lovely removal of exchange aware NTbackup we have to first move the stream data from the array to a secondary attached disk (after of course installing a secondary external scsi array) (even if we have one) and then run a backup on that then move the setup back. That more then doubles recovery time of the exchange server and adds DOWNTIME. Who's the rocket scientist who suggested it was worth it to drop this feature from development?