Backing up Microsoft Exchange 2016 DAG with Veeam to ensure exchange log truncation.
Hello Everyone, Our currently DAG setup is consist of two 2016 exchange member servers along with a witness server. Node 1 - DB1 (Active), DB2 (Passive), DB3 (Active), DB4 (Passive) Node 2 - DB1 (Passive) DB2 (Active), DB3 (Passive), DB4 (Active) Now according to our backup vendor (Veeam) when they are almost finished with backing up the server, Veeam send a signal to Microsoft VSS to basically truncated the exchange logs which then will truncate both the active and passive database. In this case for our example, when node 1 is completely backup Veeam will then send a signal to Microsoft VSS provider to then truncate logs of both passive and active database. (Please correct me if I miss understood how exchange logs are truncated.) It will then replicated the changes among the other DAG members. Therefore, my question and concern is from what Veeam indicated it is by Microsoft design that VSS provider can truncate passive database and then replicated to the primary source, is that truly the case?
Exchange 2016 Database copy
Hello Team, Environment consists of exchange 2016 cu21 servers and windows 2012 R2 All servers in DAG are physical serves Each database has 3 copies -2 at production site and 1 at DR site On particular SAN disk in production site , hard ware issue is observed and this lun will be changed 1)Database copies will be suspended ,New lun will be added Database copies will be copied on new lun then replication will be resumed Or 2) Database copies will be suspended , new lun will be added Then cmdlet will be executed : Resume-MailboxDatabaseCopy -Identity DB1\ MBX3 Which is supported method
Microsoft Exchange 2016 DAG Members addition issue from DR Site
Dear Friends, I am facing issue will adding DAG Members from DR Site in Stretch Cluster with IP Less DAG. The following are information of my Infrastructure DAG Configuration: IP Less Primary Site AD Site: Default Site Domain Controllers Windows Server 2016 2 Exchange 2016 Enterprise (Rollup 9) on Windows Server 2016 Standard (Rollup August 2018) 2 DR Site: AD Site: XYZ Domain Controller Windows Server 2016 1 Exchange 2016 Enterprise (Rollup 9) on Windows Server 2016 Standard (Rollup February 2019) 2 Replication Network and MAPI Network routing is working fine. I am facing error while adding third and forth Node in DAG. the following error are occurred. Error # 1 A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired". [Server: abc.domain.com] Error # 2 The following servers have been added to the database availability group but not to the cluster: abc.domain.com. This is usually the result of an error during membership change. Removing and re-adding the servers can correct the issue. Please help me out as I am trying to resolve this issue but till now there is no success. Regards, Nadeem Afzal