Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2005 Forums
 SQL Server Administration (2005)
 Server hangs with log shipping

Author  Topic 

steel
Posting Yak Master

107 Posts

Posted - 2010-06-23 : 01:47:43
Dear Experts,

We are having a production environment having HP proliant DL 380 servers haosting windows server 2003 SP2 and SQL2k5 with SP3.The logshipping is enabled for three databases.The server works ok but after some time it hangs .Please help.

Thanks in advance

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-06-23 : 01:55:31
What makes you think it's log shipping that causes the problem? Log shipping is very lightweight, so I would doubt it's causing your server to hang.

Could you explain what you mean by "hang"? "Hang" could mean lots of things, so we need to get clear symptoms from you.

What steps have you done already to troubleshoot this issue? Profiler? PerfMon? DMVs?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-06-23 : 01:55:52
Also, have you rebuilt your indexes in the recent past? How about your statistics?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

steel
Posting Yak Master

107 Posts

Posted - 2010-06-23 : 03:02:53
Thanks for replying..
This server is deployed with 146GB*2 RAID1 and 300GB*4 RAID5.RAID5 contains song content which is being read by other mapped machines(Only read happens during this operation) and our logshipped db are also residing in this RAID5 volume.Whenever we are dissabling logshipping then this server works fine but when we enabled logshipping this server used to reboot and then goes into hang status(this sql server is not able to connect from other machine but we are able to telnet 1433 port). Then we need to give hard boot to this server to make it functioning.It directly indicates some issue with our logshipping setup.

Please suggest.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-06-23 : 03:06:07
Why are you using log shipping if both are on the same system?

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

steel
Posting Yak Master

107 Posts

Posted - 2010-06-23 : 03:16:21
This is the configuration of Secondary server which is also hosting some content.The main Database server is working fine.
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-06-23 : 03:18:00
You should consider not using log shipping, but rather use read_committed_snapshot on the main database or replicate the data to a second system. Log shipping requires that all database connections be closed at the time of the restore, so it is not a good solution if the data needs to be queried often.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-06-23 : 03:18:34
Since you only have one server, I would recommend read_committed_snapshot. Replication would only make sense if you had separate hardware.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page

steel
Posting Yak Master

107 Posts

Posted - 2010-06-23 : 05:58:07
We are having two servers with same configuration.The issue is with the secondary log shipped server.The primary server for log shipping is working ok but the secondary server for log shipping is working abnormally.We are having two seperate machines.
Go to Top of Page

steel
Posting Yak Master

107 Posts

Posted - 2010-06-25 : 07:58:46
Dear Experts,

Please help
Go to Top of Page

tkizer
Almighty SQL Goddess

38200 Posts

Posted - 2010-06-25 : 12:47:43
It sounds like you've got an unstable server (the secondary server). Verify that you are running the latest service pack for hotfixes for both Windows and SQL Server. Open a support case with Microsoft to troubleshoot the server.

Tara Kizer
Microsoft MVP for Windows Server System - SQL Server
http://weblogs.sqlteam.com/tarad/

Subscribe to my blog
Go to Top of Page
   

- Advertisement -