Re: [BackupPC-users] BackupPC 4.4.0: Incremental smb backup is skipping not backed-up files under certain conditions

2021-06-11 Thread Les Mikesell
On Fri, Jun 11, 2021 at 8:38 AM Michael Stowe
 wrote:

> It is worth poking at the contention that "an incremental backup with rsyncd 
> unfortunately takes as long as the full backup."  This probably isn't true, 
> but I can understand how one can believe this after running a single 
> incremental backup with rsyncd.  How does rsyncd know what to copy 
> incrementally?  It skips files that are already copied ... of which, there 
> are none for your first incremental backup.

If the files are mostly tiny, you can see how rsync's action of
exchanging the directory information needed to determine
existing/changed status would be almost as much work as updating the
files.

> If your *second* incremental backup takes almost as long as the full backup, 
> we'll need more details, as your configuration is deviating significantly 
> from expectations.

I think I recall something about the third rsync backup getting a
speedup too, where the block checkums are saved on the 2nd run after a
file has been copied.  Not sure if that still applies to v4.

-- 
Les Mikesell
 lesmikes...@gmail.com


___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/


Re: [BackupPC-users] BackupPC 4.4.0: Incremental smb backup is skipping not backed-up files under certain conditions

2021-06-11 Thread Michael Stowe

On 2021-05-26 07:01, Jens Potthast wrote:


Hi,

My Problem: When doing an incremental backup with smb, only files with 
mtime

newer than the date and time of the last backup are being backed up.

To reproduce: If I copy a file with an old ctime, the file is not 
included
in the backup even if it is not contained in the previous complete 
backup.
Only the timestamp of the mtime seems to be relevant - even if the file 
is

not present in any backup so far.

I am not sure, if this behavior is intended or if I have misconfigured 
smb

backup settings.

The problem would be solved with the next complete backup. However, due 
to

my circumstances, I can rarely do a full backup. And only with rsyncd,
because smbclient aborts after a while, because I have to backup lots 
of
files (> 1.000.000), which takes usually more than a day. (However, not 
due

to configurable time limits, which I extended generously.)

An incremental backup with rsyncd unfortunately takes almost as long as 
the
full backup, so I need to do the incremental backups with smbclient. 
This
takes only minutes (with only a few changed files), but misses new 
files

with an old date.

Any help is greatly appreciated!

Regards,
Jens


You're describing a limitation of using SMB.  Considering it for a 
moment, one can ask SMB to retrieve files modified beyond a certain 
time, but SMB does not have a command that says, "send along any files 
that weren't there at a certain point in the past."  How would SMB know 
the files weren't there?


How would one implement such a command using SMB?  By retrieving all 
files, and comparing to a previous backup...  which is also known as a 
full backup.


It is worth poking at the contention that "an incremental backup with 
rsyncd unfortunately takes as long as the full backup."  This probably 
isn't true, but I can understand how one can believe this after running 
a single incremental backup with rsyncd.  How does rsyncd know what to 
copy incrementally?  It skips files that are already copied ... of 
which, there are none for your first incremental backup.


If your *second* incremental backup takes almost as long as the full 
backup, we'll need more details, as your configuration is deviating 
significantly from expectations.___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/


[BackupPC-users] BackupPC 4.4.0: Incremental smb backup is skipping not backed-up files under certain conditions

2021-05-26 Thread Jens Potthast
Hi,

My Problem: When doing an incremental backup with smb, only files with mtime
newer than the date and time of the last backup are being backed up. 

To reproduce: If I copy a file with an old ctime, the file is not included
in the backup even if it is not contained in the previous complete backup.
Only the timestamp of the mtime seems to be relevant - even if the file is
not present in any backup so far.

I am not sure, if this behavior is intended or if I have misconfigured smb
backup settings.

The problem would be solved with the next complete backup. However, due to
my circumstances, I can rarely do a full backup. And only with rsyncd,
because smbclient aborts after a while, because I have to backup lots of
files (> 1.000.000), which takes usually more than a day. (However, not due
to configurable time limits, which I extended generously.)

An incremental backup with rsyncd unfortunately takes almost as long as the
full backup, so I need to do the incremental backups with smbclient. This
takes only minutes (with only a few changed files), but misses new files
with an old date.

Any help is greatly appreciated!


Regards,
Jens



smime.p7s
Description: S/MIME cryptographic signature
___
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List:https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki:https://github.com/backuppc/backuppc/wiki
Project: https://backuppc.github.io/backuppc/