Search results

The age is irrelevant. The culprit lies in the pure number of chunks. It was a separate setup with a Raid6 (no ZFS), constructed only with HDDs. That's of course the worst case as IOPS are basically identical to one single drive. Nevertheless I wanted to give it a try - while already expecting...

That's a brave attempt. It is not clear from your post but I assume rotating rust. PBS needs IOPS, IOPS and also IOPS. Earlier or later you'll encounter timeouts and need to fight to get the data read back successfully. My very first PBS was so slow that listing the backups was impossible...

Welches Dateisystem verwendet PVE? (ZFS? ARC limitiert?) Wieviel Ram ist der VM zugewiesen? Laufen noch andere VMs? Sind die virtio Tools installiert? Ballooning aktiviert? Unbegründete Vermutung: Resource Exhaustion, insbesondere hinsichtlich RAM - 8 GiB Ram sind echt nicht viel für PVE plus...

From your post we can not see the reason. Has your last change been applied? Please post cat /etc/network/interfaces and the full output of ip address show...

See also https://forum.proxmox.com/threads/move-proxmox-boot-files-to-usb.165749/ PS: this thread is several years old...

Well, it might be easier. You can specify pruning rules in the backup job. If you have different groups of VMs with different rules and one job each. I had a system with 20 jobs --> 20 times the same pruning rules --> that's hard to maintain. In that case it is obviously better to leave those...

Oh! I've never encountered such a scenario, but yes, that would be a showstopper.

Under <your vm> --> Hardware --> Display you can select some (a very few) different graphic cards, including: "virtio-gl, often named VirGL is a virtual 3D GPU for use inside VMs that can offload workloads to the host GPU without requiring special (expensive) models and drivers..." Reference...

Yeah, that's not the usual approach. (But if it works for you... is is fine.) Just run one job with the highest frequency (daily). Learn how "pruning" works, use the Simulator: https://pbs.proxmox.com/docs/prune-simulator/ One single "Prune Job" can specify that you want to keep the latest 30...

Why? PVE can boot from a disk and use the very same for vm data. Go the HBA road. Install straight forward with ZFS. At the end all disks are bootable and the only ZFS pool (called "rpool") will allow to create virtual disks - automatically during the creation of a VM. (( Yes, it is still...

Ja, sogar offiziell: https://pbs.proxmox.com/docs/installation.html#install-proxmox-backup-server-on-proxmox-ve

Sorry again to move the topic of this thread so far away. I will stop discussing "AI" here. Perhaps a generic "New Post" would be helpful. Including a statement of "staff" if "AI" generated replies are a good thing, should be required to be tagged or should be avoided. "AI" has come to stay...

Well, that's not so easy. Searching for a keyword will find and deliver it. If you poke around here you'll find several first-posts of new accounts which reply to very old threads since some weeks now. Not all of them are recognizable as the output of a Generative LM at a first glance but...

Well, you know that /etc/pve is a representation of a shared database, so everything you put there increases the size of that database. The current implementation is fast. It is reliable. It needs to be small.

<photo> Please try to put the output of a console command into ...-tags. That makes it a) often better readable and b) copy-able. You may use the "</>" symbol at the top of the editor for that. What I wanted to say: your second screenshot shows data from "February 22". Was that intended? It...

Choosing one or the other depends on several factors. "Actually shared" being the main difference. Personally I am a ZFS enthusiast. If you can accept data loss betrween one replication point-in-time to the other then this is the best filesystem you can get. Without it you lose some nice...

Yes. Personally I would choose the Micron - but without a hard reason, just because the overall features seem to be a bit better. All three of them look good. Decide by price...?

Disclaimer: I am NOT a VirtualBox user, so my following text may be completely wrong for your situation. Do NOT do NAT / masquerading. This destroys information by replacing native and valid IP addresses by the one of a proxy machine - a gateway. In your current case there is no way to "ping"...

Ignore PVE and examine every service individually. I have three piholes. One of them is the hot one, this one is reachable by a "floating IP address". If this one dies then another pihole will take over that IP address. No client will notice that this is now another instance. I utilize...

If I remember correctly my six node Ceph was clever enough to distribute data in a way that the smaller OSDs were assigned less data - without any manual tuning. A small OSD would get 80% filled at (nearly) the same time as a large one. One of my core statements was and is "you need some more...