A SQL Backup v6 job looks to have failed and not reported anything back to the GUI / Log.

SQL response told me that our daily all database backup job on MEDSQLTEST didnt start today.

Looking at SQL Server Agent it show the job as still running from yesterday (24th at 7.00am)

The SQL Backup GUI shows that SQL Backup backed up the first database and then looks like it crashed? Looking at the backup files it looks to have done what the GUI displays. Of the 97 databases it only backed up the first one. The job is configured to backup all databases [*]


backupissue.gif
Andrew Hodge
0

Comments

6 comments

  • Andrew Hodge
    Did a quick stop start of the SQL Server agent and SQL Backup service.

    On trying to restart the SQL Backup service I got the following error in the event log

    SQL Backup Agent startup error: error initialising IPC objects. Error creating mutex (already exists): Global\SQBMutex_

    Left it a minute or two and then restarted the SQL Backup agent ok
    Andrew Hodge
    0
  • Andrew Hodge
    Just tried to run the same job again and seem to be getting the same issue
    Andrew Hodge
    0
  • Andrew Hodge
    I changed the backup job details from remove backup files except last 5 to remove files older than last 5 days

    Job seems to run ok now.
    Andrew Hodge
    0
  • Andrew Hodge
    Changed it back to remove all except last 5 and job failing at a different location now, after the 15 or so db

    SQL Agent Job still shows as executing. But nothing from SQL Backup


    backupissue1.gif
    Andrew Hodge
    0
  • mattchandler
    Hi Andrew,

    A bug that's come up with the pre-release is that backup can fail when you delete all but the last 'x backups', but there are encrypted 5.4 (or earlier) backups where you're backing up to. If you're backing up multiple databases the same issue can lead to SQL Backup hanging.

    I suspect this is what's happening here - if you could try removing older backups files from the folder, I'd be interested to hear if the job starts working.

    The fix for this particular bug is already implemented in our internal builds, and this shouldn't affect the final 6.0 release.

    Thanks for getting in touch,
    mattchandler
    0
  • Andrew Hodge
    Will give it a try and let you know.

    I was wondering if it would be possible to refresh the pre-release build that we are testing. 3 or 4 of the bugs I have logged have all come back with having been fixed in newer internal builds. Seems a bit of a waste of our time to be logging all bugs if they are already fixed.
    Andrew Hodge
    0

Add comment

Please sign in to leave a comment.