Azure AD Connect Backup and restore.

Contributor

Hello!

 

We use Azure AD Connect for syncronizing our local users with Azure. We use two servers, main and staging. Can anyone give an advice how to make a correct backup of this systems for cases of servers lost?

3 Replies

@caseykraus 

The article you referred to explains only AD Connect configuration backup and restore. I doubt it doesn't answer initial question. The ask was rather what is the backup / restore scenario and how one could get the AD Connect / SQL backend servers restored in case of disaster or OS disruption or whatever else what cause AD Connect servers collapsed (what type of backup should be used or what would be the restore procedure / constrains to bring the AD Connect infra back to operational state. 

According to your AAD connector design as fault-tolerance in which primary server as export to sync to O365/Azure AD from On-Prem to azure and staging has read-only export where you can rollback for any crit-sit.

 

However, taking VM level backup using azure native backup or MABS or thrid party integrated solution using VEEAM VM azure backup is highly resilient for restoring the VM in case of OS corrupt or application corrupt.

 

The following article is defined about the backup configuration of AAD which would also helpful for your backup scenarios.

https://github.com/Microsoft/AADConnectConfigDocumenter

 

Note: Azure AD Connect requires a SQL Server database to store identity data. By default, a SQL Server 2012 Express LocalDB (a light version of SQL Server Express) is installed. SQL Server Express has a 10-GB size limit that enables you to manage approximately 100,000 objects. If you need to manage a higher volume of directory objects, point the installation wizard to a different installation of SQL Server.