Search results

I've tried to use Ceph in a small Homelab, with hardware three classes below yours (Mini PC and slow network). I've learned that there are some pitfalls and I would work hard to start with five instead of the absolute minimum if three nodes...

I'm not using one, but I have a question: that seems plausible during setup, but during operation? Is ssh-access actually used for a QDev "doing its thing"? If not one could disable it after installation... My (possibly wrong) understanding was that the QDev is attached to the corosync...

Obviously that depends on the modified data per interval and the "prune"-settings. And it needs a number of backups present to work at all :-) Both my dayjobs cluster and my homelab show around 30 - with basically "everything daily". If I would run hourly backups the Dedup-Factor would...

Um ein paar Prozent Ram-Entlastung zu erzeugen taugt das hier: # apt show zram-tools Homepage: https://github.com/highvoltage/zram-tools zram-tools uses this module to set up compressed swap space. This is useful on systems with low memory or servers running a large amount of services with...

Yes. Just know that the last release seems to be (nearly) three years old... https://www.gluster.org/release-schedule/ (while github lists more fresh 11.x releases...)

For example: echo 'Acquire::ForceIPv4 "true";' | tee /etc/apt/apt.conf.d/99force-ipv4 This works obviously only for apt; the rest of the IP stack is not affected by this.

ZFS with HDD without Special Device? (( The difference between Sata SSD and PCIe NVMe is theoretically large. Practically it is not - in this context. The important aspect is the access time compared to the rotating spindles. Data access will take five milliseconds and it is nearly irrelevant...

So the problem may be that your IPv4 setup is not... correct? Everything else works? A simple configuration for one NIC and one bridge: https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_default_configuration_using_a_bridge - of course it needs to fit to your actual LAN... Edit: if both...

https://geizhals.de/?cat=hdssd&xf=7139_>=480GB~7156_Power-Loss Protection Schlechte reale Auswahl... :-( Aber die Filtermöglichkeiten sind gut... MIt "M.2" Filter = https://geizhals.de/?cat=hdssd&xf=7139_%3E%3D480GB~7156_Power-Loss%20Protection~7177_M.2%202280&offset=0

Try to use IPv4 instead, at least for troubleshooting to exclude IPv6 has problems: Run this on a root shell: apt -o Acquire::ForceIPv4=true update && apt -o Acquire::ForceIPv4=true -d -y full-upgrade

Seems so. One can build a backup system in any way - if it works (reliably, on the long run), it is probably fine :-)

There is extensive documentation available: https://pbs.proxmox.com/wiki/Upgrade_from_3_to_4 If there are no specific reasons against it, I would follow that doc.

You are questioning my words that PBS "wants IOPS"? That's... surprising! "Backup storage: Prefer fast storage that delivers high IOPS for random IO workloads; use only enterprise SSDs for best results." -- https://pbs.proxmox.com/docs/installation.html#recommended-server-system-requirements...

Yes, that's possible. Please be aware that there may be some surprises hidden in this "absolute minimum"-approach: https://forum.proxmox.com/threads/fabu-can-i-use-ceph-in-a-_very_-small-cluster.159671/

https://pve.proxmox.com/pve-docs/chapter-pvecm.html#pvecm_qdevice_status_flags Edit: to see the current connection state: corosync-cfgtool -s ; corosync-cfgtool -n

Yes, it works. I said "suboptimal". For me this means that some potential is wasted - for one or another reason. In this case we know that PBS wants IOPS. For me this means that the best results require direct hardware access to fast storage, e.g. SSDs. Each abstraction layer like virtual disks...

No :) The used technology (Qemu) allows to "freeze" a machine and make a (temporary) snapshot. After this is done - which takes only a few seconds - the VM will continue to do whatever it is meant to do. Then the actual backup starts. Of course this invisible snapshot is removed when the...

You may read man zpool-import - there are some options to find a missing pool by searching for devices and also to import a "destroyed" pool (for example). Of course most of those commands are dangerous, but you don't have actual data on those drives yet, right? The drives are visible via lsblk -f?

I am not convinced! 4 binary TB (correct: 4 TiB) is 4398046511104 Bytes. And it is 4294967296 KILOBytes. The last one is possibly used to show wrongly 4.2 TB...

Perhaps a maximum filesize limit is hit somewhere? Compare: https://en.wikipedia.org/wiki/Comparison_of_file_systems#Limits