Login to participate
Backup and Archiving IdeasRSS
0 votes
SQL Backup
0 Agree, 0 Disagree
I came accross this issue when for some reason our SQL Transaction log backups were failing with a Status 2. Our Master/Media server was running some Transaction log backups and rebooted itself for some reason or another. Once back online Transaction log backups were failing with a Status code 2. Now after alot of looking it seems that SQL thought the backups were still running and there were orphaned dbbackex.exe process's running on the SQL Client (these were still running after 4 days!!). What would be good is if either those processes timed out after no contact with the media server for X amount of time or when Netbackup runs another transaction log backup it told you that there was a Backup in progress on the client.