August 6, 2009 at 1:13 am
In LogShipping, do we need to do a manual failover in case of primary failure OR will the failover to secondary take place automatically ?
August 6, 2009 at 2:01 am
its a manual process in which you will need to restore the latest tlog to the secondary with recovery then do something to repoint your applications/users to the new server
August 6, 2009 at 3:24 am
So, what in case if the primary fails and no one is around to monitor this ? You mean there should be DBA who should be sitting and constantly watching the primary server to act immediately in the event of failure ?
August 6, 2009 at 3:41 am
You would generally setup alerts to monitor the jobs and then act upon them when neccesary. Log shipping is not seen as a warm/hot solution, clustering (sql 2000 onwards) and mirroring (2005 onwards) are primarily used for this.
Although i have never done it, there is no reason you couldnt automate the steps required to bring the secondary server to a state where it can begin taking connections, and have that script run on failure of the primary server.
August 6, 2009 at 4:06 am
If you are looking for automatic failover than you should think about clustering or mirroring option.
Refer following link for further detail:
http://msdn.microsoft.com/en-us/library/bb510414.aspx
HTH
---------------------------------------------------
"Thare are only 10 types of people in the world:
Those who understand binary, and those who don't."
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply