Re: [BackupPC-users] Correct rsync parameters for doing incremental tran

Subject:

Re: [BackupPC-users] Correct rsync parameters for doing incremental transfers of large image-files

From:

Andreas Piening <andreas.piening AT gmail DOT com>

To:

"General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>

Date:

Tue, 15 May 2012 01:34:29 +0200

There are already two USB-disks that are swapped every few days and I copy nightly images on the currently connected drive. Some weeks ago, the office had a water-pipe break. The water has been stopped early enough so there was no damage, but my customer assigned me to create a external backup solution. He wants me to be able to completely restore the system including the virtual machines if someone breaks into the office and steals the hardware ore something like that. If this happens, I need at least one day to buy new hardware. But the point is that I need to be able to restore the system afterwards to a working state just like it was one day before the disaster happens.

As I understand the rsync functionality the algorithm is able to do in-file incremental updates. My problem is just that I can't figure out what prevents it from working in my case...

Am 15.05.2012 um 00:53 schrieb Les Mikesell:

On Mon, May 14, 2012 at 5:20 PM, Andreas Piening
<andreas.piening AT gmail DOT com> wrote:
Hi Les,

using a outdated image for restoring and "manually" copying things over is
not an option for me. The Server is a domain-controller with several
profiles, running two databases and have proprietary software installed that
relies on registry settings and all that silly stuff.

I don't see another chance then using a nightly created image atm and I can
live with space-waste, no pooling and heavy IO but I just want this in-file
incremental rsync to work as expected because the only thing that breaks it
is that I can't transfer 80 GB of data through a DSL50 line every night.
This would exceed the time-window I have for the backup.

Can you park another drive nearby - preferably on a different machine
but not absolutely necessary?   Then script a local copy during your
backup window and dribble the offsite copy out after it completes.
That gives you a much faster restore option unless you have a site
disaster or it failed mid-backup, and the backuppc history will cover
those risks.

--
   Les Mikesell
      lesmikesell AT gmail DOT com

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

_______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List:    https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:    http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [BackupPC-users] Correct rsync parameters for doing incremental transfers of large image-files, Les Mikesell

Next by Date:

Re: [BackupPC-users] Correct rsync parameters for doing incremental transfers of large image-files, Adam Goryachev

Previous by Thread:

Re: [BackupPC-users] Correct rsync parameters for doing incremental transfers of large image-files, Les Mikesell

Next by Thread:

Re: [BackupPC-users] Correct rsync parameters for doing incremental transfers of large image-files, Adam Goryachev

Indexes:

[Date] [Thread] [Top] [All Lists]