July 16, 2002 at 8:51 am
Just wanted to know if any of you out there has encountered this wierd going ons.
I have been running these backup for months now and this just happened not too recent.
* Backing up a number of db through jobs.
* Jobs would hang.
* Reboot whole machine
This is the first time that I have encountered this event.
Config:
* Windows NT 4 SP6a
* SQL 7 SP2
Thanks.
July 16, 2002 at 10:21 am
Have you checked disk space? Any errors when the job hangs? It could be the file has grown and slowed the job and some other backup (tape) is interfering?
Can you give any more specifics?
Steve Jones
July 16, 2002 at 11:17 am
Some details on how you perform your backups will be helpfull as well. Are these disk or tape backups? How often? Etc.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
July 16, 2002 at 2:57 pm
The job is dumping the files into another server as a dumping ground. This server has tons of space in it. So far only 25% of the total disk space is in use.
Then from there, the dumps are backed up to tape.
Their time intervals between the dump from SQL to tape is rather far.
Thank you for your input.
Edited by - mtaburada on 07/16/2002 2:58:33 PM
July 16, 2002 at 9:19 pm
Do you have it verifing the backups? Also check to make sure the file itself is not locking or a netowkr issue that may exists. Problem with remote backups is there are external variables you introduce that make trouble shooting a larger issue.
"Don't roll your eyes at me. I will tape them in place." (Teacher on Boston Public)
August 1, 2002 at 1:59 pm
I have had exactly this same problem on exactly this same configuration (NT 4.0 SP6a and SQL Server 7.0 SP6) twice in 2 years. Backup jobs were working fine and suddenly started hanging. The last time was a week ago after there was a hard shutdown because of a bad internal battery. After replacement and restart, everything worked except the SQL Server Agent Jobs. Anyway, in testing out the Outlook Profile for the Login account that SQL Server Agent runs under, I discovered that at least 1 binary for OUTLOOK was corrupt. I tested that this was a problem by turning off the notifications in the jobs and they worked fine. So SQL Server isn't quite intelligent enough to detect if OUTLOOK is working correctly or not. I reinstalled OUTLOOK and everything works fine again. Don't know if you have the same setup with jobs including notifications, but if you do, this might help.
"All your database are belong to me"
"All your database are belong to me"
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply