Some basic log shipping questions | SQL Server Performance Forums

SQL Server Performance Forum – Threads Archive

Some basic log shipping questions

Hi folks,<br /><br />I have a question or maybe some more. <img src=’/community/emoticons/emotion-5.gif’ alt=’;-)’ /><br /><br />In case of a system failure one of our customers wants to have their data back running asap and also as little data loss as possible (anyone out there how does not? <img src=’/community/emoticons/emotion-5.gif’ alt=’;-)’ />).<br /><br />So I look around how to manage this and found log shipping to be maybe a good solution.<br /><br />My questions with this topic are the following:<br /><br />- When implementing log shipping successfully is it possible in the event of system failure of the primary server to just replace it with the second one, then change the DSN accordingly and have my application back up running?<br /><br />- What are the performance issues with log shipping, esp. when doing log shipping to more than one backup server (if this is possible at all) or when doing log shipping for more than one database?<br /><br />- Is log shipping to more than one servers possible? Would it be possible to cascade log shipping, i. e. to set up the secondary server to be the primary server to a third one in means of log shipping?<br /><br />Thanks for your help.<br />Daniel<br /><br />
1) You need to go for clustering in this case, to take care of dsn settings automatically. In log shipping you need to have some downtime during role reversal and manual settings from application to talk to secondary server for the database. 2) No performance issues as long as the network is well designed to handle the file copy and ensure similar levels of MDAC, Service packs are deployed between primary and secondary servers. 3) MSKB FAQ for log shipping refers:
Read the following Microsoft Knowledge Base article about a known problem that can cause errors while performing a role change that involves multiple secondary servers-
http://support.microsoft.com/kb/300497/EN-US/ FIX: Log Shipping: Cannot Change Role From Secondary to Primary When Database Names Are Different In order to make sure the log shipping is working properly you must perform the role reversal.
Satya SKJ
Moderator
http://www.SQL-Server-Performance.Com/forum
This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
]]>