marama wrote:EDIT: oh, now I realise the "you will need to reconfigure your jobs" might mean I just need to remap the backup
Regarding backup jobs mapping, if you just re-add corresponding replica VMs into existing backup jobs, you would be able to map the jobs to existing backup files to keep backup history.
Vitaliy S. wrote:Hi Cor,
You can either use replication or Quick Migration jobs to do that. Please review our Evaluator's Guide for more info.
As to possible tips and tricks for VM migration process, then it would help if we could know a bit more on your environment
marama wrote:Unfortunatelly, I am still struggling with this. I've tried everything possible to switch backup job source from old host to new host, while keeping the backup "base" - no luck so far. Am still waiting to hear from Veeam Support, but in all my tests I keep getting the line "backup is no longer processed by this job". I guess the VM-replica on the new host has another VMID so the backups treats it as complete different VM, hence cannot make use of existing backup files. Am I doing something wrong, is there a way around this? (am pointing to standalone hosts, not vCenter).
albertwt wrote:So, what's the difference and benefits of using Veeam replication as opposed to using the builtin VMware vSphere replication ?
foggy wrote:Well, each time you register VM within VI, it gets a unique ID, which is used by Veeam B&R to track VMs. So if the VM ID is changed (and replica VMs have IDs different from the original VMs), it technically makes them new VMs from perspective of our product. After re-adding VMs and mapping backup jobs, they have to read the entire VM image during the first job run. You can ask support for assistance in modifying product database to avoid this, though.
Users browsing this forum: Google Feedfetcher, stephendietrich and 1 guest