April 9, 2007 at 3:19 pm
Hello,
We will be running a near-mission critical SaaS application(99.99% or higher uptime wanted) for our clients soon and a large issue we are having involves SQL replication between our two remote data centers.
We want to of course ensure data consistency/integrity, ease of fail-over, and have regular testing intervals setup once we go live.
The servers are stand-alones with no domain controller(s) involved. Our application requires the transaction logs to be replicated over in order to start up successfully. We'd like this to happen within a near-live or live situation...this rules out cold servers we believe and possibly "warm" servers depending on everyone's definition.
What are some of the best practices in your opinion to our needs? Cost isn't a high concern, however we're looking for a non-vendor based solution currently, ie native to the MSSQL 2005 tool set and/or custom scripts.
Thank you.
April 10, 2007 at 4:17 am
have you looked into database mirroring?
It might be a better option than log shipping
ron
April 10, 2007 at 5:39 am
Log shipping is always going to give you some sort of delay or data loss. You can reduse the time between log backups and restores to a minimal, but when you have a failure, you will have lost the data since your last transaction log backup and/or you will have to wait for the final log file to be restored.
If you are looking for a failover solution that will be up in less than 10 seconds, you will need to go another direction to do it reliably.
Clustering is obviously the fastest and most transparent failover solution, but multiple sites can make this complicated and expensive. Mirroring is probably a good direction for the bit of requirements you have explained so far.
April 10, 2007 at 7:27 am
if we go with db mirroring would it be best practice to place the witness server in the same datacenter as the mirror server? we don't anticipate major network issues or other downtime in our primary dc, but if it happens we need to be very certain that our data will be available and up2date. our application is 100% sql driven with an asp.net frontend.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply