Rocket Surgeon

  • 3 Posts
  • 22 Comments
Joined 5 months ago
cake
Cake day: March 10th, 2025

help-circle
  • dbtng@eviltoast.orgOPtoProxmox@lemmy.worldWho's using Proxmox?
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    1 month ago

    Perhaps this comment most addresses what was on my mind. I see comments from admins, education, small biz, homelabbers (homelabbers rule!).
    There are only a couple folks that appear to be in my tier (50 + hosts). And that’s because there arent a lot of us on proxmox.

    I think you’re right. Big enterprise moves slow. The VMwsre implosion is just now hitting corporate budgets.
    Thanks for your perspective, friend.


  • dbtng@eviltoast.orgOPtoProxmox@lemmy.worldWho's using Proxmox?
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 month ago

    I love to hear this. I admit tho, I thought Proxmox would explode after VMware imploded. Proxmox did not just step into the gap left by VMware. A very large portion of IT has still never heard of Proxmox and could not tell you what its for, while they all have some passing understanding of what VMware is.

    I was hoping for a sudden swell where companies were moving ESXi > PVE en masse … and hiring engineers at high dollars. I don’t see that. :[


  • dbtng@eviltoast.orgOPtoProxmox@lemmy.worldWho's using Proxmox?
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    1 month ago

    Thank you so much. I was headed there. Doc caught me 2 years ago, gave me the big warning. Cut back the booze, dropped 50 pounds, started eating fiber. Now I’m just a stress case, but a darn healthy one.
    I’m not scrambling to get a different job. I’m well paid, and good luck finding someone to do my job, so the boss takes some crap back from me. Plus, I don’t think we can do more layoffs and stay in biz. But the ceo does make bold architecture decisions.

    Lemmy is awesome. I act like a jerk and meet people regardless.
    Well met, friend.








  • dbtng@eviltoast.orgOPtoProxmox@lemmy.worldWho's using Proxmox?
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 month ago

    Hehe. Have you been to a real job? Where real things happen? The mark of a good admin is that they can do anything at all.

    Oh, we are gonna switch to 100% Docker now? Ok, I’ll get up to speed on that. Ooops, no now it all goes to Azure. Ok, dust off my Azure certs. Nope, now we are gonna put everything on this gui on top of kvm called proxmox.
    Sure, whatever. Let’s just get it done.


  • dbtng@eviltoast.orgOPtoProxmox@lemmy.worldWho's using Proxmox?
    link
    fedilink
    English
    arrow-up
    9
    ·
    1 month ago

    My friend, I’ll hand out discredit where it is due, and Proxmox has a lot of issues … but the Proxmox vendor does a decent job of supporting a free product.

    https://forum.proxmox.com/

    In fact I do devote several hours every week sorting out people’s issues on the vendor’s forum.
    But they have real employees … well they are interns and a few really cranky support folks.
    And they drag the devs in to respond to stuff regularly.
    So they don’t really need my help. But I’m helping.




  • This is the latest from the staff.

    • My guess is that you are writing and pruning backups faster than the GC is able to keep up with. New backups might be created faster (using fast incremental mode) than the GC phase 1can keep up with due to cache capacity limit. How big are such backup snapshots typically in your case? Are they in the TiB range? In previous versions new snapshot indices were not considered during GC, which could however lead to possibly not touching all chunks in very specific edge cases with long running GC and high frequency pruning setups.
    • You can try and increase the gc-cache-capacity in the datastore tuning options to the maximum value of 8388608 and restart GC, see https://pbs.proxmox.com/docs/storage.html#tuning
    • In general, you should consider adding a special device for such a storage setup, see https://pbs.proxmox.com/docs/sysadmin.html#zfs-special-device

    My interpretation is that this issue will affect setups with slower disks and larger backups.

    The recommendation to add an SSD special vdev is an interesting aside. Like, are they actually pushing that now? That’s some ZFS rocket surgery. (I like ZFS.)




  • dbtng@eviltoast.orgOPtoProxmox@lemmy.worldProxmox Backup Server
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    Let me explain the ‘pro’ comment. I’m active on the official forum. Most of the ‘pros’ there don’t use proxmox_backup_client. People I respect do not use that tool, probably each for their own reasons.

    My own issue with PBS support for physical servers is that full recovery is DIY. You have to format disks and stand up at least a temp OS in order to wipe and start over.

    I think I’ve scaled out PBS pretty far. My biggest datastores are 14 TB. That’s about 85 VMs. I use a multi-layer PBS setup for Backup and Sync at 5 geographic locations. A couple sites have hardware syncing to virtual, which in turn does site-to-site. I’m using PBS site-to-site sync to support a colo migration.

    PBS is a great tool in rapid development. During the time I’ve used it, they introduced fleecing and all its many issues. There are more changes coming. As admins, we are supporting a moving target.


  • dbtng@eviltoast.orgOPtoProxmox@lemmy.worldProxmox Backup Server
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    I believe the point is that it doesn’t do a snapshot stun or run out of a delta disk. Its a different technology. I know it does use qm snapshot. The tech docs I’ve read don’t quite fill in the details for me either. Much of the point of PBS architecture was to avoid that stun.

    The proxmox_backup_client is not my bag. I’m glad it’s found a user. Most pros I know don’t touch it.