veeam exchange 2016 backup best practices

We had lately some customers that struggeled with the recovery after a broken Exchange Update. What to restore and how to establish replication again. As well at restore it can get complicated. In general if you only backup active or passive databases you have always the issue with the human factor which can select the wrong stuff. That way you can backup both servers full and let the deduplication reduce the data. In case of backup saving, if you prepare well you can backup both DAG nodes in the same job and use per Job chains for the deduplication. We tell the VSS framework that we are ready with backup and the Exchange writer will decide what to do. Instead of our aproach, It will be better to backup both nodes in the same task, or maybe backup always only the same node?įor the log truncation part: Veeam itself do not decide if the logs will be truncated and on what systems with what replication.

If we backup the nodes in different tasks and different days, Could we have any problem when we will make a restore, or this doesn't affect?. Transaction logs will be truncated on all DAG members.īecause of 'Transaction logs will be truncated on all DAG members', I don't know If I am backing DAG in the right way. In particular, having all the databases active on a single node or with the active databases on each node.

ml?ver=100 and It says: Veeam Backup & Replication supports any configuration of DAGs. Besides, I make a full backup in the even months from one node and a full backup from the other node in the odd months. I would like not wasting space so instead backup both nodes everyday, I have created two different task and I backup a node one day, and the other one the following day.

We have two nodes (virtual machines) with active databases in both nodes. I just starting to backup my Exchange Infrastructure with V&R 10.

Veeam exchange 2016 backup best practices