BackupPC-users

Re: [BackupPC-users] [SUGGESTION] "Duration/mins" not in decimal format

2009-05-18 11:39:47
Subject: Re: [BackupPC-users] [SUGGESTION] "Duration/mins" not in decimal format
From: Adam Goryachev <mailinglists AT websitemanagers.com DOT au>
To: "General list for user discussion, questions and support" <backuppc-users AT lists.sourceforge DOT net>
Date: Tue, 19 May 2009 01:34:35 +1000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Boniforti Flavio wrote:
>> bad news is, (AFAIK) that this data is not collected within 
>> backuppc, and would need a different implementation for each 
>> transfer method. The best suggestion I could make would be to 
>> measure this at the network interface of your backuppc host. 
>> ie, the simplest method to track bandwidth consumption for 
>> rsyncd transfers is to add an iptables allow rule for traffic 
>> to your client host on port 873 (or whatever the correct ip + 
>> port is)...
> 
> Well, if I'd achieve something like this, I guess I would be collecting
> *every single bit* (also commands issued and stuff like that).
> For my purpose, it would be sufficient to know that I transferred a
> total amount of 14 files, which sum up to 1034896 bytes. I tried to look
> at the log files, but I don't understand how to distinguish between the
> words like "pool", "same", "skip", "create"... If I could assume that
> all the "create" ones are really transferred bytes, I'd be summing them
> up with a simple bash script. But what about "pool" ones (I just imagine
> that "skip" and "same" are really NO TRANSFERS)?

Also, when using rsyncd, although the file is different, the entire file
may not have been transferred. ie, a 100MB file might only transfer 5MB
which was modified from yesterday's backup....

In addition, when using rsync+ssh, if you are using compression, then
again, the actual data over the network will be less than the size of
the files transferred (probably also correct for tar+ssh with
compression, etc).

So all of these are estimations, and whether backuppc can internally
even know what the correct settings are/should be, is possibly (probably
as I think about it) impossible.

A simply pre/post script which sets up the iptables entry, and then
records the result and deletes the entry would probably be the quickest
solution for a couple of simple bash scripts.....

Still, this doesn't address the meanings of the various bits of data
which *are* kept by backuppc. Did someone manage to find the
documentation on the meaning of the data recorded in the backups files?

Regards,
Adam
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkoRgAoACgkQGyoxogrTyiXCKwCcD9eR1JNCzOvnQE9JVdxYNcyZ
FXQAn14DU0ediRfcfAXd6Ka7xoTb+8ze
=QOCY
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables 
unlimited royalty-free distribution of the report engine 
for externally facing server and web deployment. 
http://p.sf.net/sfu/businessobjects
_______________________________________________
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>