GUI falsely reports job in progress

Compresses, encrypts, secures and monitors SQL Server backups.

Moderators: Chris Auckland, eddie davis, Colin Millerchip, Brian Harris, james.billings, RBA, petey

GUI falsely reports job in progress

Postby degnoski » Fri May 27, 2011 2:43 pm

A t-log backup runs every two hours for several months. Suddenly the job is not running but the SQL Backup V6.3 gui says it's in progress. This has been going on for several days now. SQL Server indicates that the job is not running. I deleted the job from SQL Backup but the gui still reports the job in progress. I created a new job to replace the problem job and it is running fine. How do I force the gui to end(release) this job?
degnoski
 
Posts: 2
Joined: Fri May 27, 2011 2:33 pm

Fixed

Postby degnoski » Fri May 27, 2011 4:10 pm

I stopped the SQL Backup Agent service and restarted. Problem solved.
degnoski
 
Posts: 2
Joined: Fri May 27, 2011 2:33 pm

Is this error been fixed in 6.5.1.9

Postby hitsgdba » Thu Apr 26, 2012 4:32 pm

We encountered a similar error today where it appeared as if a Txn log backup was still processing from 4 days ago, even though the job history did not indicate an error. I closed the client and opened it back up and it disappeared.

We are doing backups with VERIFY_ONLY. Is there a fix/patch in place to resolve this issue or do we need to turn off the VERIFY_ONLY option?

(SQL Server 2005 with SP4 32bit Clustered)


Regards.

Paul
hitsgdba
 
Posts: 2
Joined: Thu Apr 26, 2012 4:25 pm

Postby ChrisAVWood » Thu Apr 26, 2012 9:48 pm

hitsgdba,

Yous don't mention what version you are running other than the possible subject line.

We are running 6.5.2.9 and have this happen every so often. We even added a VERIFYINTERVAL parameter as we had been told it might help with this issue.

Chris
English DBA living in CANADA
ChrisAVWood
 
Posts: 308
Joined: Tue Dec 18, 2007 6:18 pm
Location: Edmonton, Alberta, CANADA

Backup Pro Version

Postby hitsgdba » Fri Apr 27, 2012 2:16 pm

6.5.1.9 is the version we are on. Here are the parameters from the job.
WITH ERASEFILES = 3, DISKRETRYINTERVAL = 30, DISKRETRYCOUNT = 10, COMPRESSION = 0, INIT, THREADCOUNT = 7, VERIFY
hitsgdba
 
Posts: 2
Joined: Thu Apr 26, 2012 4:25 pm

Postby ChrisAVWood » Fri Apr 27, 2012 3:23 pm

I think that it was 6.5.2.9 that introduced VERIFYINTERVAL. I am sure that a Red Gate support analyst will confirm. It delays the time at which the verify process begins so that data in cache can be written to disk if I rememebr correctly. I also think that there is a later version 6.5.2.18 that may have other improvements for the verify process.

You might also be able to try V 7 that came out earlier this week.

Chris
English DBA living in CANADA
ChrisAVWood
 
Posts: 308
Joined: Tue Dec 18, 2007 6:18 pm
Location: Edmonton, Alberta, CANADA


Return to SQL Backup 6

Who is online

Users browsing this forum: No registered users and 0 guests