Wednesday, December 10, 2014

Proper Database Availability Group Creation - How to not do the stupid thing I did

I was configuring a Database Availability Group (DAG) in Exchange 2013 just using the Exchange Admin Center. It should be a pretty straight-forward process and has been for me in the past, more or less. After all, the GUI promises that everything will be taken care of for you.



However, I started running into all sorts of errors...


Text: A server-side database availability group administrative operation failed with a transient error. Please try the operation again. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "CreateCluster() failed with 0x5. Error: Access is denied"
But wait... there's more!

Text: Add-DatabaseAvailabilityGroupServer
WARNING: Server �exchmbxcas02� has multiple network interfaces that are configured with default gateways. This is not a recommended configuration. It is recommended that only one network interface have a default gateway defined. Error: A matching cluster network for the specified IP address could not be found� 
(By the way... that message about the default gateway problem was because I had DHCP enabled for IPv6. Either configure a static address for IPv6 or disable it outright.)
Text: Add-DatabaseAvailabillityGroupServer
WARNING: The operation wasn't successful because an error was encountered.

A server-side database availability group administrative operation failed with a transient error. Please try the operation again. Error: an error occurred while attempting a cluster operation. Error: Cluster API failed: "CreateCluster() failed with 0x5. Error: Access is denied"



...and it's mainly because I forgot about a key step in the process. That step is basically ignoring whatever EAC tells you because it's a filthy liar.

The BEST thing to do is create the Cluster Name Object (CNO) on your own, and assign permissions. So, let's go to Active Directory Users and Computers (ADUC) and do just that.

1. Navigate to where you want to store the object. It doesn't matter where you pick, but it makes sense to stick it in the OU with your Exchange servers. Create a new Computer object.



2. Name your DAG:




3. Click OK and then disable the new account:


4. Right-click, "Properties"


5. Click the Security tab. Click Add...


6. Click Object Types...



7. Put a checkmark by Computer



8. Search for the names of the Exchange mailbox servers in the DAG.



9. Find each one, select it, and click "Full control" under "Permissions"



10. Click OK. Go back to the Exchange Admin Center. Click "database availability groups" in the servers tab. Click New.




11. Fill in the information. The name must match the CNO created earlier. The witness server must have the "Exchange Trusted Subsystem" added to local admins on this server. You don't need to enter anything for the directory unless you want to. If you don't choose an IP address, the server will use DHCP. I'm not sure what problems you may run into with this approach, so just choose a static IP address in the same subnet as the servers. If they are in different subnets, enter an address for each subnet.




12. Click Save. Click "Manage DAG membership."




13. In the window that opens, click the + button to add servers.




14. Select the servers to be included in the DAG. Click "add ->". Click ok, and then click save.




15. The process should complete successfully. Leave a comment if you're running into trouble.




No comments:

Post a Comment