October 13, 2008 at 4:50 am
can anyone suggest the best way to backup DB's used in transactional replication? I am looking to setup a replicated Database which will pull transactions from 3 different databases (Total of about 10 tables) on another server. I'm looking for peoples views on backup / recovery procedures for this setup???
Nothing else will be written to this replicated database so would it be just as easy to reinitialise the subscription if it all goes horribly wrong at the Replicated DB end?
Also, if for example my "Live" databases go pop, our current backup strategy captures log files every 15mins which means we could in theory have replicated data which no longer exists on the Live databases if i have to restore - what is the best thing to do in this instance? Restore live DB's and reinitialise the subscription?
any words of wisdom much appreciated!
_________________________________________________________________________________SQLGeordieWeb:- Jarrin ConsultancyBlog:- www.chrisjarrintaylor.co.ukTwitter:- @SQLGeordie
October 13, 2008 at 2:55 pm
You need to read a bit in BOL about Backing up replicated databases but in short all you need to do is to set the sync-with-backup option on the publication and you should be fine. There are of course trade-offs but you should be the want who determines if you are comfortable with it.
* Noel
October 14, 2008 at 1:42 am
Thanks for that. Unfortunately i cannot afford any latency (well, as little as possible!) so sync with backup on the publication DB is not an option.
Since the replicated DB is essentially going to be readonly and a full snapshot takes roughly 3-5mins, would i be able to get away with just reinitialising a new snapshot from Live to be replicated to get it back up to speed?
_________________________________________________________________________________SQLGeordieWeb:- Jarrin ConsultancyBlog:- www.chrisjarrintaylor.co.ukTwitter:- @SQLGeordie
October 14, 2008 at 1:54 pm
Swirl80 (10/14/2008)
Thanks for that. Unfortunately i cannot afford any latency (well, as little as possible!) so sync with backup on the publication DB is not an option.Since the replicated DB is essentially going to be readonly and a full snapshot takes roughly 3-5mins, would i be able to get away with just reinitialising a new snapshot from Live to be replicated to get it back up to speed?
Sounds OK to me.
* Noel
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply