<![CDATA[CBR start operation is blocked]]>Hi guys.
I am currently testing Continuous Replication as our way, to migrate our vms from one pool, to another. So i set up a test vm and a replication job on the same pool (different sr), since i dont have the new pool yet. Everything worked fine, job is running and creating the replicated vm. But when i want to start the vm, i will get the warning "Forbidden operation Start operation for this vm is blocked." I could klick "force start" but i am afraid, the universe will dissolve. So what is the best practice for my task? Do i have to recreate the vms and attach the cr disks, or is there a way to unblock the cr vm and use it as the new vm? I will have to migrate about 30 vms with 15TB so i obviously dont want to clone the cr vm to a new one. Or do i?

Kind regards

Milenko

]]>https://xcp-ng.org/forum/topic/12251/cbr-start-operation-is-blockedRSS for NodeMon, 01 Jun 2026 12:50:40 GMTMon, 01 Jun 2026 10:36:25 GMT60<![CDATA[Reply to CBR start operation is blocked on Mon, 01 Jun 2026 12:50:26 GMT]]>I think that blocked start is actually on purpose rather than something gone wrong: XO guards a continuous-replication target, so you can't accidentally boot the replica and have it drift from the source while the job keeps running.
The documented way to bring one up is the failover process (https://docs.xen-orchestra.com/xo5/incremental_replication#failover-process), and for a real cutover, that's just starting the replica on the destination side; there's also a tip there about making a copy first if you want to start it without breaking the CR job on the source.
So, for your pool-to-pool move, I don't think you'd need to recreate the VMs and reattach disks; the failover flow is meant for pretty much exactly this.

I'd test the whole cycle on your one VM before committing the other 30.

]]>https://xcp-ng.org/forum/post/105867https://xcp-ng.org/forum/post/105867Mon, 01 Jun 2026 12:50:26 GMT