BackupPC-users

Re: [BackupPC-users] Different Blackout Periods

2015-04-03 13:35:48
Subject: Re: [BackupPC-users] Different Blackout Periods
From: "Alexander Rehbein" <alexander.rehbein AT fmex DOT de>
To: "'General list for user discussion, questions and support'" <backuppc-users AT lists.sourceforge DOT net>
Date: Fri, 3 Apr 2015 19:34:01 +0200
Hi,

I used one file per message. The amount of messages are about 100 per hour.
In my setup now, I can see that the number of files are increasing every
incremental backup (the incr backup self takes 0.5mins). IncrLevels is set
to 1. If read the doc about this value but I think I didn't understand this
right. In my case, were I takes (7*24) around 168 incr backups between two
full backups, which value were a good choice for IncrLevels? Is it
1,2,3,4,5...,167?

I get a little bit confused because my english is not very well.

Thank you for helping!

Greetings

Alex

-----Ursprüngliche Nachricht-----
Von: Les Mikesell [mailto:lesmikesell AT gmail DOT com] 
Gesendet: Freitag, 3. April 2015 18:16
An: General list for user discussion, questions and support
Betreff: Re: [BackupPC-users] Different Blackout Periods

On Thu, Apr 2, 2015 at 4:25 AM, Alexander Rehbein
<alexander.rehbein AT fmex DOT de> wrote:
>>
>
> I've looked in the archive. Sometimes the incr backup is only 20mb, 
> sometimes 200mb. Perhaps it is an better idea to only backup 
> /var/vmail directory hourly instead of the full root path.

First, make sure you understand how backuppc works - and the type of your
mail files.  If you use the old mbox mail format where messages are appended
to a single growing mailbox file, and use rsync, only the difference will be
transfered, but there is some CPU work involved to compute the changes, and
on the server side a complete new file copy will be constructed and stored
separately. Xfer methods other than
rsync will send the whole changed file.    If your mail storage uses
one message per file like maildir format, rsync will only send the new files
(whether doing a full or incremental) and the ones where the content matches
the previous copy will all be pooled without taking
additional space.   Non-rsync xfers will send only new files on
incrementals and everything on fulls, but existing content is still
found and pooled in storage.   Note that 'new' means newer than the
previous full unless you have configured incremental levels.

So, there won't be much difference in the storage used regardless of
your mix of incremental/full runs.   The main difference will be in
the time they take to complete and possibly the performance impact on
the target system.   An incremental rsync run quickly skips fields
where the length/timestamp match the previous copy where the fulls do a full
read of the target content to do a block-checksum comparison, Also, the
fulls will rebuild the archive directory tree which may be time-consuming
with many small files, but that becomes the new base for incrementals,
making the next ones more efficient.

--
  Les Mikesell
     lesmikesell AT gmail DOT com

----------------------------------------------------------------------------
--
Dive into the World of Parallel Programming The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
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/


------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the 
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
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/