July 7, 2013 at 9:06 pm
Dear All,
My current SQL configuration is SQL 2008 standard edition (Vmware virtualized 2 node failover cluster) on windows 2008 R2 .
Whenever I run my SQL backup the CPU shoots up over 90%. How do I restrain this so that the CPU does not go up above 60%. Is there any way I can prioritize this task ?
Many thanks,
Jai
July 8, 2013 at 2:15 am
I'm sure this can be done with Resource Governor
July 8, 2013 at 3:04 am
Thanks, Is this something that can be done upfront even before the job actually kicks in (my job is a scheduled task)
July 8, 2013 at 3:12 am
mJai (7/7/2013)
Dear All,My current SQL configuration is SQL 2008 standard edition (Vmware virtualized 2 node failover cluster) on windows 2008 R2 .
Whenever I run my SQL backup the CPU shoots up over 90%. How do I restrain this so that the CPU does not go up above 60%. Is there any way I can prioritize this task ?
Many thanks,
Jai
Sounds like there's something misconfigured. Taking a backup shouldn't cause that much CPU usage. What's the CPU usage on the VMware host. How is the IO throughput during backup.
[font="Verdana"]Markus Bohse[/font]
July 8, 2013 at 3:17 am
Hi - You can use Resource Governor. But I would recommend to find why cpu usage is high during backup rather than solving it temporarily/ restricting it to certain percentage of cpu.
Is the usage consistently 90+% through out the backup?
Which time are you taking the backup? (Production or off hours)
Which type of backup?
What is the size of database and backup file?
Are you using compression mode to take backup?
What is the waiting types happening during taking the backup?
How many processors are in the server?
What is the physical memory size?
Are you taking the backup to disk/ tape/ network path?
Find out if there is cpu or any other resource bottleneck there.
July 8, 2013 at 11:05 pm
I shall get back after conducting couple of tests. Thanks.
July 15, 2013 at 3:00 am
Found the culprit. It was a 3rd party tool causing this havoc!
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply