Recent content by hevisko

Thank you I just wish this description is/was included in the Wiki/Documentation :)

YEs, I saw the S3 options advices... I had ask and do have a need/use for it, but in an archival setup, not my first/primary and neither my secondary/sync servers, but like my tertiary servers when I need to recover something from a year ago, not to recover in a jiffy after a DC burn down (Yes...

Do NOT forget about Tuxis.nl -> not associated with them, I just used their services when I initially started using PBS, and it's well priced remote sync options to consider. Not fancy all bells included, but is does do work as a remote destination, and they do allow/etc. sync jobs

I advise, and are using it this way myself.. and lately it is the only deployment *for*me* for PBS, is to run PBS as an LXC, and PVE managing the ZFSs... this leaves (at least in my case) some spare throw-away CPU cycles to use of throw-away VM stuff :)

@jfraf I actually abuse that disabled backup job method to clear the guests without backups :D But yes, an API/etc. call to see/fetch where VMID are included in backups etc. to report on would be great.

As everything Unix/ProxMox - they provide you the rope, the question is whether you'll tie it around your neck or your waist as you jump off the building... I actually abuse the above from OP to hide the Guests I don't want to backup :D I'm more interested in a way to show which backup jobs a...

Also add the question: Are the CEPH perhaps so busy deleting other VM's data that it can't handle this deletion request?" Just had the exact same error... and after the big boy's deletion where done, and the ceph "stabilized" things just "work(TM)" again

let me check the cases I've stumbled on this week on 8.4.x (All ZFS) - out of storage errors during migration(s) with zpool (HDDs) busy and time outs - multiple storage migrations queue for multiple VMs with multiple storages "queue (waiting on locks) with out of capacity (and too busy zpools)...

I *assume* I'll have to still write a script to find the actual orphans, as I don't see those having any options popping up stating: `List the volumes that doesn't have a *valid* VMID` neither `list the storages that doesn't belong on this host`

But here is the next "kicker", I've already deleted the guest or the guest got migrated, and something in the migration errored, or a replication sync was not properly cleared and the disk/storage is still left on the other hypervisor/host. How do we clear/remove those??

Thank you! Suspect it is the updates not being as "up to date" as Quad9's CapeTown IPv6 was also having troubles with the CDN.

Is there anybody I could chat with to check what/which Geofeed is used? checking all and sundry p location/geo service providers, and I keep getting the "right" answers for the network's IPv6, but download.cdn.proxmox.com still returns unknown.unknown when querying from my IPv6 DNS resolvers ;(

Hmmm...haven't been able to make it work on FRR 10.3 nor 10.4 so that is why I'm asking for the running `wr t` output of one that is configured on.

Applied to the wrong work loads, I fully agree... especially as there are few people that understands the pros and cons of each. It's like comparing the long road driving in a Mahindra Bakkie vs taking the expensive Mercedes/BMW roadster to pickup your building sand.

Is that a modified FRRouting?