Disaster recovery of Exchange DAG architecture (2)

The last DAG recovery was carried out in the test domain environment (refer to the article: http://hubuxcg.blog.51cto.com/2559426/1156785), this use of the work environment domain, again encountered two problems, now recorded, share with you!

Environment Description: The original DAG environment consists of two Exchange Servers MAL741/MAL742. Currently, Setup/mode: Recoverserver is used to install the first Server MAL741,

1. DatabaseCopy cannot be deleted

Problem description:

Go to Step 2: delete DatabaseCopy of MAL742 in the DAG, several DBs are found to be undelable, And the PowerShel: Remove-MailboxDatabaseCopy-Identity QX-DB2 \ MAL742-Confirm: $ False:

650) this. width = 650; "title =" clip_image002 "style =" border-top: 0px; border-right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image002 "height =" 72 "src =" http://www.bkjia.com/uploads/allimg/131227/1T2115130-0.jpg "/>

Cause analysis:

Because the current database Hosted (Active) is on the unrecovered HOST: MAL742, but MAL742 is not yet restored, it cannot be deleted, and the execution of Mover-ActiveMailboxDatabase cannot be successful!

Solution:

Into AD, open ADSIEDIT, into the current DB to be restored, such as: QX-DB2

Configuration \ CN = Configuration, DC = Domain, DC = com \ CN = Services \ CN = Microsoft Exchange \ CN = Domain \ CN = Administrative Groups \ CN = Exchange Administrative Group \ CN = Database \ CN = QX-DB2, QX-DB2 is the DB to be restored now, right-click, attribute

650) this. width = 650; "title =" clip_image003 "style =" border-top: 0px; border-right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image003 "height =" 244 "src =" http://www.bkjia.com/uploads/allimg/131227/1T2113036-1.png "/>

650) this. width = 650; "title =" clip_image004 "style =" border-top: 0px; border-right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image004 "height =" 244 "src =" http://www.bkjia.com/uploads/allimg/131227/1T211E39-2.png "/>

Locate msExchOwningServer, open it, change MAL742 to MAL741, and change the current Hosted (Active) to MAL741.

650) this. width = 650; "title =" clip_image005 "style =" border-top: 0px; border-right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image005 "height =" 244 "src =" http://www.bkjia.com/uploads/allimg/131227/1T211O55-3.png "/>

Go to PowerShell again and execute it!

Remove-MailboxDatabaseCopy-Identity QX-DB2 \ MAL742-Confirm: $ False,

650) this. width = 650; "title =" clip_image007 "style =" border-top: 0px; border-right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image007 "height =" 11 "src =" http://www.bkjia.com/uploads/allimg/131227/1T2115947-4.png "/>

Perform the same operation on several other databases!

2. You cannot use PowerShell to merge emails.

Problem description:

You cannot use the PowerShell Cmdlet restore-mailbox and New-MailboxRestoreRequest to merge the user email content in the database with the current user Email:

Cause analysis:

Exchange 2010 Service Pack 1 (SP1) or later, you need to use the New PowerShell Cmdlet: New-MailboxRestoreRequest instead of Restore-Mailbox, and the current environment is Exchange2010 SP2, so you need to use: new-MailboxRestoreRequest

When using New-MailboxRestoreRequest, you must have sufficient permissions!

Solution:

Enter AD and add the current user to the Organization Management group. The execution is successful:

New-MailboxRestoreRequest-SourceDatabase RDB-SourceStoreMailbox 'johnson '-TargetMailbox 'johnson'

You can also run the following PowerShell command to view the merge progress:

Get-MailboxRestoreRequest | Get-MailboxRestoreRequestStatistics

650) this. width = 650; "title =" clip_image009 "style =" border-top: 0px; border-right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image009 "height =" 27 "src =" http://www.bkjia.com/uploads/allimg/131227/1T211L00-5.jpg "/>

After the script is executed, run the following command to check the size of the user and mailbox in the current database:

Get-Mailbox-database qx-db4 | Get-Mailboxstatistics | sort totalitemsize-desc | ft displayname, totalitemsize, itemcount

650) this. width = 650; "title =" clip_image011 "style =" border-top: 0px; border-right: 0px; border-bottom: 0px; border-left: 0px; display: inline "border =" 0 "alt =" clip_image011 "height =" 26 "src =" http://www.bkjia.com/uploads/allimg/131227/1T2114361-6.jpg "/>

Summary:

Recovery tests in different versions and environments may encounter different problems. Therefore, you must develop a recovery test plan and perform regular drills to cope with the problem in a timely manner, minimize the loss or downtime!

This article is from the "" blog. For more information, contact the author!