[SOLVED] Unable to replicate new VM to new Node

cbarbie

Member
Aug 24, 2021
5
1
8
I have successfully setup replication before, but this time I am unable to figure out the issue.

I am trying to replicate new VM (105-OpnSense) on node ProxMoxD to a new node on my Test cluster, ProxMoxC.
1715596162009.png

Both nodes have a ZFS pool called VMs.
1715596183085.png
1715596193242.png

I can ping the cluster IP address and the node addresses from each node to all of the other nodes.
1715596209871.png

The replication job is failing with exit code 255, which seems generic.

2024-05-13 05:29:02 105-0: start replication job
2024-05-13 05:29:02 105-0: guest => VM 105, running => 0
2024-05-13 05:29:02 105-0: volumes => VMs:vm-105-disk-2,VMs:vm-105-disk-3
2024-05-13 05:29:04 105-0: (remote_prepare_local_job) storage 'VMs' is not available on node 'ProxMoxC'
2024-05-13 05:29:04 105-0: end replication job with error: command '/usr/bin/ssh -e none -o 'BatchMode=yes' -o 'HostKeyAlias=ProxMoxC' -o 'UserKnownHostsFile=/etc/pve/nodes/ProxMoxC/ssh_known_hosts' -o 'GlobalKnownHostsFile=none' root@192.168.1.226 -- pvesr prepare-local-job 105-0 VMs:vm-105-disk-2 VMs:vm-105-disk-3 --last_sync 0' failed: exit code 255


Is there a log that would give me additional details?
Am I missing something obvious?
 
Both nodes have the same ZFS pool.
1715599114262.png
1715599140186.png

The pool showed up here before I added ProxMoxC (target) to the cluster:
1715599199715.png
After adding ProxMoxC to the cluster it disappeared.

If I try to add the storage in Datacenter, I get this:
1715599355084.png

I was able to add VMs_C, but replication still failed with the same 255:
1715600823265.png
 

Attachments

  • 1715599840232.png
    1715599840232.png
    119.7 KB · Views: 8
  • 1715599868819.png
    1715599868819.png
    119.7 KB · Views: 7
  • 1715599901995.png
    1715599901995.png
    119.7 KB · Views: 7
  • 1715599934308.png
    1715599934308.png
    38.3 KB · Views: 8
  • 1715600781332.png
    1715600781332.png
    18 KB · Views: 6
Last edited:
The storage is not active on both nodes.

The steps to create the zfs storage are:
  1. Create ZFS on first node. "Add Storage" has to be checked.
  2. Create ZFS on second node. "Add Storage" must NOT be checked.
  3. Go to Datacenter > Storage. Edit your new ZFS storage. In the field "Nodes:" add the second node.
  4. Enable "Thin provision" to get thin provisioned VM HDD images.
 
Last edited:
The storage is not active on both nodes.

The steps to create the zfs storage are:
  1. Create ZFS on first node. "Add Storage" has to be checked.
  2. Create ZFS on second node. "Add Storage" must NOT be checked.
  3. Go to Datacenter > Storage. Edit your new ZFS storage. In the field "Nodes:" add the second node.
  4. Enable "Thin provision" to get thin provisioned VM HDD images.
One little check box made all the difference! :D

Thank you!
 
  • Like
Reactions: Azunai333

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!