Warning 161 and Error Code 32

khickman32 · August 12, 2016 9:29AM

We are currently backing up 9 of our User databases to the local server and then copying the backup files to a network location. We delete the local backup files that are older than 1 day and we delete the network backup files older than 7 days. The backup files are successfully being copied to the network location and SQL Backup 7 is successfully deleting the older local backup files, but we are randomly receiving the error "Warning 161: ERASEFILES error: Failed to delete file: "\serverfoldersqlservernameackupfilename". Error code: 32 (The process cannot access the file because it is being used by another process)" when deleting the network backup files. This error occurs on random days and on random databases. There is no consistency. We have other SQL Servers using SQL Backup 7 using the same method without errors. I downloaded and ran process explorer to see what process or application was accessing the backup files and there were no locks on the file. I then manually ran the SQL Backup 7 backup job and received the same warning and error above. Any help you can provide in resolving this error would be greatly appreciated. Thanks.

petey · August 14, 2016 11:03PM

Is your network share a Windows box too? If so, you should run Process Explorer there to see if any applications on that box are accessing the files.

khickman32 · August 15, 2016 8:34AM

Yes the network share is a windows box as well and that is where I ran the Process Explorer and no applications or processes are accessing the files.

petey · August 15, 2016 12:05PM

Could you please send me the contents of any single log file that shows the error? SQL Backup generates a log file for each process that it runs. The default folder where the logs are stored is C:ProgramDataRed GateSQL BackupLog<instance name>, unless you're using Windows 2003 or older OSs, for which the default folder is then 'C:Documents and SettingsAll UsersApplication DataRed GateSQL BackupLog<instance name>'. You can send the log file to peter.yeoh@red-gate.com.

khickman32 · August 15, 2016 3:56PM

I have sent you an email with the requested log file. Thanks!

petey · August 15, 2016 11:46PM

Thanks for sending the log over.

Do you have a scheduled job that backs up the transaction log for the same set of databases, which also copies files to the same network share and also uses the ERASEFILES option? If you do, could you please post the backup command that's used to back up the transaction logs? Thanks.

khickman32 · August 16, 2016 8:50AM

Yes, we backup the transaction log at 1 AM, but these files are not copied to a network share. The local backup log files are deleted after 1 day.

petey · August 16, 2016 9:44AM

In that network share (\W*****3SQLBackupsW****E'), are there any other backup files stored in there that is not copied from this server?

khickman32 · August 16, 2016 9:54AM

No, there are no other files or folders in that directory from other servers. There are other folders from other SQL Servers under the SQLBackups folder that use the same method with SQL Backup 7 and we are not having any issues with those.

petey · August 16, 2016 11:21AM

Is this server only recently been copying the backup files to the network share, relative to the other servers that are not having issues?

khickman32 · August 23, 2016 8:58AM

No, this server was created several months back and all SQL servers were setup to copy their backup files to this server around the same time. The nightly backups for each server are ran at different times, so they won't conflict with resources as well.

petey · August 24, 2016 1:40AM

I have created a support ticket for this issue for easier communication.

Warning 161 and Error Code 32

Comments

Product Learning

Community Forums

Events & Friends

Simple Talk