when replasing the WM with another with same same name and ip

[Tommi]

hi everyone.

i have a question, hope its not too dumb.

i have a fileshare server called xxx, running windows 2012 r2 (old i know) i am planning to migrate to a new windows 2019 server, for that i am using the service " storage migration service"
the service copy the files and shares from the old server and then,, and here it comes,, it replace the old server name and IP, taking over its place.

så now the new server is stil called XXX with same IP as the old server,,, and the old server is shut down.

how would Veeam backup react to this ?? what would happen when veeam try to run its backup of the job " server xxx" .. `?
what would be best practice to prevent veeam from going nuts ?? how how would i add the new server " with same and and ip" to veeam.

hope you understand my question,,

cheers
Tommi.

[Andreas Neufert]

For the VM backup, we work with an VM identification ID (moREF) from VMware. If you rename a VM it is still backed up. If you delete and recreate the VM, this is a new VM and you have to add it to the job again.

Out Job UI shows the names, but we work in the background only with the IDs.

[Tommi]

great thanks for info, apriciate it

cheres
Tommi

[bizunesh]

let me one question
Exception of type 'Veeam.Backup.AgentProvider.AgentClosedException' was thrown?
Thank you

[Andreas Neufert]

Please open a support ticket and upload logs. It is hard to say.