Update 19 Updated most part of the text and links. + Minor updates on the other topics make them better understandable. Update 18: Changed the NFS statement slightly to reflect my latest discussions with other Exchange experts. Update 17: Added new NFS discussions and statements from the internet. Update 16: Added chappter “7.” with “Storage Spaces are not supported within a VM”. Update 15: Added Restore Tips and tricks ac)-am) VMware+Exchange Design + Background informations:” section with more tips. Update 13: Changed tips f), i) j) k) l) v) y) Changed Priority for Tips Changed SnapShot background story Added tips: aa), ab) As well I placed h) more prominent on the beginning of the chappter. Update 12: Added new VMware Exchange on vSphere guide and updated h) because of actual SnapShot changes in vSphere6 actual Patch level. Update 11: Added Tip y) and z) regarding existing SnapShots Update 10: Added the IP Less DAG section. November 2014 Corrected a statement at the CAS HA section. November 2014 Added Tip “x)” that addresses VSS Timeouts. August 2014 Added a tip from a forum member regarding Public Folder databases and VSS timeouts. July 2014 Added recommended Hotfixes to DAG recommendations section. June 2014 Added Transport Role and CAS role specific backup informations. April 2014 Added Exchange Update Link with Exchange 2013 CU3 example. Update 3: 11.April 2014 Added some planning informations round about CPU/RAM/DISK to section 2. I added some small updates to the text based on your feedback. blogger completely destroyed my article as a April-Joke, so I had to rearrange the text again.
Split of DAG failover / 20 sec timeout tips. plication/ that backing up the passive database will also truncate the logs on the active.Update 1: Added Exchange & Virtualization + NFS Support statement. Please correct me if I have misunderstood what was Andreas had explain on his blog. From my understanding Veeam should be able to call upon Microsoft VSS writer to notified it to truncate the logs from either active or passive database and then it should replicated to the other DAG members. My I ask if this is best practice as we do not have a third node that is purely passive. However for node 1 we had set it to truncate the logs, whereas for node 2 we had put it to copy logs only. Now currently we are backing up the the exchange servers independently and application-awareness enable on both node 1 and 2. Node 2 - DB1 (Passive) DB2 (Active), DB3 (Passive), DB4 (Active) Node 1 - DB1 (Active), DB2 (Passive), DB3 (Active), DB4 (Passive) An example of how our DAG look like in term of the active and passive database. Our DAG is consist of a cluster of 2 member servers along with a witness server.
0 kommentar(er)
