Hi,

I have 2 servers Proxmox with ZFS as storage.

I create 1 CT with 1 root disk on SSD ZFS and 1 mount point on the HDD ZFS

I create a replication rule on the 2nd serveur : all is OK !

I do the "same thing" with another CT, but I have always the following error :

2024-11-09 13:55:11 5201-0: start replication job
2024-11-09 13:55:11 5201-0: guest => CT 5201, running => 1
2024-11-09 13:55:11 5201-0: volumes => local-zfs:subvol-5201-disk-0,zdata:subvol-5201-disk-0
2024-11-09 13:55:11 5201-0: end replication job with error: No common base snapshot on volume(s) local-zfs:subvol-5201-disk-0,zdata:subvol-5201-disk-0
Please remove the problematic volume(s) from the replication target or delete and re-create the whole job 5201-0

I try to delete all snapshot, I have destroy and create again my CT, no snapshot found relative to 5201 with zfs list -t snapshot.
I create once again the replication rule : same error.

This error (bug ?) is on Proxmox 8.2.4 and also I have the same problem with another cluster with same Proxmox

I don't understand what is wrong !

Please can you help me ?

Thanks, but I have already delete and re-create, but still the same error

Exact same here.
I was not even able to remove the job, I had to use --force in the CLI.
Then took a snapshot as a base and recreated the replication Job.
Still the same.

Solved.

I migrated the VM back to it's original server, and setup the replication again.
That did the trick, it replicates fine now.

But I'm not wiser now ;-)
I don't know why it happened. Also checked if disk full or other disk problems, but none.

So, if anyone can tell me what the problem is with this error message, I would much appreciate.

Proxmox, I have bug on bug, nothing pro with it :-(

I'm no longer looking for help, I'm disappointed by the bug after bug that we encounter for nothing, on freshly installed and up-to-date servers... I see a spectacular deterioration in the functioning of software over the last 15 years... That's all LOL

I had the same problem and solved it by deleting the ZFS volume on the target replication device.

I had the same problem and believe it was caused by a power interruption on a switch during replication. Deleting the target replication device allowed the next replication to work smoothly. It would be prudent to have a fresh backup when you do this.

Is there any option to force an initial resync without removing the replication job? I don't want to recreate tens of sync tasks manually.

> Is there any option to force an initial resync without removing the replication job? I don't want to recreate tens of sync tasks manually.

Same here. Everytime I reboot a node I get multiple failed replication that I need to delete (it takes forever) and recreate manually.
And since the replications have multiple destinations and various frequencies, it's really a pain.