July 18, 2011 at 7:58 am
Hi all,
I've set up transactional replication with a remote distributor. I have mirrored the publisher database so that if it goes down, replication continues without me having to set up replication again.
This was done by setting the -PublisherFailoverPartner parameter in the log reader agent.
I did the following failovers and these are the outcomes:
1. Manual failover from Principal publisher to Mirror - replication continued to work.
2. Manual failover from Mirror publisher to original Principal publisher - replication continued to work.
Finally to mimic what is most likely to happen in a Disaster recovery situation:
3. Shutdown principal publisher and ran ALTER database databasename set partner FORCE_SERVICE_ALLOW_DATA_LOSS’ to make the mirror the principal. Replication did not continue to work.
Is it even possible to make scenario 3 work? This is what is most likely to happen in real life, in that your production server goes down and you need to failover to the mirror and make replication continue.
July 18, 2011 at 9:58 am
Any ideas people?
Is there anyone out there who has used database mirroring with replication?
Thanks.
July 19, 2011 at 11:41 pm
Replication didn't work,
Can you give more detail on what didn't work.
I have used mirroring and replication and there is a few things to look out for.
When the mirror is broken you replication won't work anymore this is because the -publiserfailoverpartner paramter is not longer valid as it's not participating in replication.
I also suspect that during disater you log will get broken on way or the other. If the log of the database breaks so will replication , even if it was up to date at point of failure. However you might be able to resume it.
What was the error you got from replication.
Cheers
Jannie
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply