April 10, 2008 at 8:43 pm
I have recently inherited a server, which is having trouble with its nightly backups.
On investigation, I find that the problem lies with the verification of the backups.
I can now create the situation with ease - simply initiate a verify on any backup file, and the disk writes to C: immediately rocket. Before long, the server locks up.
CPU remains very low.
Memory is not at all stressed.
This is on SQL2000, SP4.
Can anyone give me any pointers as to why this is happening?
April 11, 2008 at 8:44 am
Can you restore the backup on another server and verify that the backup is good?
-- You can't be late until you show up.
April 11, 2008 at 9:16 am
check your hardware as well. Look for errors in the event log.
Are you backing up to a new file every night or the same one. Not sure why writes skyrocket. A verify should be reads.
http://msdn2.microsoft.com/en-us/library/aa238412(SQL.80).aspx
April 13, 2008 at 3:59 pm
Thanks for the reply.
It is the writes which have got me wondering too!
I have tested some restores - they work fine.
The raid setup on this server leaves a lot to be desired.
Unfortunately, it isn't very likely to change in the near future.
The C: and the backup drive are on the same array.
During the Verify, I see a number of the following Event log errors:
"The device, \Device\Scsi\cpqcissm1, did not respond within the timeout period.".
I have had our server people check the array out, but they insist that it is not throwing any errors. Simply overworked.
Being a new server to our fold, I have no history to go by.
The last (weekly) backup which went through without fault was 20 March. I can't see whether it experienced the same errors.
In the interim, switching off the verify is a good enough workaround.
I am just trying to get to the bottom of the reason for all those writes!
Regards
BB
June 24, 2008 at 12:23 pm
Have a look at this link and see if it helps.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply