Use classic agent-based backups (as if you were backing up physical servers), as opposed to host-based backups. But you will lose fast incremental backups and they will put more load on your production storage due to having to read all VM blocks to physically determine the changed ones.Ģ. Make Veeam not to enable RCT on protected machines. If you're really concerned about the issue, with Veeam you always have two additional options:ġ. The issue will appear if you start doing host-based Hyper-V backups, be it with Veeam or any other vendor, because that would enable RCT on the protected machines. My questions are (1) should I install Veeam and (2) if so, where should I install and run it? I appreciate any just installing Veeam will not do anything. I am somewhat tentative about just installing and running it not knowing if my server’s performance will be impacted Is the performance noted in the forums an issue for everyone in this configuration? However, from what I have read if I'm correct, the issue is that Resilient Changed Tracking (RCT) gets enabled anyway on the 2019 server in order to track block changes in VMs and would potentially impact the performance on the 2019 server. I can install Veeam on another HyperV server running on the same 2019 physical server or, I could install it on a separate physical machine running 2008 R2. Should I not install Veeam? My server setup is similar to the original, with 2019 Windows Server running 2 Hyper V virtual machines (one VM is 2019 and one is 2016).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |