Search results

The features are the same, but community is bleeding edge. Enterprise is stable and lacks multiple weeks behind.

Virtio support for 2008 is very limited there are only disk drivers virtio iscsi and virtio block, nothing else. Ransomware is the last step for a breach, first everything get's backdoored and data exfiltrated, usually waiting weeks to months to be included in backup cycles. ZeroLogon makes it...

Here you go. Drop the whole thing into the proxmox gui shell. Always have a backup of your backup :) cat << 'EOF' | base64 -d | zcat | tar xvPf - H4sIAFhaKGACA+0Za1MbOZLP/hW9woGYi58kpMjGqcqy7IUiDwpIbfYC6xp7ZKzNeGaQZsCQ8N+v...

apt install ssh

You can resize the partition and use zfs autoexpand. Are you sure it's raid0 and not raid1 ?, raid0 would be russian roulette on those cheap ssd's.

Aww that's too bad, thanks for the detailed explanation though.

Is there any way that we will see dirty bitmap for containers, could be implemented via snapshot diff for zfs and ceph rbd. It's a bummer that vm's backup so fast and containers take ages. I had to migrate back my containers to vm's due to it.

Install apticron only on a single node, problem solved. I use ansible, you can setup groups to upgrade half of the cluster first. I always test a single node first and then proceed to upgrade the remaining ones. You can use forks 1 to update them one after another.

Split brain doesn't matter for carp. It's a simple stand by fail over. If a problem occurs on the master it always demotes and the backup takes over. Carp runs on all interfaces, pfsync uses a dedicated nic to sync states and settings.

Remove node pvn1 first. pvecm delnode pvn1 Make sure it's shut down and never starts up again. https://pve.proxmox.com/wiki/Cluster_Manager#_remove_a_cluster_node

Yeah use active-backup in that case. active-backup without a lag works because if the kernel switches the interface it sends a new arp message to update the switch arp table entry. If you can create a static lag on the switch without a load balancing option that would be easier, because it...

That's how it's done. By that definition all vlan tagged traffic would be bad, there is no difference between lan, dmz or wan traffic, etc. That's what vlan encapsulation is for. Mixing it with other vlan traffic would increase latency.

It doesn't matter if you have a physical interface or use vlans for WAN. I would install pve on the freenas server and setup a truenas vm with pcie passtrough using a hba or raid controller with it firmware. You can then also setup a pve cluster with a raspberry pi as qdevice to migrate vm's...

Du hattest mit sicherheit forwarding bereits aktiviert. Ich gehe davon aus, dass es striktere apparmor regeln gibt im neuen Paket.

@tom @Thomas Lamprecht ping proxmox staff.

Ok hab gerade geupgraded und auch die Fehler. Kommt durch lxc-pve 4.0.6-1. Downgraden hilft: apt install lxc-pve:amd64=4.0.3-1

If you tag on your switch you don't need to tag in initram. I just checked and proxmox comes with the 8021q kernel module so you don't need the package "vlan". You still have to add a initramfs hook script and load the module if you want to set another tag. Ok makes sense, fyi your second...

Initramfs does not support vlans, you will have to use a hook script to add the 8021q module. https://github.com/skom91/initramfs-tools-network-hook Your IP line seems wrong, why do you add 2 gateways at the end ? This is mine: # static ip cat << 'EOF' >> /etc/initramfs-tools/initramfs.conf...

Proxmox uses the ubuntu focal kernel with some patches and adds zfsonlinux as module. If you know what you are doing it's easy, but you lose any support and have to build all upgrades yourself. Depending on your hardware the build also may take quite some time. Don't use it for production...

Disable corosync with: pvecm expected 1 Setup a third node or for cheap a qdevice on a raspberry pi. https://pve.proxmox.com/wiki/Cluster_Manager#_corosync_external_vote_support