From: Roman Mamedov <rm@romanrm.net>
To: Ram Ramesh <rramesh2400@gmail.com>
Cc: Adam Goryachev <mailinglists@websitemanagers.com.au>,
Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: How to backup of large md raid volumes?
Date: Fri, 19 May 2017 10:01:42 +0500 [thread overview]
Message-ID: <20170519100142.1f034b82@natsu> (raw)
In-Reply-To: <8b840e53-1be2-b1b5-632f-e75f0c6c53b7@gmail.com>
On Thu, 18 May 2017 22:39:59 -0500
Ram Ramesh <rramesh2400@gmail.com> wrote:
> Here is a summary of what I like to do. I want to backup files on to
> (multiple) disks that will be loaded on to a USB dock. Simple one to one
> copy is all I am looking for. I am not interested in full vs.
> incremental or keeping versions of files for restore. My data is just
> movies and songs. All I want is a SW that understands links (to avoid
> duplicates) and copy files in batch on to multiple disks. I want content
> of each (backup) disk to be independent. This way if one backup disk
> dies, I have all other files unaffected by this failure. The only reason
> I did not try multi-volume tar is the lack of independence across disks.
What I'm doing is storing files on my primary storage in folders according to
where they are backed up to.
E.g. "[back up of this is to be stored] On USB disk A", "B", etc.
In your case that would be:
/storage/OnDiskA/Movies/......
/storage/OnDiskA/Music/......
/storage/OnDiskB/Movies/......
--
With respect,
Roman
next prev parent reply other threads:[~2017-05-19 5:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-18 21:37 How to backup of large md raid volumes? Ram Ramesh
2017-05-19 1:34 ` Adam Goryachev
2017-05-19 3:39 ` Ram Ramesh
2017-05-19 4:36 ` Victor Helmholtz
2017-05-19 5:01 ` Roman Mamedov [this message]
2017-05-19 5:11 ` Roman Mamedov
[not found] ` <95546cb8-e195-a693-f4c8-e8b250cec30e@cas.homelinux.org>
2017-05-21 19:48 ` Ram Ramesh
2017-05-19 3:59 ` Victor Helmholtz
2017-05-19 5:49 ` Reindl Harald
2017-05-20 18:00 ` Wols Lists
2017-05-20 18:11 ` Reindl Harald
2017-05-20 18:14 ` Reindl Harald
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=20170519100142.1f034b82@natsu \
--to=rm@romanrm.net \
--cc=linux-raid@vger.kernel.org \
--cc=mailinglists@websitemanagers.com.au \
--cc=rramesh2400@gmail.com \
/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