November 3, 2006 at 11:59 am
We currently have db running from one server (MSSQL 2005 Standard). The db is about 60GB in size and we are planning on having a standby db for fail over purposes.
The db serves high volume website, and we want to have the standby db (with standby webserver) at remote location (outside of our office).
What is the best strategy to accomplish this? Will log shipping be good enough for this scenario?
We have T3 (45mbps) connection to the remove facility.
If someone has had good experience with this (or knows someone), we're willing to pay someone to help use setup a plan for this.
November 3, 2006 at 6:47 pm
log shipping should be fine. That would be my first thought. at my current client we quickly gave up on log shipping and went to a snapshot... which locked the user DB for 13 minutes while creating the snap.
Thank-you,
David Russell
Any Cloud, Any Database, Oracle since 1982
November 6, 2006 at 2:21 pm
Andrew,
Log shipping is an important part of the solution, but will require manual intervention to activate your remote database as the new primary. You might want to look at database mirroring; set it up with a witness and obtain the benefits of automatic failover in the event your primary database becomes unavailable for any reason.
Elliott
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply