LAB: Deploying Exchange 2010 DAG - Part 3 – Manage DAG

-

 

Manage Database Availability Group Membership

image

image


image


image

image

Summary: 2 item(s). 1 succeeded, 1 failed.
Elapsed time: 00:01:53

BQT-E14CAS1
Completed

Warning:
Insufficient permissions to access file shares on witness server 'BQT-MB07'. Until this problem is corrected, the database availability group may be more vulnerable to failures. You can use the Set-DatabaseAvailabilityGroup cmdlet to try the operation again. Error: Access is denied

Exchange Management Shell command completed:
Add-DatabaseAvailabilityGroupServer -Identity 'BQT-DAG1' -MailboxServer 'BQT-E14CAS1'

Elapsed Time: 00:01:27

BQT-E14MBS1
Failed

Error:
There was a problem changing the quorum on cluster BQT-DAG1. File share witness '\\BQT-MB07.\BQT-DAG1.network name was not found. This may be due to a problem with firewall settings.

Warning:
The network name 'BQT-DAG1' is not online. Please check that the IP address configuration of the Database Availability Group is correct.

Warning:
The network name 'BQT-DAG1' is not online. Please check that the IP address configuration of the Database Availability Group is correct.

Warning:
Insufficient permissions to access file shares on witness server 'BQT-MB07.. Until this problem is corrected, the database availability group may be more vulnerable to failures. You can use the Set-DatabaseAvailabilityGroup cmdlet to try the operation again. Error: Access is denied

Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2009-10-21_08-09-43.173_add-databaseavailabiltygroupserver.log".

Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -Identity 'BQT-DAG1' -MailboxServer 'BQT-E14MBS1'

Elapsed Time: 00:00:26



image

Blog Extended Reading
1. LAB: Deploying Exchange 2010 DAG - Part 1 – Configure Witness
2. LAB: Deploying Exchange 2010 DAG - Part 2 – Create NEW DAG
3. LAB: Deploying Exchange 2010 DAG - Part 3 – Manage DAG
4. LAB: Deploying Exchange 2010 DAG - Part 4 – Manage DAG Network
5. LAB: Deploying Exchange 2010 DAG - Part 5 - Create Database Copies



More Information & Reference
1. Deploying High Availability and Site Resilience

image

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-179c7992...
Read more

Backup issues and limitations with Exchange 2010 and DAG

-
  Backup issues and limitations with Exchange 2010 and DAG http://blogs.technet.com/b/ehlro/archive/2010/02/13/backup-issues-and-limitations-with-exchange-2010-and-dag.aspx   13 Feb 2010 12:14 AM   · I have come up with the following conclusions after testing some backup functionalities with Windows Server Backup and Exchange 2010 with DAG. There are some limitations that we'll have to be aware of: 1. Windows Server Backup (WSB) When using Windows Server Backup to backup an Exchange 2010 database the backup fails under the following conditions: - Each database and associated logs are stored on a dedicated LUN (these are presented by the SAN software to the OS as separate volumes as expected in Disk Management) - The database LUN is presented via a mount point - Some database copies on the server are not active For example, two mailbox servers that are DAG members (SERVER1 & SERVER2), and two mailbox databases (MBX1 & MBX2). If both mailbox...
Read more

Ref: Exchange 2007 中的郵件路由概觀

-
Image
  Exchange 2007 中的郵件路由概觀 · 代理程式處理提交的郵件 收到郵件要進行分類時，就會在 Hub Transport Server 上執行某些代理程式處理。此階段提供的代理程式，包括選用的 Forefront Security for Exchange Server 防毒代理程式與日誌代理程式。 · 收件者解析 進行此階段時，會解析收件者的電子郵件地址， 以判斷該收件者擁有的是 Exchange 組織內的信箱，或者是外部電子郵件地址。 · 路由 完成解析收件者的資訊之後，分類程式的路由元件會判斷郵件的 最終目的地以及前往該目的地的路由、選取下一個進行郵件轉送的區段或躍點 ，然後將下一個躍點資訊解析成實際的伺服器及 IP 位址清單。 · 內容轉換 在將郵件轉送至下一個躍點之前， 要執行內容轉換 ，如此才能以收件者能夠閱讀的格式傳送郵件。「內容轉換」程序可將電子郵件從某種格式轉換成另一種格式，以用於郵件流程或儲存 (例如， 從 MAPI 轉換成 MIME，或是從 UUENCODE 轉換成 Base64 編碼 )，或者，用於電子郵件用戶端特有的適當轉換 (例如，從 HTML 轉換為 RTF 或純文字)。 · 代理程式處理路由郵件 決定了特定郵件的路由決策後， 傳輸規則代理程式及日誌代理程式便會套用至 Hub Transport Serve r。提交郵件以及路由郵件時，都會套用日誌代理程式，如此傳輸規則代理程式對郵件所做的任何變更 (例如修改傳遞位址或套用郵件特定的日誌需求)，才不會略過日誌代理程式。 · 封裝郵件和產生 DSN 組合已完成分類的郵件， 然後將它移至傳遞佇列。傳遞狀態通知 (DSN) 也會在此階段產生 。   下列是內部郵件路由的重要組態和服務元件： Active Directory 站台     Active Directory 站台代表 Hub Transport Server 的路由界限。Hub Transport Server 會直接傳遞給 Mailbox Server、通訊群組擴充伺服器，並傳遞給本機 Active Directory 站台內連接器的來源伺服器，以及傳遞給訂閱該站台的 Edge...
Read more