April 15, 2008 at 8:08 pm
I have a issue, we need to keep our production server using on other location by taking a cold/warm backup onto a standby server with transactional replication..
what is the best way to implement this.
How to take the cold/warm backups? How to move the databases to the standby server? and how to implement T-replication while the server is in standby mode,and how to prepare the standby server running in a Disaster Recovery scenario?
Thanks
April 15, 2008 at 9:05 pm
if you need a stand by server, replication may not be the best option. it has some requirements. here is article that you may want to read first.
http://www.sqlservercentral.com/articles/Replication/logshippingvsreplication/1399/
April 16, 2008 at 8:56 am
that SSC article was written in 2004 so pre-dated SS2005. you should now also consider database mirroring. each has de/merits.
my suggestion is Log-Shipping for D/R as you can recover to a particular point in time (the other solutions will blindly replay badstuff [eg table drop] in the DR copy).
be aware that the *.TRN files [pulled in by L-S agent job] are applied to the standby/readonly db in D/R [by another L-S job], but you MUST also get the .BAK file (from db-dump on LIVE) copied to DR site [e.g. via VSS or DT].
if you decide that you needed the point-in-time to be earlier [eg. prior to such drop table!] you would have to start with prior .BAK and roll the *.TRN forward, but if you don't have that .BAK you are stuffed. [this is a weakness in the standard MS implementation IMHO]
HTH
Dick
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply