Hello. Thank you for your input. I am aware, that this is more of a warning message, than a error. I´m just trying to figure out, what is my best way to go here.
My plan was:
Setup a repljob for the vm in a lets say hourly interval
On the day of the migration, shutdown the vm and start the last replication manually
Disable the cr job
Start the replicated vm on the new pool, check it and if all is ok, use it as new vm, otherwise start the old vm.
The documentation says "If you want to start a VM on your destination host without breaking the CR jobs". Tbh i dont care about breaking the job. If everything works fine, i dont need it anymore, if not, i can setup a new job pretty fast. I was just wondering, if the new vm will stay in "blocked mode" for ever.
Kind regards
