Hello,
I am deploying two normal high available database copies in Exchange 2013 in local site and one lagged DB copy in remote DR site. My question is that in case local site goes down for extended period and I activated the lagged copy in DR site by playing all log files.
what will be the procedure when primary site come back on. Lets say the issue in primary site was power failure, so all servers and storage are well and no hardware failure has occurred. Will it automatically start copying log files back from DR site to primary site or do i need to do full re-seed of DB from DR site to primary site?