Comments
Sort by recent activity
Not the case. Full and log backups are taken in different folders. I have submitted support ticket #F0054297 / comments
Not the case. Full and log backups are taken in different folders. I have submitted support ticket #F0054297
I am running multiple backup jobs for different databases, but in different folders. Each db has it's own folder for transaction log backups. thanks / comments
I am running multiple backup jobs for different databases, but in different folders. Each db has it's own folder for transaction log backups. thanks
I have exact same issue when trying to delete old file: Warning 161: ERASEFILES error: Failed to delete file:... Error code: 32 (The process cannot access the file because it is being used by another process).
Basically, I have SQl agent jobs which runs every 10 min and doing backup transaction log backup using SQL Backup 6.5.1.9.
Periodically, few times a day these jobs literally stuck without reporting fail,
backup was created successfully but I can see that job is still running and stuck on ERASEFILES with Error code: 32 (The process cannot access the file because it is being used by another process).
Jobs hangs forever until manually stopped or killed, But even after stopping stuck job file to be deleted is still used by Redgate SQLBackupAgent. Looks like multiple Redgate processes trying to get to the file at same time. Only workaround I found so far is to restart Redgate SQLBackupAgent service, but issue raised again in less than a day.
Any ideas? thanks a lot / comments
I have exact same issue when trying to delete old file: Warning 161: ERASEFILES error: Failed to delete file:... Error code: 32 (The process cannot access the file because it is being used by anot...