From: "Björn Fischer" <bf@cebitec.uni-bielefeld.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Don't be like stupid me!
Date: Mon, 12 Feb 2024 09:34:18 +0100 [thread overview]
Message-ID: <416f3775-edf0-28d5-1ef2-e6b87efbd392@cebitec.uni-bielefeld.de> (raw)
In-Reply-To: <ea20c3d7-9dd3-42d8-9be8-155694d8dcaf@kenworthy.id.au>
On 2/11/24 03:14:49, William Kenworthy wrote:
[...]
>> It occurred to me fairly quickly after that press of RET that I
>> could have done well with a COW snapshot facility, something which
>> has been discussed at length on another recent thread. I even have
>> LVM on my machine for its RAID capabilities. But I've never
>> bothered before. I mean "I'm too careful", amn't I? ;-( At least
>> I do a weekly backup, though.
[...]
> No, you don't need a snapshot system - you need a proper backup
> system that stores the proper metadata. When I was experimenting
> with snapshots (btrfs and moosefs) at different times I lost
> everything a few times with filesystem corruption which meant I lost
> the snapshots too.
>
> Snapshots are NOT safe backups - treat them as a convenient copy ...
Snapshots are as reliable as the underlying file system. Here at CeBiTec
we use snapshots on several PB CephFS and ZFS with great success.
And yes, I completely agree with Alan, snapshots would have saved his
day as they provide excellent and cost efficient protection against
pilot errors.
Our users restore lost data from snapshots themselves in seconds, while
it usually takes several hours to restore data from tape. Snapshots
and tape backups complement each other perfectly and both strategies
provide means of protection the other lacks.
Cheers
Björn
next prev parent reply other threads:[~2024-02-12 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-10 15:56 [gentoo-user] Don't be like stupid me! Alan Mackenzie
2024-02-10 16:06 ` Stefan Schmiedl
2024-02-11 2:14 ` William Kenworthy
2024-02-11 10:48 ` Alan Mackenzie
2024-02-12 8:34 ` Björn Fischer [this message]
2024-02-11 18:13 ` cal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=416f3775-edf0-28d5-1ef2-e6b87efbd392@cebitec.uni-bielefeld.de \
--to=bf@cebitec.uni-bielefeld.de \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox