Microsoft TechNet
Sign in
Home Library Wiki Learn Gallery Downloads Support Forums Blogs
Popular Topics

Browse By Tags

Home » All Tags » DAG
Related Content

  • Blog Post: SPOTLIGHT: Using Microsoft Azure for Microsoft Exchange Database Availability Groups

    Joe Davies
    With Exchange Server 2013, you can configure your mailbox databases in a database availability group (DAG) for automatic datacenter failover. This requires three separate physical locations: two datacenters for mailbox servers and a third location to place the witness server for the DAG. If your organization...
    on 13 Jan 2015

  • Blog Post: CNO Pre Staging (DAGs)

    BesirovicX
    Hello there, Recently I had been helping a customer in a migration from Exchange Server 2010 to Exchange Server 2013. All went pretty normal, actually some of the steps were easier than I thought they would be, but there was a tiny little (and very annoying) surprise – the DAG creation kept failing…...
    on 19 Jun 2014

  • Blog Post: Data Protection Manager 中的 Exchange 2010 DAG 被动节点可见性和 EnableVSSWriter 注册表项

    微软中国TechNet
    嗨，大家好，我是 Andy Nadarewistsch。今天，我想谈一下 System Center Data Protection Manager 中的被动节点可见性。更具体地说，我想探讨一下被动节点不在 DPM 控制台中显示的原因。在保护 DAG 时，您会看到 DPM 控制台中没有列出被动节点或 Exchange 数据库。一般而言，存在以下一些原因： 拥有试图受保护的邮箱数据库的 任何节点上都没有安装代理 存在导致数据源无法枚举的 VSS 错误 EnableVSSWriter 注册表项被设为 1 请注意最后一个应用场景，我们将讲述当存在下面的注册表项时 DPM...
    on 10 Mar 2014

  • Blog Post: Windows Server 2012 R2 and Database Availability Groups

    Scott Schnoll [MSFT]
    Exchange Server 2013 Service Pack 1 (SP1) has released, and among other features and improvements , SP1 includes support for Windows Server 2012 R2 . This means that a database availability group (DAG) running Exchange 2013 SP1 on Windows Server 2012 R2 automatically takes advantage of the improvements...
    on 25 Feb 2014

  • Blog Post: Update-DatabaseSchema cmdlet

    Rob Whaley [MSFT]
    The Update-DatabaseSchema cmdlet is designed to safely upgrade database schema in a DAG deployment. Unlike previous releases, a database schema upgrade in Exchange 2013 can only occur after all DAG members are upgraded to a version of software that supports the schema version and there is control over...
    on 16 Feb 2014

  • Blog Post: Exchange2013: Testing MRS Across A DAG

    John Bailey [MSFT]
    In Exchange 2013, it may become necessary to test the Mailbox Replication Service (MRS) against all members of a Database Availability Group (DAG) . To do this, we can perform the following script: #We obtain the member servers of the DAG $Servers = (( Get-DatabaseAvailabilityGroup LAB-NAEX15-01...
    on 27 Dec 2013

  • Blog Post: DAGs: When Installing Them Becomes A Chore

    John Bailey [MSFT]
    I had a lab and I was running into a problem building a Database Availability Group (DAG). I had installed Exchange 2013 Mailbox Role on 3 Windows Server 2008 R2 Standard machines. I was receiving the following error: A database availability group administrative operation failed. Error: Failed to...
    on 25 Oct 2013

  • Blog Post: Exchange 2010 Datacenter switchover

    Loay Al Hammouri
    when exchange 2010 was released and the DAG feature was first introduced everybody was excited about it and looking forward to deploy it, but performing the disaster recovery is a nightmare because it requires multiple steps so I thought sharing the steps to do a site switchover in a scenario based will...
    on 30 Aug 2012

  • Blog Post: Exchange 2010 ServicePack 2 및 Rollup 2 설치

    Juaeha
    Exchange Server RTM에 Service Pack을 설치하게 되면, Active Directory 뿐만 아니라, Exchange Databse의 Schema가 변경됩니다. 또한 Exchange Database의 Schema 변경 때문에 SP가 설치된 서버의 Database를 SP 가 설치되지 않았거나, 하위 버젼의 SP가 설치된 서버로 이동 하는 것도 불가능해 지구요. 오늘은 Exchange 2010서버의 ServicePack 2설치와 관련된 내용을 살펴보겠습니다. 1. Exchange Server 역할별 Service Pack의...
    on 13 Apr 2013

  • Blog Post: Exchange 2013 DAG 구성 및 문제 해결

    Juaeha
    Windows Server 2012에 Exchange 2013을 설치하고 DAG를 구성하면 Member Server를 추가하려고 할 때 다음과 같은 예기치 않은 오류를 만나게 됩니다.  먼저 증상을 확인하기 위해 다음과 같이 DAG를 만들어 보겠습니다. New-DatabaseAvailabilityGroup -Name DAG -DomainController AD2012 -WitnessServer EX2013CAS01 -DatabaseAvailabilityGroupIpAddresses 192.168.10.120 그럼 이렇게 DAG가...
    on 12 Apr 2013

  • Blog Post: Mailbox Database 복사본 관리

    Juaeha
    먼저 Mailbox Database를 생성합니다. [PS] C:\Windows\system32>New-MailboxDatabase -Name MBX01DB01 -Server EX2013MBX01 -EdbFilePath H:\MailDatabase\MBX01DB01.edb -LogFolderPath H:\MailDatabase 하지만 Database 상태를 확인해 보면 아직  Mount가 되지 않았습니다. Mount-Database -Identity MBX01DB01를 이용하여 DB를 Mount 시킵니다. 생성된 Database에...
    on 13 Apr 2013

  • Blog Post: Exchange 2010 DAG MBX Rebuild

    Juaeha
    원하지 않았지만, 여러 가지 이유로 서버를 Rebuild 해야 하는 일들이 생깁니다. 예를 들어 H/W 이슈로 서버를 재설치 해야 하는 일이 있는데, 아주 오래 전에 Exchange MBX서버 Mother Board가 나갔는데, H/W가 오래 되어서 교체를 못하고 새 서버에 설치해야 하는 일이 있었죠. 뿐만아니라 Exchange Service Pack 설치 작업에서 Crash가 생겨서 문제를 해결 할 수 없는 경우들도 종종 볼 수 있죠. Exchange 2007의 경우는 setup.com /m:recovercms 옵션이 있었지만...
    on 15 Dec 2013

  • Blog Post: Exchange 2010 SP3 on Windows Server 2012

    Michael Hall (EXCHANGE)
    I've been busy with a small Exchange 2007 to Exchange 2010 engagement the last few days and we decided to go with Windows Server 2012 for the base operating system. Luckily for us Exchange 2010 SP3 has been released and I was very excited to deploy on a new Windows Server 2012 OS. I thought it would...
    on 2 Mar 2013

  • Blog Post: Rebuild an Entire Database Availability Group

    Mohamed Tawfik AMHIL
    A database availability group (DAG), together with mailbox database copies, can provide automatic recovery from a variety of server, storage, network, and other hardware failures. A DAG can also provide a site resilience solution so that you can perform a datacenter switchover in the event of a site...
    on 28 Feb 2013

  • Blog Post: Move Mailbox Database

    Mohamed Tawfik AMHIL
    1. Remove the Mailbox database copy: 1.2 In the EAC, go to Servers > Databases. 1.2 Select the mailbox database whose copy you want to remove. 1.3 In the Details pane, locate the passive copy you want to remove and click Remove. 1.4 Confirm the removal on the warning dialog box by clicking yes...
    on 7 Dec 2013

  • Blog Post: Exchange 2013 DAG Cluster Network Object

    Richard Schwendiman
    There has been some confusion about the CNO object creation with Exchange 2013 DAGs that I want to clear up. The documentation was a little unclear with the following statement: "When creating a DAG with Mailbox servers running Windows Server 2012 in an Active Directory environment with Windows...
    on 6 Dec 2012

  • Blog Post: Exchange 2013 DAG Cluster Network Object

    Richard Schwendiman
    There has been some confusion about the CNO object creation with Exchange 2013 DAGs that I want to clear up. The documentation was a little unclear with the following statement: "When creating a DAG with Mailbox servers running Windows Server 2012 in an Active Directory environment with Windows Server...
    on 4 Dec 2012

  • Blog Post: Learn Exchange 2013 with me! - High Availability and Site Resilience

    sachinshah55
    Exchange 2013 builds on the existing High Availability and Site Resilience features from Exchange 2010. A huge amount of work has been done in many areas to provide better availability and failure isolation. The use of DAGs and database copies along-with features like Single Item Restore, lagged copies...
    on 15 Nov 2012

  • Blog Post: DAG IP addresses and Failover Cluster Manager

    Chad Solarz [MSFT]
    “Hey Chad, how come I see two IP addresses in Failover Cluster Manager (FCM)? Then only one is “online” and the other is “Offline”? Is there an issue with my DAG?” Well let’s get some context here. This large customer has a stretched dag that spans two geographic and AD sites. This DAG (per Microsoft...
    on 12 Feb 2013

  • Blog Post: Case of the unfailback-able DAG

    Chad Solarz [MSFT]
    Good afternoon all, hoping you are having a good weekend! I wish I could say I had a bunch of sleep last night but I can’t. One of my customers reached out to me in frustration at 1 am. They were in the middle of doing some initial Disaster Recovery testing for their new 2010 Exchange environment. For...
    on 22 Sep 2012

  • Blog Post: What You Need To Know About Exchange 2010 DAG Failover Behavior

    Premier Field Engineers
    Article written by Jaroslav Zikmund, Microsoft Premier Field Engineer. In this article, I’ll provide some insight into changes in Microsoft Exchange Server 2010 Database Availability Group (DAG) failover behavior. The Exchange 2010 mailbox server which is part of the DAG uses windows clustering in a...
    on 30 Nov 2011

  • Blog Post: Exchange: DAGs and reseeding

    Marc Dekeyser
    *repost from my old blog: http://geekswithblogs.net/marcde/archive/2011/11/03/dags-and-reseeding.aspx I worked on a case today which had 2 Exchange 2010 servers in a DAG with about 6 mailboxes, all in healthy status. All but one that is. This DataBaseCopy just would not come back into sync and was stuck...
    on 10 May 2012

  • Blog Post: Secondary Protection and Exchange 2010 DAG Node Protection in System Center Data Protection Manager

    J.C. Hornbeck
    Hi everyone, Andy Nadarewistsch here, and today I want to talk about secondary protection and Exchange 2010 DAG node protection in System Center Data Protection Manager 2010 (DPM). DPM allows for great flexibility when it comes to protecting Exchange ...read more
    on 9 May 2012

  • Blog Post: Secondary Protection and Exchange 2010 DAG Node Protection in System Center Data Protection Manager

    J.C. Hornbeck
    Hi everyone, Andy Nadarewistsch here, and today I want to talk about secondary protection and Exchange 2010 DAG node protection in System Center Data Protection Manager 2010 (DPM). DPM allows for great flexibility when it comes to protecting Exchange DAGs (Database Availability Groups) but this can become...
    on 9 May 2012

  • Blog Post: DPM による Exchange 2010 DAG のバックアップ時の注意点について

    Teppei Ishii
    こんにちは。System Center サポート部の石井です。 今回は DPM より、Exchange 2010 の DAG 環境をバックアップする際の注意事項についてご紹介します。 (現状、Exchange 2010 DAG に対応している DPM のバージョンは 2010 のみです。今後リリース予定の DPM 2012 でも、原則として同様の設定が必要となります。) 1. ノードは最低 2 つバックアップすることを推奨いたします。 必須の条件ではありませんが、ベストプラクティスとなります。 もし、ノードを 1 つのみバックアップしている場合、何らかの理由で該当のノードがダウンし、別ノードのみの運用となった場合にバックアップが一切不在の状態となります...
    on 19 Oct 2011