Rudder

Hello Noelle,

People generally does that at DNS level (ie use a name in policy_server.dat and make the switch in name resolver).

If that option is not possible, you can configure a file enforce technique content with the new IP and see agent go from one server to the other. Be sure to have a fallback solution to still be able to connect to your node if something goes wrong.

Depending of the logic of you migration, you could create a technique with some fallback logic, like "condition from command => try curl -k https://ip_in_policy_server.dat/uuid => if != 0 then retore old IP".

Just to be sure: you are copying the old server into a new place, or is it a new installation ?

If it's a new installation, the proposed solution won't work: server keys will be different (see https://docs.rudder.io/reference/5.0/administration/procedures.html#_migration for further action to do in the node), and the node will need to be accepted in the new server so a "rudder agent inventory" must follow the migration.