August 21, 2012 at 3:10 am
Hi,
Last week successfully upgraded to SQL 2008 R2 from large size SQL 2000 database (size 648 GB), application working fine wt no issues.
Management decided to configure HA solution in this database. (not for clustring) most of the Data like text and image, GUID column format type.
Could anyone suggestion me? which is the best method as follows,
1. Replication, 2. Log shipping, 3. Mirroring
rgds
ananda
August 21, 2012 at 3:24 am
No where near enough information.
What's the RTO? What's the RPO? Is automatic failover required? How difficult can the fail-back process be? What edition do you have? etc...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2012 at 4:31 am
yes, we have discuss with vendor as well as application owner, they are accepting as following condition.
OS - Win 2008 R2 64bit enterprise edition
DB - SQL server 2008 R2 enterprise edition
Installed single default instance. RAM - 8 GB,
Recovery Time Objective (RTO). This is the duration of the outage. ( Seconds)
Recovery Point Objective (RPO).
This is often referred to as a measure of acceptable data loss (Mintues)
Is Automatic Failover - No, manual failover process.
thanks
ananda
August 21, 2012 at 4:36 am
If automatic failover's required then your only option (of the ones listed) is mirroring. Replication provides neither a failover mechanism nor a fail back. Logshipping the failover is manual.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2012 at 4:44 am
GilaMonster (8/21/2012)
If automatic failover's required then your only option (of the ones listed) is mirroring. Replication provides neither a failover mechanism nor a fail back. Logshipping the failover is manual.
Mirroring have two method, auto & manual failover.
automatic failover require one more system for configure witenss server, if choose auto failover, does this option any impact on performance in production server (principal server) ?
August 21, 2012 at 5:02 am
Synchronous mirroring (whether it's automatic or manual failover) can affect performance. Make sure that the network is adequate for the load and the mirror server is appropriately specced.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2012 at 5:42 am
ok, thanks for reply..
I am going for choosing Synchronous Mirroring (without witness server, manual failover process) , and writting data at a time at mirror server disk.
principal/ mirror server located at same location. and we have 100mbs n/w speed. Is it sufficent for data tranfer to mirror server.
Inital database size 640 GB now.
August 21, 2012 at 6:08 am
ananda.murugesan (8/21/2012)
Is it sufficent for data tranfer to mirror server.
No way to answer that. You need to check that the network is adequate for the workload you have on your server.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
August 21, 2012 at 7:43 am
If you use mirroring, you may need to modifiy the application connection strings to automatically failover to the active server.
August 21, 2012 at 2:22 pm
ananda.murugesan (8/21/2012)
and we have 100mbs n/w speed. Is it sufficent for data tranfer to mirror server.
This would quite possibly struggle to meet the needs for the public network access let alone mirroring, gigabit networking would be more suitable.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply