Search results

I am closing this thread and using https://forum.proxmox.com/threads/change-of-proxmox-backup-client-output-makes-cron-annoying.112728/#post-486872

I'm not sure of the syntax. which of these should be used ? export PBS_LOG='error proxmox-backup-client' # or export PBS_LOG='error'

try this: # m5300 auto bond21 iface bond21 alias bond21 on swp21 bond-slaves swp21 clag-id 21 mtu 1500 bond-miimon 100 bond-mode 802.3ad bond-xmit-hash-policy layer3+4 then there are the different macs to use for peerlink.4094 etc.

the config is slightly diff. there are important differences.

here are the /etc/network/interface files for our lagged two switches

I also liked the idea of Debian on a switch - until Nvidia bought Mellonax and dropped software upgrades [ stuck on deban 10 ] for many switches including our two very expensive ones. they are speed 40 and not 100 so just dropped . I could post our working interface files so you have an...

we ended up getting these switches working. what part are you trying to set up?

hello e100. 04:34:46 with bandwidth limit 150G was the fastest backup on the your post today. was that a typo? If not a typo then why not go with 16 workers and bw limit 150? [ yes i should have re read the entire thread .... ]

hello e100 - there are updates to zfs and a bunch of other packages today. hopefully those help with the issue you ran in to. from apticron: The following packages are currently pending an upgrade: e2fsprogs 1.46.5-2~bpo11+2 e2fsprogs-l10n 1.46.5-2~bpo11+2 libcom-err2...

Perhaps there is a way to use a newer [ systemd related or something ] logging method , with an email only when a backup failure occurs .

fbc-all-servers-crond:05 06 * * * root nice /fbc/bin/fbc-sleep-15-min ; ionice -c 3 /fbc/bin/pbs/pbs-servers | grep "had to backup" | /usr/bin/logger -t BACKUP the script sets variables then ionice -c 3 proxmox-backup-client backup etc.pxar:/etc var-www.pxar:/var/www...

running proxmox-backup-client from crontabs we want to know if there are errors errors go to an email, standard output to a log file with a recent update to Version: 2.2.5-1 we are getting standard output to emails . for example: Starting backup: host/nextcloud/2022-08-03T14:12:10Z...

all backups worked after the reboot.

pve2 - the node that had backup issues some hours before the backup fail - also had some trouble when it was rebooted for the upgraded kernel to be used . after pve2 restarted the 4 lxc's that use HA - and were trying to migrate back to pve2 had this error task started by HA resource...

we ugraded on Fri 5/6/22. after that some backup issues started to occur. we have 5 nodes, each have a mix of kvm and lxc. Friday on one node all 7 lxc backups failed. the backup was to local storage, [ Also on Friday all PBS backups worked. ] I tried to backup one of the lxcs...

Hello I am seeing this: fast migrations as a system is moving vms prior to reboot. slow migrations are seen when the vms migrate back after reboot.

migration:insecure solved the issue. 30 secs: ask started by HA resource agent 2022-02-06 12:39:15 starting migration of VM 216 to node 'pve11' (10.1.10.11) 2022-02-06 12:39:15 starting VM 216 on remote node 'pve11' 2022-02-06 12:39:16 start remote tunnel 2022-02-06 12:39:17 ssh tunnel ver 1...

Hello Spirit ! bandwidth is 40G . connect-x5 cards, 2 mlaged mellonax 40G switches. I'll test migration: insecure

Okay so the issue is slow MEMORY as that vm has 32GB . I thought it was slow disk transfer. so perhaps there is no way to get around the slow memory transfer? Is it possible to set some vm's to shutdown migrate and start? just a few vm's like phone and main database require live migration.

this vm takes over 15 min to migrate bootdisk: scsi0 cores: 4 lock: migrate memory: 32765 name: imap net0: virtio=72:3B:6D:47:A5:CB,bridge=vmbr3,tag=3 numa: 0 onboot: 1 ostype: l26 protection: 1 scsi0: nvme-4tb:vm-216-disk-0,discard=on,size=16G,ssd=1 scsi2...