Server1: PVE für VMs.
Server2: TrueNAS oder OMV ZFS für Daten
Server3: PBS für Backups der PVE VMs
Server4: ZFS destination für ZFS von Server2
Dann noch Server2 und Server3 mit S3 Backup ergänzen.
Ja, aber das ist noch immer Mist.
Nehmen wir mal an, du hättest nur 100 Fotos à 10MB also 1GB an Daten.
PBS, erste Sicherung:
Liest die komplette 1GB. Macht ca. 4MB chucks, sichert die weg.
PBS, zweite Sicherung:
Liest nochmals die kompletten...
Dazu nochmal meine Gedanken:
Backups, die du auf mehrere Bänder verteilt musst, sind Riesenmist
Bänder sind sowieso ein totes Pferd und nur in ganz engen Nischen alternativlos
Änderungen des Workflows helfen häufig immens ohne hohe Kosten zu...
Warum überhaupt OMV? Wenn es dir um eine GUI für Dateifreigaben gibt, dafür tut es dann auch eine Debian-VM mit Webmin oder Cockpit. Oder ein lxc-Container mit den turnkey-fileserver o.ä, etwa https://github.com/bashclub/zamba-lxc-toolbox...
Luckily enough both are not five years old, the first version of ZFS was released in 2006 and development started in 2001 if I recall correctly.
In contrast the BSD filesystems as well as xfs or ext2/ext3/ext4 are basically decades old but they...
I did not ignore them. I did not mention them, because NTFS was only an example. You are spot on, I also don't trust ext4, xfs....
I do, yes.
That is why I wrote "maybe" for BTRFS. For me personally, it is not battle tested enough. (as we saw...
Mein Tipp: Tue es nicht!
Schau, deine VM zu sichern mit PBS, heisst Blockstorage zu sichern.
Blockstorage zu sichern ist extrem nervig. Es dauert ewigs. Die kompletten 20TB müssen gelesen werden, eine checksum berechnet werden, die veränderten...
Sure. But first tier providers also sometimes do not so smart stuff. That argumentum ad verecundiam is not that strong IMHO. Some would probably even argue that Synology is first tier and look what they do with BTRFS ;)
Simply because it has no...
Even though I believe @somedude, I also agree with @guruevi that there are shady vendors. Mabye shady is a little bit extreme, let me rephrase that to "vendors I would not trust my data".
Just like NTFS is IMHO a shady FS.
For example, I only...
> Battery backup of a single cache still makes it a SPOF
No, it doesn't.
In your scenario, another, prior and unaddressed, failure is required to make NVRAM (and/or other component(s)) a potential single point of failure.
It doesn't make it a...
@alex:
- Dell 'managed' IT - they'll sell Kubernetes (RHEL OpenShift) with an Emulex FibreChannel SPOF proprietary RAID - Ceph is available upon request, but the per-TB licensing cost is (much) higher. I've gotten similar constructions from just...
Just because a vendor does it, doesn’t mean it’s a good idea. Vendors sell some shady stuff and it works, most of the time. Most VMware clusters, even relatively large ones indeed have a storage design that basically resembles DRBD, mdraid or...
like I wrote earlier - the server will calculate and set the CRC for all incoming chunks, and will verify the digest if the chunk is unencrypted (verifying the digest of an encrypted chunk would require the encryption key, which only the client...
I am not 100% certain either. But since we use LLMs to make wild guesses, here are my wild human made guesses: ;)
Course not, incoming data is already optionally encrypted and or compressed. Checksums (verify) are probably not important at this...
You realize how wonky that sounds?
That is like me saying "hey I have this super stable Windows Server here, but unless I run that bat script to release the DHCP every night at 02:00, the NIC won't have an IP the next day".
If you clear out swap regulary you are basically doing the same as not using swap at all. Then you could disable it as well. Now I wouldn't recommend this in general ( again see the already linked pieces by Kernel developer Chris Down for...
IMHO since you already experience IO errors, you are in the danger zone already.
I would disable SWAP on both the VM and Proxmox and see what happens. Reboot and short service interruption is needed anyway.