[sles-beta] SLES 12 x86_64 RC1 snapper does not do snapshots as configured

Matthias G. Eckermann mge at suse.com
Thu Aug 7 10:10:36 MDT 2014


Hello Urs and all,

On 2014-08-07 T 15:58 +0000 urs.frey at post.ch wrote:
 
> With the hourly snapshots there is an aspect which is
> very practical: For the first time one can see what
> changes from hour to hour on the so called "static"
> filesystems.  It is a kind of security feature, when
> feeding the output from snapper detected changes into
> splunk, as example.  I had it running for weeks now
> and it grew very moderately because of the well
> defined default cleanup rules.  So I would encourage
> everybody to re-enable the hourly snapshots and get a
> free monitor of what had changed within the last hours
> on the server on the most valuable filesystems.  It
> makes life in a production environment with operators
> a bit more transparent.
 
I agree with your Use Case, and this one of the reasons,
why hourly snapshots have been implemented and had been
default before.

However, as Thorsten stated, we got feedback that the
number of snapshots were overwhelming and confusing, and
thus we decided to not switch it on by default. This
reduces risk, reduces space needed and reduces pain for
people not so much experienced in working with btrfs
and snapper.

Certainly, you are free to change the snapper settings!

What I specifically liked in your statement in addition,
was this: "well defined default cleanup rules". This is
the key part of working with hourly snapshots, and making
use of it in an efficient way; and I think "well defined"
will be different for everybody here in the one or other
way, ...

So long -
	MgE

-- 
Matthias G. Eckermann     Senior Product Manager   SUSE® Linux Enterprise
Phone: +49 30 44315731    Mobile: +49 179 2949448    E-Mail: mge at suse.com
SUSE LINUX Products GmbH  Maxfeldstraße 5          90409 Nürnberg Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)


More information about the sles-beta mailing list