Can Veeam back up an Exchange VM running on an ESX(i) or a Hyper-V host? As a result, there have been many questions about the backup and recovery of those apps, including questions about what Veeam has to offer for such circumstances. I don't know for sure.īut I'm in agreement that I either need to redesign my RAID for both nodes, or consider migrating the DBs.Over the last few years, virtualization has gained a lot of trust and many decided to virtualize Microsoft Exchange and other I\O intensive business apps. Though I believe Backup Exec's behavior is a bit different with DAG backups. Surprisingly, Backup Exec does not cause this issue when backing up either node (passive OR active).
Like I said, I've only noticed an issue when I ran my Veeam backup. We don't have any issues with performance on either node (I've conducted several failovers over several months). This was setup by a consulting company prior to my time here. There are 9 disks total on each DAG node (4 DBs, 4 log disks, and an OS disk). Looks like I have some baselining work to do. I've doubled the CPU cores (from 4 to 8) on the Exchange servers to see if that helps but was hoping maybe there were some other tips or best practices I should be following or anything else I may be overlooking. Suffice to say, I'm currently using Backup Exec, and though I hate it and am ready to move to Veeam, I've never seen this type of behavior when backing up our Exchange DAG. Has anyone ever experienced such a strong performance hit on Exchange backups with Veeam? I can only imagine it would be impossible to backup a single Exchange server if there was no DAG environment. I assume the replica failure during the backup is causing all of this.
However, the same behavior occurs on the incremental jobs as well.Īdditionally, attempting a restore of the "successful" backup fails when the Exchange Explorer cannot mount 3 out of 4 databases due to log corruption (so it says in the logs). I figured okay, it's an active full backup, I understood going in that it's going to be tough on the server. When the backup completes, the VSS Exchange Replica writer is in a retryable error state and I have to reboot the passive node for the replica to begin again between the two nodes. Exchange Replica event errors all over the place, Replay and Copy queue length increasing the entire time. On the first run of the job (which is an active full backup), the performance hit on our passive node is so significant, that replication starts to fail between the nodes while the backup is running. In order to avoid any performance issues, I am only backing up the passive node. I'm testing Veeam Backup and Replication 9 in our environment.
0 kommentar(er)
