- Posts: 24
- Liked: 1 time
- Joined: Jan 13, 2023 6:50 pm
I am pretty new to Veeam and in the process of setting it up in our environment to replace Altaro VM Backup
We have a main Windows-Server 2019 Host-System, that runs our VMs, one big one as our fileserver and some smaller ones for utilities - Domain Controller, Linux-VMs, 1 Windows 10 VM as Veeam Backup Server (I run with Windows 10 for the backup server, because we would require to buy another full Windows Server license to cover that additional VM, which is a cost, I do not fully see the need of having - according to the manual, Windows 10 is a supported system to run Veeam Backup&Replication on)
The most important VM to be backed up is our fileserver, that is about 11TB in size.
At the moment, we are also running a Hyper-V Replica Setup, so the VM is replicated with Hyper-V-Toolset to the Secondary Host in 5 Minute intervals.
When reading the manual of Veeam, I came across this part though, which makes me doubt, if I can keep this setup running, when switching to Veeam, or if I need to also switch to Veeam Replication to make it work properly:
Do not use native Hyper-V replication especially if replication is targeted at the same scope (host, cluster, SCVMM) where the source VM resides. This can cause VM ID collision. Instead, we recommend you use Veeam replication. For more information, see Replication.
The two host systems are not part of a cluster or anything like it - they are part of the same domain, but that's about it.
We don't have high-availability setup - it's a plain replication with Manual Failover-Option.
Can I keep that Replica-Setup within Hyper-V or do I need to switch to Veeam Replication to prevent any issues when using Veeam as my backup tool of choice?
- Service Provider
- Posts: 69
- Liked: 7 times
- Joined: Oct 28, 2019 7:10 pm
- Full Name: Rob Miller
Users browsing this forum: No registered users and 9 guests