none
Creating DAG - problem with specifying FSW server RRS feed

  • Question

  • Good day,

     

    I am trying to create new DAG. With the EMC I specify my witness server and the witness folder. I have added Exchange Trusted Subsystem to the local admin group of my witness server.

     

    I then run the wizard but get the error message:

     

    But that is not correct, podaci.algoit.net indeed has the required group added. I have also tried with my DC as witness (added the exchange group to the built in administrators group in AD) - same result. My witness server is running DFS role, but I doubt that is relevant. I have checked, my Exchange is a part of the Exchange Trusted Subsystem.

     

    What did I miss, help please.

    Monday, September 27, 2010 4:32 PM

Answers

  • Ok, I recreated the group, added static IP to the group.

    Still had the same warning about the FSW. Then I configured NIC's of my exchange and added it to the DAG. It was successful. Now I can also see the folder I specified as my FSW on the witness server, but it is not shared and I can not see any files within.

    If I check the DAG, I can see my exchange under operational servers.

    Is this ok now ?

    EDIT: Now the FSW is shared and I can see the requried files inside. I am not sure when this happened, but I noticed it when I added my 2nd exchange to the DAG. I am really confused why was I getting the error while creating the DAG.

    So in the short terms - I created DAG and assigned it static IP. Configured exchange servers NIC's as required (replacation & MAPI). After that I added my servers to the DAG. Checked my WitnessServer and the share was up & working (folder with file share witness that is) that I specified during creation of DAG.

    Thursday, September 30, 2010 9:00 AM

