Exchange Server SE / 2019 / 2016 Archives - Page 2 of 2

14Feb 2013 by Ceyhun Kirmizitas 0 Comments

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…

05Feb 2013 by Ceyhun Kirmizitas 0 Comments

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…

17Jan 2013 by Ceyhun Kirmizitas 0 Comments

Troubleshoot Exchange Replica Inconsistent Error 30146 in DPM

Exchange, Exchange Server SE / 2019 / 2016, System Center

Applies to: System Center Data Protection Manager 2025 / 2022 / 2019 | Exchange Server 2019 / 2016 / 2013 Data Protection Manager (DPM) can report an Exchange mailbox database replica as inconsistent when a consistency check fails. One common cause is a version mismatch between eseutil.exe and ese.dll on the Exchange server and the DPM server, especially after an Exchange update. Error ID 30146 is a general data consistency verification failure, so it should not automatically be treated as an Eseutil mismatch. Check the accompanying error details and event logs before applying the fix. In This Article 1. Symptom 2. Why the Eseutil Version Matters 3. Compare the File Versions 4. Update the Files on the DPM Server 5. Run the Consistency Check Again 6. Other Causes of Error…

18Dec 2012 by Ceyhun Kirmizitas 0 Comments

Moved Mailboxes Appear as Soft-Deleted After a Database Move in Exchange Server

Exchange, Exchange Server SE / 2019 / 2016, Migration & Upgrade

Applies to: Exchange Server SE / 2019 / 2016 After moving a mailbox to another mailbox database, you may still see the old mailbox on the source database with a SoftDeleted disconnect reason. This is expected behavior in Exchange Server, including Exchange Server Subscription Edition, Exchange Server 2019, and Exchange Server 2016. The mailbox on the source database is not another active copy of the user mailbox. Exchange keeps the source mailbox temporarily so that its data can still be used for recovery if something goes wrong after the move. In This Article 1. Why This Happens 2. Check Soft-Deleted Mailboxes 3. Check Mailbox Retention 4. Should You Delete It? 5. Permanently Purge a Soft-Deleted Mailbox 6. Key Takeaways 1. Why This Happens When a mailbox move between Exchange mailbox…

14Oct 2010 by Ceyhun Kirmizitas 0 Comments

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…

09Sep 2010 by Ceyhun Kirmizitas 0 Comments

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…

07May 2009 by Ceyhun Kirmizitas 0 Comments

Fix “No Site Name Is Available for This Machine” on Exchange Server

Active Directory, Exchange, Exchange Server SE / 2019 / 2016, Identity

Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 | Active Directory Domain Services When the Microsoft Exchange POP3 service cannot determine the Active Directory site for the server, it can fail with the following error: No site name is available for this machine. This is Windows error ERROR_NO_SITENAME (1919 / 0x77F). In most cases, the Exchange server IP subnet is missing from Active Directory Sites and Services or is mapped to the wrong AD site. In This Article 1. Check the Detected AD Site 2. Verify the Subnet in Active Directory Sites and Services 3. Correct the Subnet-to-Site Mapping 4. Validate the Fix 5. About the SiteName Registry Value 6. Key Takeaways 1. Check the Detected AD Site Run nltest /dsgetsite on the Exchange server.…

Category: Exchange Server SE / 2019 / 2016