I don't think so because the sourcecode contains these hits:
find /usr -type f -exec grep bridge-disable-mac-learning {} +
/usr/share/perl5/PVE/INotify.pm: 'bridge-disable-mac-learning' => 1,
/usr/share/perl5/PVE/INotify.pm: $done->{'bridge-disable-mac-learning'}...
I wonder how to enable the bridge-disable-mac-learning feature within SDN?
According to the sourcecode it should belong to the bridge object but trying it like this (see below, some line from /etc/network/interfaces) doesn't work.
auto vmbr27
allow-ovs vmbr27
iface vmbr27 inet manual...
I want to add/remove the MAC addresses of my VMd during start/stop to ovs. I think I need to create a hookscript and make calls like
ovs-appctl fdb/add <OVS_BRIDGE_NAME> tap<VMID>i<NETNUM> 0 de:ad:be:ff:00
I could parse most information with a call to
qm config <VMID>
but maybe some of the...
I tried to debug an ARP issue and want to use the command ovs-appctl ofproto/trace vmbr0 as described here. But the command failed with:
root@xxx:~# ovs-vsctl --version
ovs-vsctl (Open vSwitch) 3.1.0
DB Schema 8.3.1
root@xxx:~# ovs-appctl ofproto/trace vmbr0
syntax error at vmbr0 (or the bridge...
You can take a look at https://github.com/lae/ansible-role-proxmox. Even if you don't want to use the ansible part, there's exactly the code you're looking for included.
You're right, the option "Verify new snapshots" is set to "Yes". And I already made a new test backup with the "Protected" Checkbox to "Yes" without an error.
I think it should work nevertheless the "Verify new snapshots" at the server...
Thanks for the help!
Ok, I made a new backup and get these logs:
INFO: starting new backup job: vzdump 83010 --storage horst --notes-template '{{guestname}}' --mode stop --protected 1 --remove 0 --node hugo
INFO: Starting Backup of VM 83010 (qemu)
INFO: Backup started at 2022-10-13 13:21:14
INFO: status = stopped...
Starting a backup within the proxmox ui to a pbs storage and enabling the "Proctected" checkbox I get the following error:
INFO: backup is sparse: 216.12 GiB (84%) total zero data
INFO: backup was done incrementally, reused 234.97 GiB (91%)
INFO: transferred 256.00 GiB in 222 seconds (1.2...
And just for reference, use zdb -Lbbbs POOLNAME to determinate how big your special vdev. Level 0 ZFS Plain File and Level 0 zvol objects do NOT go to the metadata SSD, but everything else would.
I will give it a try soon, just need to get more disks to make some tests.
Not being able to remove the special vdev device makes testing not easier... But since this is a new setup I can try diffent things. The (s)log device really doesn't help, I currently monitor the iostats with "zpool iostat pbs01 -vly 1" which seems pretty informative.
The "special" vdev device...
Are you talking about the new "special" device vdev? I already added a (s)log vdev to the pool, but just looking with atop what's going on everything seems to be more or less idle..
PS: I will try the special vdev.
I just created a new proxmox backup server and made my first test. The backup storage consists of 4 vdevs with a raidz1 that is build with 3x 18TB Seagate EXOS (ST18000NM000J) HDDs. I also add a log mirrored vdev that uses two Intel Optane NVMe. The network is a bond of two 10GbE cards. The...
The first time just uncheck und checked the "Enable" option but without leaving the dialog. Seconds try is with leaving the dialog and now the jobs.cfg was created and the old entry was removed from vzdump.cron.
Ok, thanks for the hint. But it seems that just using the GUI doesn't create the jobs.cfg file if an vzdump.cron exisits. Just checked. With pve-manager/7.1-10/6ddebafe (running kernel: 5.15.19-1-pve) running.
I'm searching an official way to create an entry in /etc/pve/vzdump.cron to add a PBS backup job. I already use pvesm to create the PBS server via cli but I can't find any documentation how to add something to vzdump.cron.
I don't know if it's related. But that a look at Bug 1738839 - I/O error when virtio-blk disk is backed by a raw image on 4k disk. I had the described IO errors within a Debian based VM that uses ZFS as storage. Using the ZVOL outside the VM didn't trigger these IO errors. And it only occurs...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.