...
Migrating to another datacenter or another node, is basically like any other VM. If there is the same virtual network infrastructure there, nothing needs to be done as far as Switchvox is concerned. If not, then it needs to be treated as any other VM and have the IP updated and any other network pieces that the customer has in place.
How to proceed with the migration
In our example, we are considering having our Switchvox on IP address 10.10.26.2, running on the node with IP 10.10.9.51 and we are going to move it to another host with IP set to 10.10.9.58
Step 1: Right click on your VMware (SWVX1 in my example)
...
Step 3: Select a migration type.
You can either move to Compute resource or storage or both. It depends on how you are using the VMware.
If your storage is in a shared storage, so you can only move compute resources.
...
In our example we use Change both
...
Step 4: Select a Compute resource
Click next once selected and you will see compatibility checks succeed if your choice is compatible with it.
...
Step 5: Select Storage
You should see compatibility checks succeed.
...
Step 6: Select Networks
Click next and select the network. Check the Compatibility text area to confirm all checks succeeded.
...
Step 7: Select vMotion Priority
...
Step 8: Ready to complete
You will be presented with a summary to confirm all the choices made.
...
Step 9: Finish
Thus will start the effective migration
...
When the migration process completes, Switchvox migrated machine will show the same old IP address it was running on the new host 10.10.9.58.
Some useful Veeam document
https://helpcenter.veeam.com/docs/backup/vsphere/replication.html?ver=100
https://helpcenter.veeam.com/docs/backup/vsphere/surebackup_job.html?ver=100
https://helpcenter.veeam.com/docs/backup/vsphere/recovery_verification_surereplica.html?ver=100
https://helpcenter.veeam.com/docs/backup/vsphere/data_recovery.html?ver=100
...