| Author |
Topic |
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
 Posted - 2005-04-04 : 02:28:35
|
this is on sqlserver 7.0i've inherited this box with sql server 7.0 and backup is done via tape coz the drive is just enough for the mdf and ldf files.problem is the tape drive is now failing. i've redirected the backup to a drive (newly attached) and the job is being cancelled after a few seconds whenever i run it.Here's the message from job historyquote:
The job was stopped prior to completion by Shutdown Sequence 0. The Job was invoked by User sa. The last step to run was step 1 (Step 1).
anyone please help, mdf is 19GB in size, backup drive is 111GB, any idea is better than no idea at all...--------------------keeping it simple... |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-04 : 06:40:53
|
| Look in the application event viewer and the SQL Server error logs. They will usually have a much more descriptive error. Post whatever you find there applicable to this failure. If they don't have more information than this, go into the job step and have the job write the output to a file. See what the file says. It's going to be hard to help you with this amount of information. It could be all kinds of things.MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-04-04 : 07:59:14
|
sad to say, that's all i got,i tried running the backup procedure using QA and it keeps disconnecting after sometime and givesquote:
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionCheckForData (CheckforData()).Server: Msg 11, Level 16, State 1, Line 0General network error. Check your network documentation.Connection Broken
any help will be appreciated--------------------keeping it simple... |
|
|
|
jason
Posting Yak Master
164 Posts |
Posted - 2005-04-04 : 15:26:43
|
| Is the newly connected drive local or network?If local, are you using a controller card for the new drive?Can you transfer data from one of the original drives to the new one? Try shutting down the SQL server and transfer the db to the new volume. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-04-04 : 21:45:59
|
quote:
Originally posted by jason
Is the newly connected drive local or network?If local, are you using a controller card for the new drive?Can you transfer data from one of the original drives to the new one? Try shutting down the SQL server and transfer the db to the new volume.
Yes Jason, I can transfer files, folders to the new drive and yes there's the controller card too.Actually, the backup file was created but is smaller than expected, sometimes ~1GB, ~8GB. I know this is not the complete backup because QA stops the transaction with the error message I listed before--------------------keeping it simple... |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-04 : 23:32:03
|
| Are you having this trouble with anything else? Try setting up a continual file copy to the drive. Just copy a 10 meg file (for example) back and forth repeatedly. See if you get failure there. If so, I would start by replacing the drive. If that doesn't work, replace the controller card.Is your SQL Server 7.0 server and OS up to the latest service packs (laughing hysterically)?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-04-05 : 02:05:52
|
ha ha ha, yes they are derrick  i also tried doing some backups of other databases and they were successful without a hitch, the main difference is that the other backups were considerably smaller ~2GBdo you think it's the size that's making the difference? (no pun intended  )--------------------keeping it simple... |
|
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2005-04-05 : 02:14:33
|
Just upgrade to SQL Server 2000. It will be quicker than troubleshooting this.  I can't believe it's the size making a difference. I would seriously look at replacing the disk drive to see if that fixes anything. There's not that much more you can do. Don't you have a spare in your pocket?MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2005-04-05 : 05:51:34
|
| i was afraid you'd say that, problem is this server houses a third-party program and their support sucks!i guess i'll try to change the new disk to a newer one if this fails, then bye bye to this serverthanks for the replies and insights--------------------keeping it simple... |
|
|
|
jason
Posting Yak Master
164 Posts |
Posted - 2005-04-05 : 10:22:31
|
| I would check the bandwidth settings on the controller card. If possible, try turning it down a notch (i.e, 40MB transfer rate to 10MB transfer rate). I experience issue with backup once where the controller card was moving faster than the backup could handle. This only happened with large transfers. Clean the tape drive r/w heads. |
|
|
|
|
shutdown sequence 0