All replies

  • Is there a compelling reason you can't use a hub transport server for the witness?
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."
    Monday, September 27, 2010 4:33 PM
  • Hi

    And you have waited a while so this isn't replication related?

     

    And like Ed wrote, why not use HUB for fsw?


    Jonas Andersson MCTS: Microsoft Exchange Server 2007/2010 | MCITP: EMA 2007/2010 | MCSE/MCSA Blog: http://www.testlabs.se/blog
    Tuesday, September 28, 2010 7:52 AM
  • Hi,

    Please ensure that you add  Exchange Trusted Subsystem to the local admin group on your fsw.

    Do not use Domain controller as the File Share Withness for DAG.

     Besides, please try to ignore the warning and then have a ExBPA check for your Exchange organization.

    Regards,

    Xiu

    Tuesday, September 28, 2010 8:39 AM
  • Thanks for replys.

    I have all roles installed on 1 server, so I can not set  hub as a witness. I would like to install another MB server so I can test DAG. This is lab environment.

    And why not some other member server, since it is supported and should be working fine?

    It could be the replication... I will try tomorrow since I was out of office today. I did everything 'by the book', so I am confused with this error.

    No folder is created, but DAG is created. If I do it directly from the shell, DAG is not created, and folder also not. Thanks for the advice, I will try to run ExBPA if the warning remains.

    Tuesday, September 28, 2010 9:45 PM
  • Ok, still no changes. I ignored the warning. I ran ExBPA 2.8 (updated before running).

    I got some errors: The Exchange schema extensions are from an unknown version. Schema version detected is 14726.

    Active Directory domain 'ALGOIT' has an unrecognized Exchange signature. Current DomainPrep version: 13040.

    Exchange server EXCHANGE.algoit.net is a virtual machine but the additional tools are not installed. This configuration is not supported. Install Virtual Machine Additions for this guest.

     

    I ofcourse followed the provided links, but they just got me confused... arent those versions proper for Ex 2010 SP1 ? Could they be a cause to my problem? I am also not sure about the 3rd error, since virtual machine addiotns ARE installed! (using Hyper-V on 2008 R2)

    Wednesday, September 29, 2010 8:28 AM
  • Schema 14726 is Exchange 2010 SP1. it's a known issue that certain versions ExBPA - even after updating - don't recognize the Exchange 2010 SP1 schema version (see http://exchangeserverpro.com/exchange-best-practices-analyzer-reports-unrecognized-exchange-signature ). Note that domain objectVersion 13040 is Exchange 2010 SP1 level, see http://eightwone.com/references/schema-versions/ . Use Ex2010 SP1's BPA instead.

    On the topic, verify the FSW is created and assuming you've added the ETS account to the local admins group on the server hosting the FSW you should be good.Try set-databaseavailabilitygroup DAG -witnessserver SERVER – witnessdirectory FOLDER; if you receive any warnings or errors regarding permissions etc.

    Also look here for manually creating the FSW:
    http://www.thecabal.org/2010/08/manually-creating-a-dag-fsw-for-exchange-2010/

    In addition, also see this topic:
    http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/5e96e5ef-deeb-4b5c-a65e-4ed731ac7c9c


    Michel de Rooij,
    MCITP Ent.Msg 2007+2010| MCTS W2008, Ex2007+2010 Conf, OCS2007 Conf | MCSE+Msg2k3 | MCSE+Inet2k3 | Prince2 Fnd | ITIL
    I blog on http://eightwone.wordpress.com/ and tweet on http://twitter.com/mderooij
    Wednesday, September 29, 2010 9:20 AM
  • Thanks for the explanation about the errors!

    I have created DAG with the wizard, then used your command line, but I got the same error: WARNING: The Exchange Trusted Subsystem is not a member of the local Administrators group on specified witness server

    " Share the folder with the following DAGNAME.FQDN (If you try a different share name,
    it won’t work. This is somehow required)
    - Give the DAGNAME$ computeraccount Full Control (Share)"

    Does this refer to the object in AD that should be created for the DAG cluster? I'm a bit confused here...

    Wednesday, September 29, 2010 11:17 AM
  • Share name (of DAG folder) should be DAGFQDN, e.g. DAG01.algoit.net

    There should be a DAG01$ account in AD; give that account full control on the share.

     

     


    Michel de Rooij,
    MCITP Ent.Msg 2007+2010| MCTS W2008, Ex2007+2010 Conf, OCS2007 Conf | MCSE+Msg2k3 | MCSE+Inet2k3 | Prince2 Fnd | ITIL
    I blog on http://eightwone.wordpress.com/ and tweet on http://twitter.com/mderooij
    Wednesday, September 29, 2010 12:50 PM
  • How many nodes are in this DAG?

     

    Wednesday, September 29, 2010 1:05 PM
    Moderator
  • There was no object, so I created one and gave the permission.

    I get the different output:

    cmdlet Set-DatabaseAvailabilityGroup at command pipeline position 1

    Supply values for the following parameters
    Identity:

    I type dag (as a name of my database availability group) and get the same thing.

    WARNING: The Exchange Trusted Subsystem is not a member of the local Administrators group on specified witness server.

     

    I am not sure this works, since it is also said that it aint tested.

    Wednesday, September 29, 2010 1:23 PM
  • there are no nodes, since I cannot create the DAG at all.

     

    Would it work if I installed just one seperate HUB server, just to be a witness and nothin else.... I know it sounds bizarre, but I am out of idea.

    Wednesday, September 29, 2010 1:47 PM
  • Hi,

    Please try to use Add-DatabaseAvailabilityGroupServer to add mailbox server to DAG and then check the issue again.

    Regards,

    Xiu

     

     

    Thursday, September 30, 2010 1:25 AM
  • Ok, I recreated the group, added static IP to the group.

    Still had the same warning about the FSW. Then I configured NIC's of my exchange and added it to the DAG. It was successful. Now I can also see the folder I specified as my FSW on the witness server, but it is not shared and I can not see any files within.

    If I check the DAG, I can see my exchange under operational servers.

    Is this ok now ?

    EDIT: Now the FSW is shared and I can see the requried files inside. I am not sure when this happened, but I noticed it when I added my 2nd exchange to the DAG. I am really confused why was I getting the error while creating the DAG.

    So in the short terms - I created DAG and assigned it static IP. Configured exchange servers NIC's as required (replacation & MAPI). After that I added my servers to the DAG. Checked my WitnessServer and the share was up & working (folder with file share witness that is) that I specified during creation of DAG.

    Thursday, September 30, 2010 9:00 AM