Search results

  1. Jackobli

    VM not responding during Backup

    We are seeing applications / vms not responding during backup. We assume, that this is in between the "fs-freeze" and "fs-thaw"? How could we minimize this time or avoid the issue? Setting: Cluster with 6 physical servers (only four are have vms to back up at the moment), Network is 25 GbE...
  2. Jackobli

    zfs, loosing raidz-members due to reboot

    Might be, but one disk was added newly to be sure, the first crc errors were not due to a disk error. the other one was just zapped (cleared) and re-added through zpool replace. I did not remove the existing zfs partitions nor wiped out the whole disk. Destroying a label of a zpool member seems...
  3. Jackobli

    zfs, loosing raidz-members due to reboot

    IMHO, there are the usual partition layouts on that disks. This has to be numberings, as the original /sdg or /sdh were still seen when the first replace begun. I would need to double check tomorrow. But lsblk is showing on every disk a small first partition (used for metadata imho) und the...
  4. Jackobli

    zfs, loosing raidz-members due to reboot

    Hello Unclear behavior most probably hardware related, may be config related. Supermicro barebone with 8 x 3.5 " SAS disks on LSI SAS 3008 in IT-mode. While reboot, the raidz looses the devices on phy 6 and 7. They appear as "faulted" with a number insted of device. Example: config: NAME...
  5. Jackobli

    PVE 7.2.7 suddenly one bond does not up after reboot

    Sorry for the long wait. We inspected the case very close and it never happened after. Perhaps this was caused by a OS Patch. Anyway thanks for all the advises.
  6. Jackobli

    PVE 7.2.7 suddenly one bond does not up after reboot

    Ok, yesterday we patched all nodes and they came up without a flaw. Our network engineer told, that he will check if there is perhaps something different on the switches which the system engineers didn't found. We'll keep an eye on it and will follow up.
  7. Jackobli

    PVE 7.2.7 suddenly one bond does not up after reboot

    Sorry, this is a copy paste error. It is absent in the original file on the server.
  8. Jackobli

    PVE 7.2.7 suddenly one bond does not up after reboot

    Will need to reboot the nodes to see, if it happens and to go into the journalctl -b, at the moment I don't see any useful infos in the logs of the 2 machines that have been rebooted. Just very early: Aug 02 17:04:07 MY-HOSTNAME kernel: bnxt_en 0000:85:00.0 (unnamed net_device) (uninitialized)...
  9. Jackobli

    PVE 7.2.7 suddenly one bond does not up after reboot

    Hi folks We are running a six member cluster with a several network connections trough enterprise grade switching. GbE (copper) for HA 2x2 Port SFP28 to two Switches as Bond (LACP 802.3ad) one bond for Data/Mgmt one bond for Storage This setup worked well until about two or three weeks...
  10. Jackobli

    Move Backup datastore from one ProxMox Backup Server to a new one

    Thank you, worked well. But we were in a hurry and on some machines, the new backup already took place on the new PBS. So the old backups couldn't be synced. Tried to fumble around with rsync and took a zfs snap before (to my good) on the new storage. I was unsuccessful and needed to rollback...
  11. Jackobli

    BONDING configurations issues

    Yes, your correct. Please tell model and config of switch. We're running such config with two Cisco Nexus 93xx and working well.
  12. Jackobli

    Move Backup datastore from one ProxMox Backup Server to a new one

    Sorry, I'm sure that this question has been answered but I'm perhaps to stupid for google or search. How exactly is the recommended way to move from one PBS to a new one? As I think to understand: Given ProxMox PVE are using PBS-OLD : DataStore-OLD Setup: PBS-NEW Create a Datastore on PBS-NEW...
  13. Jackobli

    Adding NFS Share as Datastore in Proxmox Backup Server

    Why are you thinking, that PBS backups «free» space? Use the function «mail» in the settings to send a report to yourself, there you find useful infos about the backup process itself. Like how long it did run and also about which disk/dirty bitmaps did get backup up. The status page of the vm...