From: Carl Cook <CACook@quantum-sci.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Synching a Backup Server
Date: Thu, 6 Jan 2011 13:42:23 -0800 [thread overview]
Message-ID: <201101061342.23991.CACook@quantum-sci.com> (raw)
In-Reply-To: <AANLkTi=iWyKFOoaY6JjTuhg_0CyAtOh=s2gcBUuHGwau@mail.gmail.com>
On Thu 06 January 2011 11:16:49 Freddie Cash wrote:
> Just run rsync on the backup server, tell it to connect via ssh to the
> remote server, and rsync / (root filesystem) into /backups/htpc/ (or
> whatever directory you want). Use an exclude file to exclude the
> directories you don't want backed up (like /proc, /sys, /dev).
> Then repeat the rsync process the next day, into the exact same
> directory. Only files that have changed will be transferred. Then
> snapshot the filesystem using the current date.
Kool.
> > Also with this system, I'm concerned that if there is corruption on the HTPC, it could be propagated to the backup server. Is there some way to address this? Longer intervals to sync, so I have a chance to discover?
>
> Using snapshots on the backup server allows you to go back in time to
> recover files that may have been accidentally deleted, or to recover
> files that have been corrupted.
How? I can see that rsync will not transfer the files that have not changed, but I assume it transfers the changed ones. How can you go back in time? Is there like a snapshot file that records the state of all files there?
next prev parent reply other threads:[~2011-01-06 21:42 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 17:35 Synching a Backup Server Carl Cook
2011-01-06 19:16 ` Freddie Cash
2011-01-06 19:34 ` Marcin Kuk
[not found] ` <AANLkTik-rhXAHW18id4WMMtdqXkicvzTZ47+2r6YMuY0@mail.gmail.com>
2011-01-06 19:47 ` Freddie Cash
2011-01-06 20:07 ` C Anthony Risinger
2011-01-06 20:13 ` Freddie Cash
2011-01-06 20:21 ` C Anthony Risinger
2011-01-06 21:06 ` Gordan Bobic
2011-01-06 21:39 ` Freddie Cash
2011-01-06 21:44 ` Carl Cook
2011-01-06 21:53 ` Gordan Bobic
2011-01-06 21:58 ` Freddie Cash
2011-01-06 22:26 ` Carl Cook
2011-01-06 22:29 ` Gordan Bobic
2011-01-06 23:07 ` Carl Cook
2011-01-07 16:14 ` Hubert Kario
2011-01-06 23:15 ` Fajar A. Nugraha
2011-01-06 21:42 ` Carl Cook [this message]
2011-01-06 21:52 ` Freddie Cash
2011-01-07 16:20 ` Hubert Kario
2011-01-09 11:46 ` Alan Chandler
2011-01-09 13:54 ` Fajar A. Nugraha
2011-01-09 15:32 ` Alan Chandler
2011-01-09 17:59 ` Freddie Cash
2011-01-09 18:30 ` Hugo Mills
2011-01-09 20:57 ` Alan Chandler
2011-01-09 22:01 ` Hugo Mills
2011-01-09 23:32 ` Alan Chandler
2011-01-11 22:25 ` Hugo Mills
2011-01-10 2:22 ` Fajar A. Nugraha
2011-01-11 22:41 ` Hugo Mills
2011-01-21 19:28 ` Freddie Cash
2011-01-22 13:45 ` Hugo Mills
2011-01-24 17:45 ` Freddie Cash
2011-01-22 13:55 ` Hubert Kario
2011-01-25 17:29 ` Kaspar Schleiser
2011-01-25 17:43 ` Hubert Kario
2011-01-25 17:59 ` Freddie Cash
2011-01-25 18:36 ` Hubert Kario
2011-01-10 13:14 ` Hubert Kario
2011-01-06 20:12 ` Fajar A. Nugraha
2011-01-06 21:43 ` Carl Cook
2011-01-06 21:43 ` Goffredo Baroncelli
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=201101061342.23991.CACook@quantum-sci.com \
--to=cacook@quantum-sci.com \
--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;
as well as URLs for NNTP newsgroup(s).