Search results

  1. S

    [SOLVED] PVE 7.3.3 auf TK LESv4 / 3CX VM und OPNsense VM stürzen immer wieder ab

    Hallo Thomas und herzlich Willkommen! Eine konkrete Idee habe ich noch nicht, wohl aber Stellschrauben, an denen ich drehen würde, in der Hoffnung, mehr über das Problem zu erfahren. Zum einen würde ich auf die aktuelle PVE-Version aktualisieren. Und dann würde ich, falls möglich, testweise mal...
  2. S

    How to build a new datastore storage, and push existing backups back and forth

    Hi everybody, we must build a new storage for our backups (see https://forum.proxmox.com/threads/zfs-raidz1-expanding-not-possible.127480), so I would like to copy our backups (about 30 TB) to another storage, build a new ZFS pool, and put the backups back. I successfully rsync'd...
  3. S

    [SOLVED] ZFS raidz1: Expanding not possible?

    ok, so I will buy another Disk and go for a new 2x 5 raidz1. The way I can do that I will discuss in a new thread. :p Thanks a lot for your support! Many greets Stephan
  4. S

    [SOLVED] ZFS raidz1: Expanding not possible?

    so... If I would like to stay with ZFS, I have to stripe some raidz1, correct? For example: 3 disk raidz1 vdevs: 12 disks for 8 disks of usable space 4 disk raidz1 vdevs: 12 disks for 9 disks of usable space 5 disk raidz1 vdevs: 10 disks for 8 disks of usable space And this list goes from...
  5. S

    [SOLVED] ZFS raidz1: Expanding not possible?

    Sorry, I forgot: Thanks so much for your fast replies! :) Well, basically I like the idea of a RAID 5: Some minor redundancy (it's "just" a backup storage) and a high percentage of usable storage - the more important because these WD SN640 7,68 TB are not cheap. The loss in write performance I...
  6. S

    [SOLVED] ZFS raidz1: Expanding not possible?

    wow, that's... challenging. Option no. 1 is no option, quite a bit too expensive. So I will try to find a temporary storage which is large enough for option no. 2. But: What are my future storage options? I need scalability, so raidz1 is out. Linux Software-RAID isn't supported by Proxmox. Can I...
  7. S

    [SOLVED] ZFS raidz1: Expanding not possible?

    Hi there, a few months ago we built up a new PBS with a bunch of U.2 NVMe. I naively thought ZFS must be the way to go creating the storage for the datastore. So I created this storage: # zpool status nvme-pool pool: nvme-pool state: ONLINE scan: scrub repaired 0B in 04:34:39 with 0...
  8. S

    [SOLVED] offsite backup (once again)

    wow - good to hear that PBS is scaling well. :D I mark this thread as "solved" and looking forward to see this feature in the enterprise repos.
  9. S

    [SOLVED] offsite backup (once again)

    that sounds great, thank you! Is there an ETA for it? I know, most annoying question from sysadmin to dev. :D
  10. S

    [SOLVED] offsite backup (once again)

    Hi, since a couple of months we have a PBS which works like a charm! It's a dedicated server hardware with a bunch of U.2 NVMe disks, one datastore with five namespaces and different retention strategies. In total about 42 TB of backup data - upward trend. :) Now we would like to do some kind...
  11. S

    Windows Server update causing boot issues with VirtIO SCSI

    wow, your're right! "... when required" seems to do nothing, when there is already some driver installed. Thanks for your research. I did some further trial & error and figured out that if I deselect "Qemupciserial" ("Entire feature will be unavailable") the installation wizard installs the...
  12. S

    Windows Server update causing boot issues with VirtIO SCSI

    We ran into this recently. Our workaround goes like this: During the installation wizard, when all components are listed, select "Feature will be installed when required" for every component. We did a quick research and found hints that one of the components, which is required almost never, is...
  13. S

    [SOLVED] moving backups to another namespace

    Yeah, thank you - that worked like a charm! Greets Stephan
  14. S

    [SOLVED] moving backups to another namespace

    Hi there, since a couple of weeks we're testing PBS to be our future backup solution. So far, so great! :) For some minor topics I would like to look for answers here - here we go: Currently we focus on backup the VMs running inside our 3-node-PVE/Ceph cluster. From the beginning we threw...
  15. S

    Proxmox VE 7.2 released!

    Hey, we had no issues upgrading our three node PVE/Ceph cluster to 7.2 (except for some minor dependency foo during the upgrade process). Our systems based on Supermicro mainboards with AMD EPYC CPUs. Greets Stephan
  16. S

    Upgrade to 7.2: unmet dependencies

    Hello everyone, today we upgraded our three node PVE/Ceph cluster from 7.1 to 7.2. The first attempt of apt dist-uprade ended up with Errors were encountered while processing: /tmp/apt-dpkg-install-0DYbqq/46-libproxmox-rs-perl_0.1.0_amd64.deb E: Sub-process /usr/bin/dpkg returned an error...
  17. S

    server hardware recommendation for PBS with about 50 tb usable storage

    thanks again! Ok, when mdadm isn't supported by Proxmox, it's not an option for us. So ZFS is king, isn't it? And from the few replies I conclude that my hardware suggestion isn't that bad. :)
  18. S

    server hardware recommendation for PBS with about 50 tb usable storage

    Thanks for this info! In fact I have almost no experience with ZFS so far. Is this basically the way to go when it comes to building local storage with multiple devices? Until now mdadm is our tool for that. :) And what about the NVMe devices? Are these WD devices suitable? Is there a cheaper...
  19. S

    server hardware recommendation for PBS with about 50 tb usable storage

    Hi there, we're planning a new backup server (migration from Bareos to PBS) including new hardware. Therefore I would like to throw the following setup into discussion: https://www.thomas-krenn.com/loadproduct?id=y4cd0fdaaa218617b&lang=de in short: CPU: 1x AMD EPYC 7343 RAM: 64 GB DDR4-3200...
  20. S

    Issue with upgrade from 7.0 to 7.1

    Hey, and I just noticed that on November 18th you tried apt upgrade dist... Did you really want to install/upgrade the package dist, or was it a failed attempt to do apt dist-upgrade? Nevertheless I don't know exactly how to resolve the current situation concerning the two packages held back...