Backup Central

I was backing up a Windows Server 2003 with BackupPC when the hard disk failed. I purchased a new hard drive and reinstalled BackupPC on Ubuntu. The initial setup was simple since I thought that the client was completely configured. I am however facing a problem with incomplete backups. Whenever BackupPC encounters a locked file, that somebody has opened via network share, it throws up an error as follows -

full backup started for share shared
Xfer PIDs are now 8448,8447
[ skipped 2 lines ]
tarExtract: Use of qw(...) as parentheses is deprecated at /usr/share/backuppc/lib/BackupPC/Storage/Text.pm line 302.
tarExtract: Use of qw(...) as parentheses is deprecated at /usr/share/backuppc/lib/BackupPC/Lib.pm line 1425.
[ skipped 120822 lines ]
NT_STATUS_SHARING_VIOLATION opening remote file \Insitu_experiments\Analyzed_data\GaN_NW_Piezoelectricity\~$CurrentVoltageMagnitudeCalculationsControlTests.xlsx (\Insitu_experiments\Analyzed_data\GaN_NW_Piezoelectricity\)
NT_STATUS_SHARING_VIOLATION listing \Insitu_experiments\Analyzed_data\GaN_NW_Piezoelectricity\*
NT_STATUS_SHARING_VIOLATION listing \Insitu_experiments\Analyzed_data\*
NT_STATUS_SHARING_VIOLATION listing \Insitu_experiments\*
NT_STATUS_SHARING_VIOLATION listing \\*
[ skipped 45 lines ]
tarExtract: Done: 0 errors, 117221 filesExist, 82081189209 sizeExist, 47478098034 sizeExistComp, 117221 filesTotal, 82081189209 sizeTotal

Now I imagine this is expected since the smbclient is incapable of accessing locked files. However the problem is that BackupPC then proceeds to backup about 40 more odd files before aborting the backup completely with the last line being the tarExtract. There are no further errors.

Subsequent incremental backups create the folder structure but don't backup any of the files in the folders that are created. The share I'm trying to backup is approximately 1TB and I have never managed to get a backup that is more than 500GB. I'm not sure what the issue is and I'd appreciate any help.

Thanks.

I ran the full backup again and it seems that BackupPC stops working pretty soon after any error. Here's another error message I got -
full backup started for share shared
Xfer PIDs are now 11512,11511
tarExtract: Use of qw(...) as parentheses is deprecated at /usr/share/backuppc/lib/BackupPC/Storage/Text.pm line 302.
tarExtract: Use of qw(...) as parentheses is deprecated at /usr/share/backuppc/lib/BackupPC/Lib.pm line 1425.
[ skipped 193446 lines ]
NT_STATUS_OBJECT_NAME_NOT_FOUND listing \New folder\*
NT_STATUS_OBJECT_NAME_NOT_FOUND listing \\*
[ skipped 69 lines ]
tarExtract: Done: 0 errors, 184740 filesExist, 234342136045 sizeExist, 137319276043 sizeExistComp, 185076 filesTotal, 235960983711 sizeTotal

It only processed about 50 odd files after the error and then stops the backup. Has anybody come across this before?

I guess this is pretty obvious, but I thought I'd just put it out there. In order to get a full backup I just manually restarted the client and then set BackupPC to do a full backup. The restart basically removes all file locks so the Backup proceeds without any errors. What I'll do (since I only really need to back up one client) is schedule a restart task at night when there are no active users and schedule BackupPC to start a half hour or so after that.

If anybody has a neater solution leave a message.

Cheers,
Ludakrish