Search results

  1. S

    Route failover IP to container

    Closing this. The setup seems to work and I did not get complaints from Hetzner. Thanks for your help.
  2. S

    ERROR ZFS REPLICATION

    This is very likely a performance problem. I am seeing this occasionally myself on systems with HDD. If you are Replicating bidrectional, it might help to prevent overlaps. If server A replicates to B while B replicates to A, it might be good to have this separated. After I did this, I get the...
  3. S

    Route failover IP to container

    Thanks for the hint with the proxy_arp. I have added this to the configuration. About the IPs: sorry for the confusion, these are not the real IPs as mentioned above the config files, but I agree: The replacement was more than unsuitable. I will edit the configs above to reflect this. Thanks for...
  4. S

    Route failover IP to container

    Hi Wolfgang, thanks a lot for helping out! Meanwhile I have resorted to a much simpler configuration in which I created a new vmbr interface for the failover IP and configured rinetd to foward ports 80 and 443 to the container vm (instead of iptables forwarding because it is only about a dozens...
  5. S

    Route failover IP to container

    Hi everybody, I am totally lost with a problem that bugs me since a couple of days, but despite reading numerous posts/sites, I wasn't able to solve it (Sorry in advance if this was answered here somewhere and I just didn't get it) We have a small two-node Proxmox cluster runinng Proxmox 6.2...
  6. S

    [SOLVED] Help with replication/migration problem

    Yes, of course. As the error message indicates there are leftovers from the broken replication process. I wasn't sure if I can delete those directly from the filesystem without messing Proxmox up, but as it seems, it works. I deleted the remains on the target server with: zfs unmount...
  7. S

    [SOLVED] Help with replication/migration problem

    Nevermind, I decided to be brave and try out what I thought should be the proper solutions and I seem to be lucky today :) Replication and migration are working again. Anyway, thanks for listening.
  8. S

    [SOLVED] Help with replication/migration problem

    Hi, I am facing a problem after the replication between two nodes hung up. I am now seeing the following error when trying to migrate the two containers which were being replicated when the replication stopped working. Please bear with me, I am long time Linux user, but new to zfs. Can you...
  9. S

    [SOLVED] QDevice or two_node on 2-node cluster without HA

    Hi Thomas, thanks a lot for your quick reply. This was exactly the information that I was missing. Best regards!
  10. S

    [SOLVED] QDevice or two_node on 2-node cluster without HA

    Hi, please forgive me if the following question was answered already and I just didn't get it when reading all the posts. What I have is a small 2-node cluster without HA. There are different suggestions to ensure that the remaining node keeps running in case that one node goes down. Mainly...

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!