• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 698
  • Last Modified:

Adding a Second Log Shipping Secondary Instance

Hi All,

I already log ship my main databases to another local server and now I need to also log ship to another physical DR location via a slower WAN connection.

My plan was to bring over the full backup of these databases ( which are quite large) and restore with standby in preparation to start log shipping to the DR site.

My question is this: how do I handle the incremental transaction log changes?  Normally when doing this for the first secondary instance I restore a full backup and then a current trans log backup before starting log shipping, I imagine doing that for a second instance will create an LSN problem for the existing log shipping instance?  Do I do a differential instead?

Thanks for the help.
0
Primedius
Asked:
Primedius
  • 4
  • 3
1 Solution
 
lcohanDatabase AnalystCommented:
I would think to use the Secondary log shipped database as source and set that one to Log ship to " another physical DR location via a slower WAN connection."
Not sure what the purpose is for the secondary database in your existing Log Shipping but I think by creating a chain rather than log ship from one single source would alleviate the problems may be caused on the primary source database.
0
 
PrimediusAuthor Commented:
Hmm, never thought of that. Is that something which is commonly done?  You can log ship from a database which is in standby as these will be?
0
 
lcohanDatabase AnalystCommented:
I'll test right now the copy only backup on 2008 R2 Standby database.
Please see more details about different ways to "log ship" as highlighted in the picture/notes at the end of the article - I know is slightly different chain with Transactional Replication first but that one is just another Log Shipping method.

http://sqlmag.com/database-high-availability/3-log-shipping-techniques

Other options would be to use Transactional Replication with Pull Subscribers so the slow one will not affect the Publisher and the fast Subscriber which is not the StandBy Log Shipoped database(s).

Also check out the last solution just before last posting in this article and see if that helps.


http://www.sql-server-performance.com/forum/threads/backing-up-a-log-shipping-destination-database.17746/
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
lcohanDatabase AnalystCommented:
Actually I just set it all up in my 2008 R2 chained exactly as mentioned SQLDEV1 my OLTP database as Primary to Secondary in SQLDEV2 as standby and that one I used as Primary to log ship to SQLDEV3 Secondary in stand by mode as well.

I just wasn't 100% if what I did a while ago is still valid but yes, it is all good so far and working well to setup your stand by database as Primary to another T-log Shipping Secondary. I know I did this a while ago to offload the prod OLTP that was log shipped to a warm standby before clustering and from that to the reporting server which was in different data center from different location and with slower network connection.
0
 
PrimediusAuthor Commented:
Wow, thanks for the validation.  Will try this afternoon.
0
 
PrimediusAuthor Commented:
A little confused. On the secondary do I do a full backup and then a trans backup to restore on the third server to get the database in place to start log shipping.
0
 
PrimediusAuthor Commented:
No provision for backing up.  Hmm take offline and move files?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now