April 24, 2007 at 11:22 am
In the most recent 3 weeks, we got an error for the SQL agent job---some DTS job did not run or failed to run. Some Backup jobs were not kicked off until a later time (not in the schedule). When we look at OS: we got
Server Time Status
MRDDPRODSQL 4/24/2007 12:13am Device Accessible
MRDDPRODSQL 4/24/2007 12:03am Device Inaccessible
MRDDPRODSQL 4/23/2007 11:58pm Device Accessible
MRDDPRODSQL 4/23/2007 11:36pm Device Inaccessible
MRDDPRODSQL 4/23/2007 11:33pm Device Accessible
MRDDPRODSQL 4/23/2007 11:18pm Device Inaccessible
.....
Does anybody know why this SQL server behaves like this for most recent 2-3
weeks???? Before that time, the server ran all job as expected.
Thanks.
April 25, 2007 at 7:37 am
Almost always, any issues with SQL Server disk devices are always caused by problems at a lower level in the IO subssytem, controllers, DISK, firmware or OS. I would look in the NT event logs, all 3 of them. The late night timing of the issue implies a possible connection to the nightly disk backups.
April 26, 2007 at 10:19 am
You may also have to look at your NAS (Network attached storage) or other servers depending on where these devices actually map to. Potential causes other that local SQL Server disk backups to look at are NAS backups, NAS disk maintenance and storage expansions; server maintenance and server disk expansions.
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
April 30, 2007 at 1:13 am
If you use a SAN or NAS, where is your tempdb located? I had a server that reacted this way because tempdb was on the SAN.
5ilverFox
Consulting DBA / Developer
South Africa
May 1, 2007 at 7:53 am
Some other possibilities:
Have the permissions of the SQL Server / SQL Agent services login been changed? Maybe can't access the network share any longer?
Is there a hung process from the initial failure that is causing subsequent failures?
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply