The previous full run is used as the comparison unless you have
configured incremental levels. But, why not just do more frequent full
runs to keep the base more current? Fulls take longer in elapsed time
because the remote files are all read for comparison, but they don't use
a lot more
Le 28/08/2010 20:02, Les Mikesell a écrit :
On 8/28/10 7:01 AM, Xuo wrote:
Hi,
I would like to notice a behavior that (I think) should be modified.
By default, my ping and ssh executables have the following file attributes :
-rwsr-x--- 1 root ntools 34920 2010-04-18 12:31
/bin/ping
Le 28/08/2010 20:02, Les Mikesell a écrit :
On 8/28/10 7:01 AM, Xuo wrote:
Hi,
I would like to notice a behavior that (I think) should be modified.
By default, my ping and ssh executables have the following file attributes :
-rwsr-x--- 1 root ntools 34920 2010-04-18 12:31
/bin/ping
Why is my XferLog 291GB large? I'm trying to backup 650GB worth of
data, I don't understand the purpose of the file, it seems like it's
dumping the binary of the backup files into the log. I also am seeing a
fair amount of Error: opendir errors for that machine. Is that
related at all? I
On 9/11/10 2:22 AM, Timothy Omer wrote:
-for rsyncd, fulls and incrementals are the same other than the fact
that full takes longer checking all files. The reason full is the same
is due to it will not transfer any files in the pool that are the
same, hence it only transfers changes... just
On 11 September 2010 17:13, Les Mikesell lesmikes...@gmail.com wrote:
On 9/11/10 2:22 AM, Timothy Omer wrote:
-for rsyncd, fulls and incrementals are the same other than the fact
that full takes longer checking all files. The reason full is the same
is due to it will not transfer any files in
On 9/11/10 11:38 AM, Timothy Omer wrote:
So when an Incremental runs, if the last backup is a Full backup files
that are the same never get transferred to the server.
Yes, and in an incremental run, only the filename, timestamp, and length are
compared. In a full run, a block checksum
