Veeam Quick Migration Use?

[Mi32]

Here is my situation:

Current Systems are

vCenter 8.03 build 24322831 Standard version
3 host are all the below configs

VMware ESXi, 7.0.2, 17867351 Enterprise plus version

Hardware:
Model: ProLiant DL325 Gen10
Processor Type: AMD EPYC 7402P 24-Core Processor
Logical Processors: 48
NICs: 7

One TrueNas Storage Device all 3 host are connected to and sharing via ISCSI

Total VM = 40 to migrate to new systems

New Systems=

New Systems are vCenter 8.03 standard
ESXI ESXi-8.0U3b-24280767

3 Dell Host
Dell Inc.
Model PowerEdge R640
CPU 48 CPUs x Intel(R) Xeon(R) Platinum 8168 CPU @ 2.70GHz
Memory 382.62 GB

They will be connecting a 3 host to a Synology NAS FS-6400 All Flash station ISCI DSM 7.2


My question is what is the best way and how would I use quick migration from veeam to do this? We have Veeam Advanced license will this work or do we need to go to Premium?

I have never used QM just B&R and V1 so if can explain as much detail on how to do this that would be great?

Do I install veeam server on both old and new systems?? etc...

Thanks in advacne

[Andreas Neufert]

As you are on the Advanced version I would not use quick migration as Veeam Replication gives you way better control over the migration process.

In the end Quick Migration uses some sort of VM Replication but the failover happens whenever the data shuffling is ready.

I would do the following:
- Implement Veeam VM Replication during regular processing.
- Spread the initial replication across multiple days, so that you do not overload your storage. This is to avoid interuption in daily processing.
- Plan the Failover (there is a Failover Plan) where you can decide in what order the VMs will start at failover.
- Schedule the Failover with the Failover plan or manually start the failover. (it will replicate just the delta from the last replication run and then failover the VMs in the order you have planned.)
- If everything runs fine. Commit the Failovers.
- Create backup jobs for the new environment.


You need the following:
A Veeam Backup Server (with Veeam Backup & Replication installed).
I would install 2 Windows VMs on each of the system temporary as HotAdd proxies for data shuffling (on the new and old system).
Install Windows as VMs and add them in the Backup Infrastructure - Proxy section.

[Mi32]

Andreas,

I did not put this in my original post we are replacing the HP AMD host with the new Dell INtel host so I am wanting solution to migrate over the vms with out having to a attach storage to old systems.

I have been reading that Veeam QM can do this without much of a problem Iam just not familiar with it. Since this is different hardware the compatibility is in question

You suggestion seems like something we would implement after we get this migration to the new servers going forward for Backups and DR and Failover so I will keep that handy

Do you have any information on the how to process for the QM?

[Andreas Neufert]

You replicate or quick migrate to the different host with newer VMware version, so the VM hardware version is compatible.

Quick Migration and VM Replication with failover is the same process. Quick Migration does not create a job (one time task) and the failover time can not be controlled (it is whenever the data is migrated, if it is a good time or not).

If you have a lot of data and want to have control over the failover time then use VM Replication with Failover (or usage of Failover plan if you want to orchestrate the failover, it is very simple to do both).

For Quick Migration you need the same setup. Install 1-2 Windows or Linux VMs on each of the clusters, add them as Proxies into Veeam. Add both VMware Clusters under Backup Infrastructure and then go to Inventory and right click on the VM that you want to quick migrate and follow the wizard.

[Andreas Neufert]

I suggest to play with it a bit. You can even do this with an empty VM. Just create the VM. and then setup Veeam in the needed way. Perform migration once with quick Migrate and once with Replication + Failover + Permanent Failover. Use Naming for the VMs at target that does not include the _replica. This way you can decide which way to go and can prepare yourself for the migration.

[Andreas Neufert]

I suggest to play with it a bit. You can even do this with an empty VM. Just create the VM. and then setup Veeam in the needed way. Perform migration once with quick Migrate and once with Replication + Failover + Permanent Failover. Use Naming for the VMs at target that does not include the _replica. This way you can decide which way to go and can prepare yourself for the migration.