Passive database copy goes into suspended or failed state after restore on active database


When you restore an active database from a backup, the passive database might go into suspended or failed state if there is a lag between the replica and the active database. The state change can occur when the active database's log chain forks and begins a new branch which breaks replication.

Corrective action

Exchange Server will attempt to fix the replica, but if it is unable to do so, after restore, you can create a fresh backup, and then reseed the replica.