Exchange 2007 Database Portability (資料庫可攜)

-

 

Exchange 2007 Database Portability 資料庫可攜測試 

資料庫可攜性功能可免除上述限制，並解決這些限制所帶來的問題。資料庫可攜性是基於下列原因而執行：

  • 免除復原程序中容易犯錯的人工步驟，進而提高可靠性。
  • 若是遺失叢集信箱伺服器的案例，則必須先復原叢集信箱伺服器，用戶端才能存取 Exchange 資料庫。
  • Exchange 信箱資料與伺服器無關，因此存取資料也應該與伺服器無關。
  • 資料庫可攜性可在各種嚴重損壞修復案例中減少端對端復原時間。


LAB目的: 將 IMSS.Virus 這個信箱從BQT-CCR1 上可攜至 BQT-MB07 上

Resolution
 

1. 位於BQT-CCR1 Server 上的 IMSS.Virus 信箱clip_image004


2. 信箱屬於BQT-CCR1_SSG_JUN 的mailbox store clip_image006

3. 先卸載此資料庫 clip_image008


4. 複製資料庫至BQT-MB07 clip_image010

clip_image012


5. 進行資料庫檢察 ESEUtil /mhclip_image014


6. 新建一樣名稱的Storage Group 及 Mailbox Storeclip_image016

clip_image018


7. 此資料庫要設定可被還原clip_image020


8. 替換資料庫 clip_image022


9. 掛載資料庫 clip_image018[1]


10. 登入OWA 測試 clip_image024


11. OWA 無法存取clip_image026


12. 登入Outlook 測試，還是檢查到搬移前的信箱伺服器 clip_image028


13. 無法開啟Outlook clip_image030


14. 取得信箱資訊 clip_image032


15. 進行信箱設定移轉 clip_image034

clip_image036


16. 信箱移轉完成，需重啟Outlook clip_image038

clip_image040


17 . OWA & Outlook 可正常登入 clip_image042

clip_image044

 

More Information

1. 資料庫可攜性
2. 如何使用資料庫可攜性將信箱資料庫還原至新伺服器

Comments

Post a Comment

Popular posts from this blog

E15 CU3–Update Failed–AD replicated Exceeded the tombstone lifetime.

-
Image
  Exchange 2013 CU3 The naming context is in the process of being removed or is not replicated http://technet.microsoft.com/en-us/library/replication-error-8452-the-naming-context-is-in-the-process-of-being-removed-or-is-not-replicated-from-the-specified-server(v=ws.10).aspx   C:\> REPADMIN /SHOWREPS Root\RDC01 DSA Options: IS_GC Site Options: (none) DSA object GUID: f1694974-47c4-4555-a214-db3c86854aeb DSA invocationID: f1694974-47c4-4555-a214-db3c86854aeb ==== INBOUND NEIGHBORS ====================================== CN=Schema,CN=Configuration,DC=lab7,DC=root     TW\AD02 via RPC         DSA object GUID: bfcc1053-e1da-46fd-8b9d-179c79921331         Last attempt @ 2013-12-19 17:
Read more

202301 - Exchange onpreme - PowerShell Serialization Payload Signing

-
Image
Released: January 2023 Exchange Server Security Updates https://techcommunity.microsoft.com/t5/exchange-team-blog/released-january-2023-exchange-server-security-updates/ba-p/3711808 https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ 1.  Update KB5022143 (Exchange SU) 2. Run latest HealthCherker 3.  PowerShell Serialization Payload Signing https://microsoft.github.io/CSS-Exchange/Diagnostics/HealthChecker/SerializedDataSigningCheck/ Certificate signing of PowerShell serialization payload in Exchange Server https://support.microsoft.com/en-us/topic/certificate-signing-of-powershell-serialization-payload-in-exchange-server-90fbf219-b0dd-4b2c-8a68-9d73b3309eb1 4.  MonitorExchangeAuthCertificate    https://microsoft.github.io/CSS-Exchange/Admin/MonitorExchangeAuthCertificate/ 5.                 New-SettingOverride -Name "EnableSigningVerification" -Component Data -Section EnableSerializationDataSigning -Parameters @("Enabled=true&qu
Read more

E14–Bulk Create Mail Contact & Set-Contact

-
Image
  http://community.office365.com/en-us/w/exchange/579.aspx     Get-Contact | Export-Csv c:\temp\contact.csv Get-MailContact | Export-Csv c:\temp\Mailcontact.csv   [PS] Import-Csv .\Contact_Source.csv | % {New-MailContact -Name $_.Name -DisplayName $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Alias $_.Alias -PrimarySmtpAddress $_.PrimarySMTPAddress -OrganizationalUnit "Contacts" -WhatIf }   [PS] >$Contacts = Import-Csv .\Contact_final.csv [PS] >$Contacts | foreach {Set-Contact $_.Name -Company $_.Company -Department $_.Department -Office $_.Office -Phone $_.Phone }
Read more