Highlighted

netbackup 7.5.0.7 causing high cpu during sql backup

We have several 2003 and 2008 servers running netbackup 7.5.0.7 and when netbackup tries to backup SQL dbs it causes extreme CPU spikes. We had this same issue with 7.5.0.6 but were able to get an EBB (3342502) patch that fixed it in that version but having since updated, the issue has returned. Anyone else having issues with CPU spikes and are aware of a fix for it?

Thanks

2 Solutions

Accepted Solutions
Accepted Solution!

Hi, All EEB's are not always

Hi,

 

All EEB's are not always include in the maintenance patch. So you could rollback to 7.5.0.6 and add the EEB, or try and add the EEB to 7.5.0.7.

 

Best check with support.

View solution in original post

Accepted Solution!

Yes, from the Etrack number

Yes, from the Etrack number you have provided, it doesn't look like this was resolved in the code until 7.6.0.3 (or 7.6.1).  If this is causing you problems and you can't roll back AND you can't upgrade, you should open a new case with support and ask for a 7.5.0.7 version of the EEB.  It would probably help with the Engineering escalation if you let your TSE know your previous case ID under which they handed you the 7.5.0.6 EEB.  Good luck!

View solution in original post

2 Replies
Accepted Solution!

Hi, All EEB's are not always

Hi,

 

All EEB's are not always include in the maintenance patch. So you could rollback to 7.5.0.6 and add the EEB, or try and add the EEB to 7.5.0.7.

 

Best check with support.

View solution in original post

Accepted Solution!

Yes, from the Etrack number

Yes, from the Etrack number you have provided, it doesn't look like this was resolved in the code until 7.6.0.3 (or 7.6.1).  If this is causing you problems and you can't roll back AND you can't upgrade, you should open a new case with support and ask for a 7.5.0.7 version of the EEB.  It would probably help with the Engineering escalation if you let your TSE know your previous case ID under which they handed you the 7.5.0.6 EEB.  Good luck!

View solution in original post