Search results

https://pve.proxmox.com/wiki/High_Availability#ha_manager_start_failure_policy -> Shutdown policy

P440ar ? It's not real HBA controller, maybe problem is there...

Create Datacenter -> Storage item with that 10G subnet and select backup option.

DMARC etc need to point to server, which is sending the mail, so mailservers. There is no cost to having PMG in those records too anyway. For certificates, the right way is such that works in long run.

You cant't evade not using swap when swap is present. You can set swappiness parameter, remove swap, raise RAM, or more debug the problem.

You can do tests. From my point of view mixing 1500/9k mtu on same interface is calling for problems. I tried something as this before even ceph was in pve and it was mess. Network latency will have higher performance impact than 9k mtu.

Yes, it's the other way to upgrade (aka, more complicated).

For OP: 4. Rook or any configuration management solutions Anyway, we are calculation external Ceph storage for our PVE too. PVE Staff, are there some requirements for external clusters? For example, version difference etc? PVE documentation handles hyperconverged/updates mainly.

Yes, soft option can be used.

Read documentation. Search forum. Analyze your requirements. Test your setup. etc etc Do your job or pay some skilled engineer.

ceph documentation

Not from PVE side. You need implement something as STONITH (locally or remotely), for example shutdown the affected node.

If you aren't skilled with ceph, the better way will be 1 osd per ssd.

There nfs works. INFO: starting new backup job: vzdump 101 --node proxmox-backup-01 --storage nfs-backup --remove 0 --compress zstd --mode snapshot INFO: Starting Backup of VM 101 (qemu) INFO: Backup started at 2021-10-21 12:19:19 INFO: status = running INFO: VM Name: REDACTED INFO: include...

Use processor type Host.

Previous image is zabbix standard disk template. Even netdata shows something crazy for VM system disk: And VM db data disk: Both disks are on this PVE host, dedicated raid for VM images: PVE OS raid diskset: All VMs are Debian 10. Upgrade was done only on PVE host level.

Hi, we upgraded our PVE cluster (very old HP G7 and 3yr old Dell R940) 6.2 to 6.4 and disk utilization in VMs raised from floor. This problem is same for VMs on: - nfs ssd storage (raw files), default (no cache) - local ssd disks (LVM thick), default (no cache) The change depends on VM...

Thanks. I used way 1]. All without any hiccup.

Hi, one of my cluster nodes hard failed due failed disks in raid. Now because cluster is 6.2, we decided to upgrade to 6.4 (needed req for 7). Reinstalled node will have same fqdn as failed node. Now i have two possible ways: 1] remove failed node from cluster (aka cleanup) and add reinstalled...

Use install ISO or any iso with recovery/repair mode.