Full backup may not back up all files on Samba share yet report success
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
backuppc (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Due to a regression in smbclient apparently starting from version 3.6, not all files may be backed up by a BackupPC full backup. Yet BackupPC reports the backup as successful.
The first NT_STATUS_
So for example, if a backup of a C$ share on a Windows host processes files in alphabetical order, and C$/pagefile.sys gives the NT_STATUS_
The backup is nevertheless shown as a full backup and not a partial one in the BackupPC user interface. Looking at the error log, the user can see NT_STATUS_
A subsequent incremental backup may actually back up more files, as it may exclude some of the ones with those errors. I actually came across this bug by seeing incrementals back up much more files than full backups. Incrementals get deleted after a week in the default configuration, leaving partial full backups.
It is quite alarming to realize this bug may affect all users with the default packages and default configuration who are backing up Samba shares with locked files - practically any Windows target.
This is probably related to this Samba bug:
https:/
That bug is tagged to Samba 3.6, but I have seen the same behaviour with Samba 4.1.6 in Trusty. The best way to see this is to run the backup command from the command line and see it die prematurely after the first error in the root of the share.
A workaround to this issue is to downgrade smbclient to version 3.5.
Status changed to 'Confirmed' because the bug affects multiple users.