August 13, 2013 at 3:29 pm
Hi
I am using sql backup 7 from Redgate and i am having an issue whereby the sql backup process 'sqbcoreservice'is consuming way too much cpu. Way to much means, right now, when the server cpu should be near 1 - 10 % (as it now not being used) it is currently at 50% cpu. When business hours start cpu will go to around 90 - 100%.
Ive just ran sp_whoisactive and i have this:
dd:hh:ss.... waitinfo..........................................................CPU.......... STATUS
00:11:56.....(43006055ms)ASYNC_NETWORK_IO...............32,953.........Runable
I have omitted some of the other info for berevity !!
When i examine the sql server processes that is running its always sqbcoreservice.
We have transaction log backups throughout the day every 10 mins. There are currently no backups being performed by sql backup and there won't be for another 8 hours untill business starts again.
Why am i seeing sqbcoreservice as the cpu bottleneck if no backups are currently happening?
I have posted a question on the RedGate web site...i am still waiting for an answer on that one.
August 15, 2013 at 3:07 am
Just in case anybody else is having an issue with the sqbcoreservice consuming a lot of cpu (although i seem to be only person 🙂 ),
then i have a resolution.
In the end it was quite simple - i just restared the sql back agent !! The processor utilisation immediately dropped down to normal levels.
I have been speaking with lead RedGate developer on this matter and he advises me that the issue is probably caused by the SQL Backup GUI trying to populate the backup timeline history. The GUI will call SQL Backup 'sqbdata' extended Sp, which will then call the SQL Backup Agent service (sqbcoreservice) and apparently it does not know if the GUI has disconnected from the SQL server instance.
Anyway the fix is simple but i had to do it outside of production hours.
Many thanks to Peter Yeoh from Redgate - their team is fantastic !!!:-)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply