May 22, 2012 at 3:17 pm
I have a local site (production) and I have a DR site located many states away.
Thanks to the help from this site, I setup mirroring. Which worked fine until I had huge amounts of inserts, which bogged down the server too much.
Company won't pay for 2005 Enterprise edition (x2) to setup async mirroring. So, bottom line I can't mirror.
Can't do merge replication, cause I can't change schema at all.
What are my options? I was even thinking about writing a SSIS package to move the data once a day and restore daily..obviously not preferred.
May 22, 2012 at 3:34 pm
May 23, 2012 at 1:39 am
What is your RTO, RPO, once you know that information you can then decide on the best HA/DR method to take.
May 23, 2012 at 1:54 am
krypto69 (5/22/2012)
I have a local site (production) and I have a DR site located many states away.Thanks to the help from this site, I setup mirroring. Which worked fine until I had huge amounts of inserts, which bogged down the server too much.
Company won't pay for 2005 Enterprise edition (x2) to setup async mirroring. So, bottom line I can't mirror.
Can't do merge replication, cause I can't change schema at all.
What are my options? I was even thinking about writing a SSIS package to move the data once a day and restore daily..obviously not preferred.
how about log shipping ?
MVDBA
May 23, 2012 at 2:38 am
If latency is an issue have you tried extending the timeout period of the mirroring setup? ALTER DATABASE <mydb> SET PARTNER TIMEOUT <int>. Max int value can be up to 2^31-1 (2,147,483,647) seconds. If latency ranges from 0 seconds to, let's say, 10 minutes, setting this value to 660 (11 mins) may provide the flexibility you need.
If it's a question of server load and performance degradation, have you collected any evidence of this using e.g. wait stats and other DMVs? If so, could you post these?
Thanks
---
Note to developers:Want to get the best help? Click here https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help (Jeff Moden)
My blog: http://uksqldba.blogspot.com
Visit http://www.DerekColley.co.uk to find out more about me.
May 23, 2012 at 6:35 am
I was thinking about log shipping...
My intial google - seems like log shipping is kinda a bitch to setup?
May 23, 2012 at 6:43 am
krypto69 (5/23/2012)
I was thinking about log shipping...My intial google - seems like log shipping is kinda a bitch to setup?
not really - in sql 2000 it was an enterprise edition only feature, so most people "rolled their own", which was a bit of a pain.....
have a look at the wizard in management studio, you'll find it very simple
MVDBA
May 23, 2012 at 6:44 am
Log shipping is pretty easy to set up, in my experience. My first DR plan, when I had been a DBA for about 2 months, was log shipping, because it was easier to set up and run than replication or mirroring. Worked well enough.
The problem with log shipping is it can be a pain to "fail back" to your primary server after it comes back up. Easy enough to deal with unless your full backups are big enough to be a problem when you first send those over.
But, main point, when I was a newbie DBA, I found log shipping easier to set up and understand than other DR solutions. Might just be me, of course.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
May 23, 2012 at 2:27 pm
Gotcha..
thanks guys I'm gonna stick with mirroring..for now..
Thanks again for all the advice
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply