Hi I have implemented Exchange 2007 in my customer environment. 3 node mailbox exchange 2007 ,2 node mailbox in Production as CCR, DR site as SCR. Everything working fine. Just curies when we doing Exchange 2007 fail-over from production to DR site. Database will fail under dirty shutdown Please let me whether dirty shutdown will always happen ,even its a planned DR activity? how to prevent this? what are the possibility ? when a database become dirty shutdown ? Regards Ramkumar.A

Please let me whether dirty shutdown will always happen ,even its a planned DR activity? No how to prevent this? Make sure network is healthy and replication is working fine. what are the possibility ? If their is any network or Hardware issue when a database become dirty shutdown ? When their is failure of Hardware, Network, Unexpected ShutdownGulab Prasad, gulab@exchangeranger.com My Blog | Z-Hire Employee Provisioning App

Please let me whether dirty shutdown will always happen ,even its a planned DR activity? No how to prevent this? Make sure network is healthy and replication is working fine. what are the possibility ? If their is any network or Hardware issue when a database become dirty shutdown ? When their is failure of Hardware, Network, Unexpected ShutdownGulab Prasad, gulab@exchangeranger.com My Blog | Z-Hire Employee Provisioning App

There can be many reseons for a dirty shutdown, it may be because of some curropted transaction logs, or can be because of failure is log shipping, or by network connectivity issue during log shipping in CCR failover/failback, this can also occur if somehow exchange is not able to replay logs properly to database. If a dirty shutdown occurs, in that case you have to recover entire database using eseutil, find more detail of recovery steps in below link http://social.technet.microsoft.com/Forums/zh/exchangesvradmin/thread/6be3b3fb-3eef-4739-b495-771bdc854f7b Prevention is on your hand only, have to validate network connectivity not more then 512 MS before any remote failover/failback, check for any disk issues etc.

There can be many reseons for a dirty shutdown, it may be because of some curropted transaction logs, or can be because of failure is log shipping, or by network connectivity issue during log shipping in CCR failover/failback, this can also occur if somehow exchange is not able to replay logs properly to database. If a dirty shutdown occurs, in that case you have to recover entire database using eseutil, find more detail of recovery steps in below link http://social.technet.microsoft.com/Forums/zh/exchangesvradmin/thread/6be3b3fb-3eef-4739-b495-771bdc854f7b Prevention is on your hand only, have to validate network connectivity not more then 512 MS before any remote failover/failback, check for any disk issues etc.

Hi Gulab Thanks for your response, please let me know Bandwidth recommended between production and DR site based on 700 users with Database size estimated 350 GB ,for Daily Replication and also SCR Seeding. Regards Ramkumar.A