02-09-2011 04:01 AM
The SQL Server database backup exits with a Status 6 in Activity Monitor. I have found two TN in which two TN have different resolutions. I have also found a MS document which is saying that this SQL error has a FIX available.
My question is that if MS is already saying that there is a FIX available thn why Veritas Netbackup is offering two different solutions. Below are three links for your reference:
http://www.symantec.com/business/support/index?page=content&id=TECH5970
http://www.symantec.com/business/support/index?page=content&id=TECH37307
http://support.microsoft.com/kb/934396 ( See the Error Message 2 )
02-09-2011 05:37 AM
Firstly, look at the date of each publication:
http://www.symantec.com/business/support/index?page=content&id=TECH5970
Article: TECH5970 | | | Created: 2000-01-17 | | | Updated: 2010-01-12 |
http://www.symantec.com/business/support/index?page=content&id=TECH37307
Article: TECH37307 | | | Created: 2005-01-08 | | | Updated: 2005-01-21 |
http://support.microsoft.com/kb/934396
Article ID: 934396 - Last Review: April 28, 2010 - Revision: 6.0
It is clear that TECH37307 is totally irrelevant, because it was written many years ago for NBU 5.x and Windows 2000.
About TECH5970 - you can see that it was updated 3 months prior to the hotfix release.
You can provide feedback and ask Symantec to update the TN with the hotfix info. You can also subscribe to the TN, so that you will receive notification as soon as it's updated.
See this section on the right-hand side of the TN (I provide feedback/suggestions on a daily basis...)
02-09-2011 10:34 AM
Thanks Marianne for your kind reply. What do you think that the TN5970+Microsoft FIX both are the solution
02-09-2011 11:58 AM
We will only know for sure once you've tried it. Good idea to apply one change at a time: I'd say try the hotfix first. I have in all honesty never tried it myself...
If that doesn't solve the problem. look at the recommendations in the TN:
Firstly memory - if SQL is configured to use all available system memory, any other app will suffer - including NBU.
It is also a good idea to schedule filesystem and database backups to run at different times. Also remember to exclude databases from filesystem backups.
TECH5970 looks like a 'best practice' approach for most environments backing up databases.
02-09-2011 03:45 PM
Ain't it the truth?
Don't always take VERITAS documentation as the truth. Experience is also sketchy at times. I don't have your soltion but there is a lot of experience in this forum. Marianne gave some good things to consider. Please let us know the outcome. Thanks.
02-09-2011 08:58 PM
I am also going to do the same thing like first i increase the VM thn second install the FIX and will share the result.
Thanks again for all