From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Safeguarding strategies against SSD data loss
Date: Mon, 27 Oct 2014 15:16:29 +0000 [thread overview]
Message-ID: <201410271516.30449.michaelkintzios@gmail.com> (raw)
In-Reply-To: <20141027122758.GB1022@ca.inter.net>
[-- Attachment #1: Type: Text/Plain, Size: 1394 bytes --]
On Monday 27 Oct 2014 12:27:58 Philip Webb wrote:
> 141027 Mick wrote:
> > On Sunday 26 Oct 2014 23:25:50 Volker Armin Hemmann wrote:
> >> With a caveat: if an ssd dies, it will die suddenly. Without a warning.
> >
> > I haven't yet started using SSD and wonder what sort of a system
> > should I set up to guard against such instantaneous catastrophic
> > failures.
>
> My desktop machine is now 2 yrs old & has an SSD for immediate stuff ;
> it also has an HHD with 500 GB available.
> Files I'm working on are backed daily to HHD & to USB stick ;
> once/week I use a script in Krusader to copy everything in ~ or /etc
> which has changed during that week onto HHD & USB
> & also to an off-site system I have I/net access to ;
> I also run a simple Bash script to rsync system files to an HHD copy.
> Every 9 mth I do a full back-up of everything in ~ or /etc ,
> of which I keep at least 1 copy off-site & another on CD (in future DVD)
> for when the Earth's poles change & everything magnetic is wiped out
> (grin).
>
> 2 belts + 3 braces : HTH.
I have never been that diligent with my back ups, unless we're talking about
critical data which I will save in two separate systems/media from the start.
Otherwise, I run a back up of the whole system every 3 months or so.
Perhaps with an SSD I will do this once a month.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2014-10-27 15:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-27 9:24 [gentoo-user] Safeguarding strategies against SSD data loss Mick
2014-10-27 10:30 ` Alec Ten Harmsel
2014-10-27 11:11 ` Alan McKinnon
2014-10-27 13:13 ` Rich Freeman
2014-10-27 15:15 ` [gentoo-user] " James
2014-10-27 15:23 ` Mick
2014-10-27 15:22 ` [gentoo-user] " Mick
2014-10-27 15:36 ` Rich Freeman
2014-10-27 16:52 ` Pandu Poluan
2014-10-27 17:26 ` Volker Armin Hemmann
2014-10-27 17:30 ` Rich Freeman
2014-10-28 0:41 ` Pandu Poluan
2014-10-28 1:13 ` Rich Freeman
2014-10-28 3:45 ` Tom H
2014-10-27 17:23 ` Volker Armin Hemmann
2014-10-27 17:37 ` Rich Freeman
2014-10-28 0:56 ` Pandu Poluan
2014-10-28 3:49 ` Tom H
2014-10-27 17:20 ` Volker Armin Hemmann
2014-10-27 17:17 ` Volker Armin Hemmann
2014-10-27 12:27 ` Philip Webb
2014-10-27 14:12 ` [gentoo-user] Safeguarding strategies against SSD data loss : PS Philip Webb
2014-10-27 15:16 ` Mick [this message]
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=201410271516.30449.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.com \
--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