Hi, I'm struggling with the configuration of a Win10 client. I'm running 4.2.1 and have several linux clients which have backups daily for years now without any problem, with various different schedules of incremental backups.
For some time I'm also backing up a win10 laptop and I found out that in certain circumstances backups, which should have a volume of about 900G are nearly empty. The entire directory structure is built correctly but most directories are empty, whereas if you look in the history, they contain some backupped files, sometimes as old as a couple of months (indicated with v0). I do not see errormessages in the logs. The backups are mostly made during nightly hours so it's unlikely that there are massive file-locks blocking the backups. The backups are from one smb share and all share the same owner. I've done some tests with different scenarios. It appears that if a directory is copied to the smb-share, in the incremental backups, only files are backed up with a datetime later than the reference file. The files which are newly copied upon the share but have a date before the reference date are ignored. These files are only backed up in full backups. My question is, is there a way to tell smbclient which runs an incremental backup ( tarmode\full -TcN) to also backup files which are NOT already present in the delta of the directory. So the backup would copy files which are newer than the reference AND files which are older but not yet backed up in the past. Thx Mike _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
