Search results

Your disk/raid setup is strange. 1] /dev/sdb as raid6 on Perc 2] fio filename is /dev/sdd <<--- ??? 3] errors are from /dev/sdd and sde <<--- ???

You need add new VM datastore name when you removed original local-zfs datastore name.

Datacenter -> nodename -> >_ Shell

You misread backup log. Backup failed because VM is not running, not otherwise. Check logs.

node1->node2 & node1->node3 vs dual 10G LACP are in theory same througput you can move pve management to ens19&20 bond and use 2x1Gbps links unbonded for corosync. You can use mesh in 3 nodes. But when you will want add more nodes in future, it will limit you.

Hiding default port on different number is security by obscurity. I think, we need root password in cluster join, if i remember correctly (it's some long time, when i created new cluster).

What will be use of the nfs server? templates only? VM storage?

Do you think, ceph = zfs? https://pve.proxmox.com/wiki/Performance_Tweaks#Disk_Cache MTU 9k doesn't have such effect as you think (and has some own problems). Where are your performance tests? What's your ceph config?

Proxmox backup server.

Proxmox 5.x is EOL. You need 6.x at least.

Old and new subnets are same vlan or different? The main rule is, multiple public_network need to be able to communicate. You need to reconfigure monitors, so it's important to read documentation (and in some cases, test such migration).

Configure server with ip 192.168.75.2 what to do with sender as noreply@mydomain.org.

asymetric routing?

Two points: 1a] in one-bond mode if bond fail, you lost all conectivity 1b] in two-bond mode if one bond fail, you still have something left (usabiliy depends...) 2a] in one-bond mode bond sides select, what iface will be used to send datastream 2b] in two-bond mode admin decide, what ifaces...

arp/mac cache on switch/firewall

hdparm and dd are useless for testing.

PVE lvm configuration != VM lvm configuration

DMARC.

I don't have experience with iscsi/lvm versions, so i only suggest to check, if this type of storage require "shared" flag for cluster-wide.

Nothing specific now. I can only suggest this for now: 1] monitor sys values 2] regular fast checks nfs availabilty 3] regular fast checks datadisk availabilty 4] regular fast checks raid controller raid availabilty For now it looks as not problem with performance, but with size. And because...