July 9, 2009 at 1:41 am
Hi,
Our management wants to find out the sloution for the below scenario.
We have 2 locations. In one location, we have 4 application servers(2 IIS and 2 Web Servers) and active passive clustered sql server 2005.Now they wants whole environment should exist on secondary location and that should survive the Business in case the location 1 has completely destroyed by fire/hurricane
Location1:
IIS server1
IIS server2
Web server1
web server2
SQL1(active node)
SQL2(passive node)
virtual server name: SQLVS
all servers in abc.com
Location2:(we can not have same server names at location 2 so we build the below servers in location2)
IIS server3
IIS server4
Web server3
web server4
Sql server: SQL3
Instance name: Ins1
virtual server name: SQLVS
all servers in abc.com
Now for the database part, we can use log shipping the database to location2. But how application changes will be applied to location2? How failover and role switch works for this scenario?
For this scenarion Is log shipping good solution? or something else to consider?
I appreciate your inputs..
Thanks
July 10, 2009 at 2:45 am
You need to make changes in the Application string to point out to these servers .That should be taken care by the application guy .
Secondly , with log shippng there is a manual process involved :
take the tail log backup (which is nto possible as your primary site will be totally destroyed) , restore it on the secondary databases one by one , apply any log that is not applied but backed up (which might also get burned with the server)...
So the approach of log based restore for the DR site is not suitable .
Instead you can go for transaction based approach i.e. Mirroring or Replication .
If the number of mirrored databases are 10 [excluding system databases]or less and you are on 32 bit then it should be fine .If the databases are more and you are on 64 bit , then also it will work (there is a list available on net how many you can mirror or check for the whitepaper easily available)..
You can configure Peer to peer replication (as every publisher will be a distributor .So not all the dataloss will take place together ) OR mirroring with witness or a combination of mirroring and replication .
For any situation where your secondary is not used in parallel you need nto to spend extra on license ..
HTH ..
Abhay Chaudhary
Sr.DBA (MCITP/MCTS :SQL Server 2005/2008 ,OCP 9i)
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply