Search results

GRUB doesn't show the previous kernel? Else you can try to boot with the 6.2 ISO. If you start it in debug mode and abort the wizard, it will drop you on a full shell.

Well, doesn't that answer it? And try your disaster recovery plan in a VM. That allows to simulate those conditions very easily.

It is even more complicated. ;) To think about, since VF are a subset of the NIC, bond modes that involve the switch (eg. LACP) will not work. The switch doesn't have any knowledge about the VF. Though the guide mentions the use of a port channel on the switch. I suppose they mean a passive...

Not possible, see here. https://community.mellanox.com/s/article/howto-configure-lag-in-the-vm-over-sr-iov

If I understand correctly you want to access the backups of a specific VM in a separate datastore on different Proxmox VE nodes. Then you will need to add the PBS datastore as storage on the PVE node.

In any case you will have to do configuration on the VM. You can set the bridge to be vlan-aware, then it will recognize the different vlan tags.

When you reconfigure the new PBS as the original then it should be ok. If you have already a second PBS running, then you could also use a sync job for the datastore. Since often the disk dies first. ;)

You can just install an older kernel, no need to reinstall the host. Do you have some serial console port redirection (SPCR) configured? Also check that the BIOS is up-to-date and if there is some serial port settings.

If the container run on the same subnet then use a linux bridge inside the VM as well. You may need to handle STP. vmbr3 has no connection to another interface. The Linux bridge is like a switch and forwards on layer 2, meaning it doesn't care about IPs so much. Be aware that this will become...

Bitte poste die VM und storage.cfg. Und ist es ein manuell gestarteter Job oder automatischer?

They are per job. But you could query the API and send the result via email. https://pbs.proxmox.com/docs/maintenance.html#notifications

The ceph-mon log should show you the operation that takes long. Depending from which version Ceph was upgraded, the change for buffered IO could be taking effect. https://forum.proxmox.com/threads/ceph-storage-all-pgs-snaptrim-every-night-slowing-down-vms.71573/post-355081 Are you running RGW...

It depends on which IPs you changed. As the change of Ceph's public_network range can't only be done in the config. The MONs will need to be moved as well.

ZFS is only the storage for a (or more) datastore. You will need to configure PBS as before. Otherwise the owner of the datastore (id) might not exist.

Likely. Did you reboot to load the old module? And in general, better pass the card into a VM. Also the encapsulation helps not to trash the host. ;)

This is generally not a supported setup. But have a look into man votequorum.

Depends on your use-case. You can run both if you wish. vzdump is build-in and creates a full-image archive.

If they are zfs snapshots, then they are on the pool. And a zpool import <pool_name> (porbably needs -f = force) should do it.

To add, in any case (as always) you will need to keep an eye on the usage.

Keep them evenly distributed. Ceph will use different ratios for those disks and fill them accordingly.