question

bags200-4895 avatar image
0 Votes"
bags200-4895 asked AndyDavid answered

Azure AD Connector

If I have one Azure Ad connector at one data center. If there was a disaster or during DR testing, I power down the the Azure AD connector and bring it up a copy/replicated/backup on the other data center. Same VLan no change to the machine. Then run it for a day then delete it and restore the primary data center machine and bring it back up. Would that server that was down completely sync with all changes it missed while it was down even thought they sync'd to the one in DR test?


Is this process support if there was a problem?



azure-ad-connect
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

AndyDavid avatar image
0 Votes"
AndyDavid answered bags200-4895 published


Really this isnt the way to do this

You need at least two AADConnect servers. One is the active one, one is in staging mode but they are peers - each has the same config - each using their own backend database.

All the steps to do this are here:

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-staging-server

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Even if I use two AADConnect Servers, what is going to happen that we take down the primary data center and we activated the passive AADConnect servers and then run it for about 8 hours, the primary server would have been down the entire time. Then we change the Secondary server back to passive and bring up the primary.

but what happens if the secondary is passive and we have an issue with both servers and have to restore to a new machine.

The system has local database.

I not sure I understand why I would have two servers with today's technology of being enable to extend the Vlan and move machine back and forth without change. With only one server up at at time, won't they sync from the cloud? If I build a new server and configured it, would I need to restore the database or will it just rebuild for the cloud.

0 Votes 0 ·

Even if I use two AADConnect Servers, what is going to happen that we take down the primary data center and we activated the passive AADConnect servers and then run it for about 8 hours, the primary server would have been down the entire time. Then we change the Secondary server back to passive and bring up the primary.

but what happens if the secondary is passive and we have an issue with both servers and have to restore to a new machine.

The system has local database.

I not sure I understand why I would have two servers with today's technology of being enable to extend the Vlan and move machine back and forth without change. With only one server up at at time, won't they sync from the cloud? If I build a new server and configured it, would I need to restore the database or will it just rebuild for the cloud.

0 Votes 0 ·
AndyDavid avatar image
0 Votes"
AndyDavid answered

The Staging and active server each have their own SQL databases are are both up to date.
When one server is down and the other is set as the "active" server and removed from staging mode, all that means is that the active server is now exporting objects to Azure and to your on-prem forest.

Once the primary data center is back online, do not bring up the original AADConnect Server until you set the other DCs AADConnect to Staging Mode, then bring the primary DC AADConnect server and it can be allowed to export the results again as the "primary"

There are other advantages as well: When you upgrade, you can upgrade one at a time, switching between servers and testing as you upgrade.

It makes it very easy, so I dont see any advantage with having one server having to restore or extend a Vlan etc...

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.