Topic: Failing backup to workstation.

[Laager]

Regularly scheduled backup sent to an empty directory on the target machine runs and completes. However the next night it fails:

Cron <root@server> /sbin/e-smith/do_backupwk:

Aborting program. User refused to continue while asking: /mnt/smb/server.com/set0/full-201306280100.27.dar has a bad or corrupted header, please provide the correct file.
Failed to add set /mnt/smb/server.com/set0/full-201306280100 to catalog.
Backup terminated: backup failed - status: 7424

...and...

==================================
DAILY BACKUP TO WORKSTATION REPORT
==================================
Backup of server.com started at Fri Jun 28 01:00:04 2013 Backup of mysql databases has been done Mounting backup shared directory 10.10.10.11/911 Backup temp directory /mnt/smb/tmp_dir/server.com is mounted and is writable Using set number 1 of 1 Attempt full backup Backup base file name is full-201306280100 Making backup in temp directory Using a backup session timeout of : 88500 seconds


 --------------------------------------------
 51482 inode(s) saved
 with 2722 hard link(s) recorded
 0 inode(s) changed at the moment of the backup
 0 inode(s) not saved (no inode/file change)
 0 inode(s) failed to save (filesystem error)
 263 inode(s) ignored (excluded by filters)
 0 inode(s) recorded as deleted from reference backup
 --------------------------------------------
 Total number of inode considered: 51745
 --------------------------------------------
Rotating backups in a new set /mnt/smb/server.com/set0.
Moving backup files to target directory /mnt/smb/server.com/set0
Updating catalog
*** No backup allowed or error during backup *** Failed to add set /mnt/smb/server.com/set0/full-201306280100 to catalog.

Any ideas? Only started recently. After last updates.