How to Perform Dial Tone Recovery in Exchange Server

How to Perform Dial Tone Recovery in Exchange Server

Exchange, Exchange Server SE / 2019 / 2016, High Availability
Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 Dial tone recovery is an Exchange Server recovery method that gives users temporary mailboxes so they can continue sending and receiving email while the original mailbox database is being restored. The original version of this article was written for Exchange Server 2010 with Windows Server Backup. Microsoft still documents dial tone recovery for Exchange Server Subscription Edition, Exchange Server 2019, and Exchange Server 2016. The recovery concept is the same, although the current procedure is based on Exchange Management Shell, a dial tone database, a Recovery Database, and mailbox restore requests. In This Article 1. What Is Dial Tone Recovery? 2. Dial Tone Recovery Process 3. Same Server or Alternate Server 4. Recovery Database and Data Merge…
Read More
Restore an Exchange Server Mailbox to a Different Mailbox Using a Recovery Database

Restore an Exchange Server Mailbox to a Different Mailbox Using a Recovery Database

Exchange, Exchange Server SE / 2019 / 2016, High Availability
Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 Exchange Server supports Recovery Databases (RDBs) for restoring mailbox data from a recovered database without interrupting access to the active mailbox database. This applies to Exchange Server Subscription Edition, Exchange Server 2019, and Exchange Server 2016. One useful scenario is restoring the contents of an old mailbox into a different existing mailbox. The recovered database is mounted as an RDB, the source mailbox is identified by its mailbox GUID, and New-MailboxRestoreRequest copies the data into the target mailbox. In This Article 1. What Is a Recovery Database? 2. Prepare the Restored Database 3. Create the Recovery Database 4. Mount and Check the Recovery Database 5. Restore the Mailbox to a Different Mailbox 6. Monitor the Restore and…
Read More

How to Restore Mailbox Data from an Exchange Recovery Database

Exchange, Exchange Server SE / 2019 / 2016, High Availability
Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 Exchange Server uses a Recovery Database (RDB) to mount a restored mailbox database and recover mailbox data without disrupting the production database. After the restored database is mounted as an RDB, New-MailboxRestoreRequest can merge mailbox data into an existing mailbox. The original version of this article demonstrated the process on Exchange Server 2010 with Windows Server Backup. The same Recovery Database concept continues in current Exchange Server releases, although the backup and recovery workflow has evolved. In This Article 1. How Recovery Databases Work 2. Restore the Exchange Database 3. Prepare the Restored Database 4. Create and Mount the Recovery Database 5. Restore Mailbox Data 6. Key Takeaways 1. How Recovery Databases Work Exchange 2003 and Exchange…
Read More

How to Block Automatic Database Activation on an Exchange DAG Member

Exchange, Exchange Server SE / 2019 / 2016, High Availability
Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 In an Exchange Database Availability Group (DAG), you can prevent a Mailbox server from being selected for automatic database activation. This is useful when a DAG member should keep passive database copies but should not automatically host an active copy after a failure. The original version of this article described this as “manual failover.” A more accurate description is blocking automatic database activation on a DAG member. In This Article 1. Block Automatic Database Activation 2. What Blocked Does and Does Not Do 3. Allow Automatic Activation Again 4. Maintenance Mode Is Different 5. Key Takeaways 1. Block Automatic Database Activation To prevent database copies on a specific DAG member from being automatically activated, set the server-level…
Read More

How to Install Exchange Server Updates on DAG Members

Exchange, Exchange Server SE / 2019 / 2016, High Availability, Migration & Upgrade
Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 Exchange Server updates on a Database Availability Group (DAG) should be installed one member at a time. The main goal is to move active databases away from the server, prevent them from activating back during maintenance, install the update, and then return the server to production. The original version of this article was written for Exchange 2010 SP1 and used the term Update Rollup. Current Exchange Server servicing uses Cumulative Updates (CU), Security Updates (SU), and when required Hotfix Updates (HU). The DAG maintenance principle is still the same. In This Article 1. Before You Start 2. Put the DAG Member in Maintenance Mode 3. Install the Exchange Update 4. Return the Server to Production 5. Update…
Read More
How to Configure Local Continuous Replication (LCR) in Exchange Server 2007

How to Configure Local Continuous Replication (LCR) in Exchange Server 2007

Archive / Legacy Topics, Exchange, High Availability
Applies to: Exchange Server 2007 Historical: Local Continuous Replication (LCR) was an Exchange Server 2007 high-availability feature. It was removed in Exchange Server 2010 and replaced by the Database Availability Group (DAG) and mailbox database copy model. LCR creates a second copy of an Exchange 2007 storage group on the same Mailbox server. Transaction logs are copied and replayed into the replica database, providing a local recovery copy if the active database or storage fails. In This Article 1. What LCR Does 2. Configure Local Continuous Replication 3. Important Storage Considerations 4. What Replaced LCR 5. Key Takeaways 1. What LCR Does LCR is a single-server replication technology. It is enabled per storage group and uses Exchange log shipping to maintain a passive local copy of the databases in that…
Read More