Recent content by cyruspy

  1. C

    pve-cli (pc) — a remote-first CLI for Proxmox VE and Datacenter Manager

    hello, sure, I'm happy to receive PRs and see it being used. I've addressed the one you've reported.
  2. C

    PBS on RAIDZ2+HDD, no special file

    I had SSD for OS, tried to go the ZFS on bare disks. Failed miserably due to a kernel bug in 7.0. Move to HDD only, 3+3 RAID10 instead of RAIDZ2 (4+2). Went back to hardware RAID1 for boot.
  3. C

    PBS on RAIDZ2+HDD, no special file

    Thanks, will try to split the boot hardware RAID and use a ZFS mirrored partition as special device.
  4. C

    PBS on RAIDZ2+HDD, no special file

    Hello, I know it has been mentioned several times a special device backed by ssd is mandatory when using HDDs for data to have a bearable solution. If I don't have SSD but RAM is available (128GB), could ARC save me here?
  5. C

    SQL Server 2022 database corruption

    I asked directly, answers were very odd. Do we need our own virtio signed drivers distribution?
  6. C

    SQL Server 2022 database corruption

    It seems the original signed driver are stale. Fix was included in https://github.com/virtio-win/kvm-guest-drivers-windows/releases/tag/mm315 "pre-release and untested binary available"
  7. C

    Non PVE backup at scale

    Oh, yes. The 1:1 CLI native client for Windows is in progress. The next challenge is to fund the usd 300 yearly certificate to make Smartscreen and SecureBoot happy (MSI installer + NBD kernel driver). While thinking beyond that point is that I thought of follow up options: A- small system bar...
  8. C

    (yet another) Non official client build

    Hello, I would like to share the initiative of packaging the Linux client for different distributions as a nice opportunity to give back to the PBS creators and the community. I've repackaged the original supported client in native RPM/DEB packages for: Install Replace <REPO> with your...
  9. C

    Non PVE backup at scale

    Hello, Much to my dismay, I've came across a heavy Windows usage environment, with not all running on PVE (yet?). I would like to write a native Windows client, with proper signage and a msi installer to simplify its lifecycle. Also, I believe we need a scheduler to centralize management of...
  10. C

    Shared SSD for OS & datastore acceleration

    Hmm, I didn't see that one coming I've just shrank my original OS rpool to 50GB. Will think about it. PS: does it mean the datastore will be just a folder somewhere and not a different pool, correct?
  11. C

    Shared SSD for OS & datastore acceleration

    Yes, you are correct about the scenario. In a "let's design this and purchase this" scenario I would purchase dedicated flash storage for metadata. Is sharing the small boot disks what concerns me.
  12. C

    Shared SSD for OS & datastore acceleration

    I'm not sure I'm following. This machine is only for PBS, live data are in other computers.
  13. C

    Shared SSD for OS & datastore acceleration

    Hello!, While deploying Proxmox Backup Server (PBS) for personal backups (NAS files and PVE test VMs), I noticed that SSDs are preferred for the datastore. Since this is a "cost-effective" scenario, I'll have to use leftover mechanical disks. Would it be possible to use the two SSD boot drives...
  14. C

    Centralized scheduling for non PVE clients

    Currently proxmox-backup-client is a stateless, outbound-only CLI, and PBS operates purely as a passive storage endpoint. For non-PVE / standalone Linux hosts, backups must be scheduled locally per-host (e.g. cron or systemd timers). This creates operational gaps: - No central control or...