From: Remi Gauvin <remi@georgianit.com>
To: Claudius Ellsel <claudius.ellsel@live.de>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: WG: How to properly setup for snapshots
Date: Mon, 21 Dec 2020 12:05:37 -0500 [thread overview]
Message-ID: <a68cd516-d6a2-b7ee-744b-d1b0ee83c2df@georgianit.com> (raw)
In-Reply-To: <AM9P191MB1650A1159D554207CB5D738AE2C00@AM9P191MB1650.EURP191.PROD.OUTLOOK.COM>
On 2020-12-21 11:11 a.m., Claudius Ellsel wrote:
> Unfortunately I am already at a somewhat production stage where I
don't want to lose any data.
>
You should first and foremost make sure you have backups of everything.
>
> The problem might be that I currently don't have any subvolumes set up at all. Am I still be able to create snapshots in this stage or do I have to create a subvolume first from which snapshots can be created afterwards?
>
You have 1 subvolume, which is the root of your filesystem. You can
make snapshots of it.. (and each snapshot will be a new subvolume) To
make your life easier, as you start experimenting, I suggest making a
new Read/Write subvolume to put your snapshots into
btrfs subvolume create .my_snapshots
btrfs subvolume snapshot -r /mnt_point /mnt_point/.my_snapshots/snapshot1
(Note: You will not be able to move or rename the snapshot1
folder, but you *will* be able to move or rename the entire
.my_snapshots subvolume
> Also I learned about snapper from SUSE which sounds nice, but I don't want to break things while trying to use it.
>
Snapper is an amazing tool... You should familiarize yourself and be
comfortable with the btrfs subvolume command first, (things will make
more sense if you know whats going on...), but Snapper makes it a.. snap
to automate the snapshots *and* the clean-up.
next prev parent reply other threads:[~2020-12-21 17:06 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AM9P191MB165033908B55F8312178D90AE2CB0@AM9P191MB1650.EURP191.PROD.OUTLOOK.COM>
2020-12-21 16:11 ` WG: How to properly setup for snapshots Claudius Ellsel
2020-12-21 17:05 ` Remi Gauvin [this message]
2020-12-21 17:37 ` Roman Mamedov
2020-12-21 18:14 ` Remi Gauvin
2020-12-21 20:14 ` Goffredo Baroncelli
2020-12-21 20:27 ` Remi Gauvin
2020-12-21 20:52 ` Goffredo Baroncelli
2020-12-21 18:26 ` Andrei Borzenkov
2020-12-21 18:35 ` AW: " Claudius Ellsel
2020-12-21 18:40 ` Andrei Borzenkov
2020-12-21 20:51 ` AW: " Claudius Ellsel
2021-01-06 20:07 ` Ulli Horlacher
2020-12-21 20:24 ` WG: " Goffredo Baroncelli
2020-12-21 18:04 ` AW: " Claudius Ellsel
2020-12-21 18:32 ` Remi Gauvin
2020-12-21 18:39 ` AW: " Claudius Ellsel
2020-12-21 20:45 ` Claudius Ellsel
2020-12-21 23:33 ` Graham Cobb
2020-12-22 15:19 ` AW: " Claudius Ellsel
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=a68cd516-d6a2-b7ee-744b-d1b0ee83c2df@georgianit.com \
--to=remi@georgianit.com \
--cc=claudius.ellsel@live.de \
--cc=linux-btrfs@vger.kernel.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