Jaster

so on the first server I have the data, the initial snapshot and one delta? or can I get rid/avoid the initial duplicate/snapshot on the source server?

I don't mind scripting but I still need a full snapshot on the source server?

Could you elaborate a little bit or send me a resource to read up please?

Hi, is it possible to work with BTRFS snapshots across two server? I'm running a cache on one server and would like to create snapshot backups (+ deltas) on the other one.

done that and running a parity check to see if this was the issue. was just wondering if smart is already telling to replace the disk.

Hi guys, I have a disk with read errors and attached the SMART report - could you tell me if that thing is still fine or if it needs to be replaced? knowlage-smart-20210409-1441.zip

My Server suddenly become unstable, - what is happening, what can I do?

Thanks, that solves it for me

Hi Guys, this keeps happening with different VMs Randomly, trying to start a VM this message pops up. If I restart some running VMs I can start also the one which would not start before and the issue is gone. Super annoying and keeps happening

Corruption can occur any time, so my questions is how to overcome it. Full backup of the drive, sure... However if this is the risky part about BTRFS, I'd like to cover this with a little bit less effort (hardware wise). So... would it be possible to create a backup or an "external" RAID just for the file system? E.g. Having the array with all HDDs protected by parity, while the file system resides on a RAID 5/10 Pool of SSDs. Or just have a job that back ups the file system on an hourly/daily basis?

I'm not talking about an empty file system. The data is protected by the parity. The Filesystem is not - so why not back it up?

Sorry if it sounds silly, but is there a way to backup/replicate the filesystem without the actual data?

Lets say I run into a filesystem corruption, can I just restore the whole disk with paraties in place?

So the increased risk is losing the filesystem on a disk, but this can be recovered by the usual parity rebuild? If I want to backup something from another pool, I need to create an entry point based on a disk instead of a share, right? Anything else I do not see? Is there something like a "save procedure" to migrate from xfs to btrfs?

How does Parity interact with this? Can I still lose a disk and restore it? Shares will not work across disks, but I rather have to create share by disk?...