All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sergiusz Brzeziński" <Sergiusz.Brzezinski@supersystem.pl>
To: David Brown <david.brown@hesbynett.no>
Cc: linux-raid@vger.kernel.org
Subject: Re: mdadm --monitor: need extra feature?
Date: Tue, 21 Aug 2012 13:51:48 +0200	[thread overview]
Message-ID: <50337654.9000905@supersystem.pl> (raw)
In-Reply-To: <503366A1.9030307@hesbynett.no>



W dniu 21.08.2012 12:44, David Brown pisze:
> On 21/08/2012 12:41, Sergiusz Brzeziński wrote:
>> Hi,
>>
>> I use Raid1 to make backup of the whole system.
>
> Raid is not a backup system. It is to improve uptimes, minimise downtimes due to
> disk failures, and possibly to improve disk speed and/or capacity.
>
> I would recommend you first think about what you are trying to achieve here -
> what are you trying to back up, how do you see restores being used, how
> efficiently are you using your hardware, your bandwidth, your time and effort?
>
> You would probably be better off with a normal fixed 2-disk raid1 to minimise
> the problems caused by a single disk failure, combined with an rsync snapshot
> style backup that can be fully automated and give quick and easy recovery of
> multiple old versions of files in the face of the most common cause of data loss
> - human error.
[...]

I know, I know. Raid is not a backup system :)

Or better: it is not intended to be a backup system.

But I do use Raid1 as backup solution because I don't know another backup 
solution giving me together:
- so simple configuration (there is no configuration!)
- so low cost (no software cost, only hdd cost)
- complete copy of the whole system (not only data but also configuration)
- so quick start in case of hardware failure
- so fast backup process without excessive system load
- so simple handling (just remove and insert hdd with hot-swap bay)

With some more rotating disks it can simulate very good backup solutions and I 
still can make backups of critical data (dumping databases, copying files) 
independently of Raid (and I do it).

And even I You don't want using it as a regular backup it is alwas worth to do a 
bootable disk with mirrored system partition and keep it somewhere out of the 
box for the bad times - just a small system backup for quick start in case of 
hardware failure.

So, maybye Raid 1 is not a backup system but for some cases this is the best 
backup solution it can be! And I am an opportunist :)

Sergiusz

--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-08-21 11:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21 10:41 mdadm --monitor: need extra feature? Sergiusz Brzeziński
2012-08-21 10:44 ` David Brown
2012-08-21 11:51   ` Sergiusz Brzeziński [this message]
2012-08-21 12:39     ` Adam Goryachev
2012-08-22  7:14       ` Sergiusz Brzeziński
2012-08-22  7:44         ` NeilBrown
2012-08-22  9:50           ` Sergiusz Brzeziński
     [not found]             ` <5034B0A2.4080403@websitemanagers.com.au>
2012-08-22 10:50               ` Sergiusz Brzeziński
2012-08-22 10:57                 ` Sergiusz Brzeziński

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=50337654.9000905@supersystem.pl \
    --to=sergiusz.brzezinski@supersystem.pl \
    --cc=david.brown@hesbynett.no \
    --cc=linux-raid@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.