July 24, 2008 at 7:57 am
Hello Guys,
I implemented logshipping from Primary server A to secondary server B. Now database on server B which is being logshipped is in standby/ read only mode. We would want to replicate this database and I am not sure if we can do it. Can any of you help me with this.
ANy help would be great.
Cheers
Nick
July 24, 2008 at 8:04 am
I don't think you can do that with replication.
But could you explain why you want such a setup? If you need just a second stand-by server you can configure logshipping with more than one target server.
[font="Verdana"]Markus Bohse[/font]
July 24, 2008 at 8:17 am
Thanks for the reply, let me tell you scenario.
We need to replicate and also have a standby server at the same time. We were planning on doing it this way. First we would do log shipping from primary to secondary which would be our standby server. THen we would want to replicate from secondary and not primary so that primary would not be the one which would handle both logshipping and replication. Did you get that? So would you want to propose anything else for our scenario.
I have another question ?
Lets say
Primary server A Mirror Server A to Server B
ALso there is witness server so that automatic failover can take place.
I know that we need to use Server A for replication. This is the same scenario mentioned above but with Mirroring instead of logshipping. So now in this case Server A would be mirroring to server B and also replicating at the same time. SO, lets say server A fails, it would automatically failover to server B. What would happen to replication? is there a way using which even replication would be failed over or something like that.
Any help would be appreciated
Cheers
Nick
July 24, 2008 at 1:27 pm
Not possible with that secondary server since it's in a standby mode. Log shipping is a backup and restore operation.
Why not just replicate from your primary server, set up a pull subscription if you are worried abt overloading ur primary sever.
July 25, 2008 at 12:51 am
I agree with Denby.
You're scenario is not possible, neither with logshipping nor with mirroring. The logshipped database would be in standby mode and can't be replicated. When using DB mirroring, the mirror database is in Recovering mode and can't be replicated either.
I still don't undwerstand what you want to do on the replicated database. Do you want it for reporting or just as an extra copy for availability/disaster recovery.
Maybe a third-party solution like Double Take[/url] can help you further.
[font="Verdana"]Markus Bohse[/font]
July 25, 2008 at 1:02 am
July 25, 2008 at 3:39 am
MarkusB (7/25/2008)
You're scenario is not possible, neither with logshipping nor with mirroring.
Actually, you can with mirroring:
http://msdn.microsoft.com/en-us/library/ms151799.aspx
The link describes (in a not terribly straight forward way) how you can mirror a database and replicate it to a third. When the mirroring fails over, the mirror server becomes active and takes over the replication, keeping the third server up to date. It's quite good 🙂
July 25, 2008 at 5:30 am
Dogers,
the article you mentioned describes how to replicate a databases which is also mirrored. But the principal database is published.
From what I understand from the original poster he doesn't want to use replication on the active (principal) node but on the stand-by\mirror node. And that's not possible.
[font="Verdana"]Markus Bohse[/font]
July 25, 2008 at 6:52 am
Thans a tonn guys forr all the responses. THey really helped me. From your discussion I can understand that I cant have mirroring and replication or log shipping and replication on the same server but with the article which I found very intersting, I feel that I can do a failover replication from mirroring or logshipping. I am wanting to do it as a DR site.
THank s a lott again...
Nick
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply