Replication does detect Mirrored Source Fail Over

I'm trying setup a proof of concept for a client but I’m having issues with mirroring and replication.

With the help of http://technet.microsoft.com/en-us/library/ms151799.aspx I’ve done the following..

The setup is as follows, I have several instances of SQL Server

A+B are mirrored with each other, with A being the principle and B the mirror

C is the distributor

E is subscribes to A, with parameters for PublicationFailoverPartner set to B

The mirroring between A+B works fine, I can manually fail each and the databases keep in step.

Without testing the mirroring failover, the replication between A+C+E also works.

However when I test the mirror to failover between A+B no transactions are replicated though to E. The publication moves from A to B in the Server Management Studio.

The logs state that the log reader agent can not gain access to A, however nothing is recorded regarding any attempts to contact B. In the replication monitor the error message

"The concurrent snapshot for publication ABCXYZ is not available because it has not been fully generated of the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Spapshot Agent for the publica..." (cut off).

"the process could not execute 'sp_replcmds' on 'A'

I have checked that the SQL Server Agents are running on all agents,

I have checked that that server B is set at the PublisherFailoverPartner on server C agent configuration, I'm now at a lost as to what is wrong,

Any help or suggestions are greatly appreciated.

Pls do not duplicate

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1958649&SiteID=1

|||

Sorry about this Deepak, I had duplicated this as I though I had lost my original post, it was just in anothor forum,

appologies for being a Topic Hog

Replication Comparison Chart for SQL2005

Anyone know of a chart on the Microsoft Site that compares all the
Replication types for SQL 2005?
Trans Shipping, Mirroring, Publication and Subscription and all that
stuff?
Here is a pretty good one on the Dell site.
www.dell.com/downloads/global/power/ps1q06-20050325-Sankaran.pdf
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"jughead" <mike.aarset@.gmail.com> wrote in message
news:1174056604.344365.92450@.o5g2000hsb.googlegrou ps.com...
> Anyone know of a chart on the Microsoft Site that compares all the
> Replication types for SQL 2005?
> Trans Shipping, Mirroring, Publication and Subscription and all that
> stuff?
>

Replication and Mirroring

I am setting up transactional replication on a database A with read only subscriber database B (for reporting purpose). I have also setup mirror on database A. I tried to manually failover to mirror...mirroring works fine but transactional replication is interrupted.

I have followed the steps as in article

http://msdn2.microsoft.com/en-us/library/ms151799.aspx

I have also used PublisherFailoverPartner parameter...but replication still complains that it cannot connect to publishing database.

Any ideas or direction is greatly appreciated.

I would trouble shoot the following way:

1) try to connect to the old mirror (which is the new principal after the failover) database from the distributor (for example using osql.exe) and see if connection can be made. This will eliminate the obvious connection issue.

2) check to see if the server that hosted the mirrored database was configured as publisher using the same distributor

Replication - Mirroring - Clustering?

Hi,
I'm not the network guy, just asking the question for him.
Here's the scenario:
We manage our own server and have a SQL 2000 database.
All database transactions are done through our website.
What the boss wants:
If one of the servers goes down, database server or the IIS server,
everything should be switched over to another server.
The data must be up-to-date at all times in the backup server.
I just need a suggestion as to the best method to implement this.
Any websites where I can get the information?For Web Servers, use NLB. Its Network Load Balancer and for database, use
MSCS Clustering.
"Raymond D'Anjou" wrote:

> Hi,
> I'm not the network guy, just asking the question for him.
> Here's the scenario:
> We manage our own server and have a SQL 2000 database.
> All database transactions are done through our website.
> What the boss wants:
> If one of the servers goes down, database server or the IIS server,
> everything should be switched over to another server.
> The data must be up-to-date at all times in the backup server.
> I just need a suggestion as to the best method to implement this.
> Any websites where I can get the information?
>
>

replication

Hi,

I posted this in the repl section, but perhaps I should post it here as well. Say for example, with mirroring set to high-safety mode, if the mirror box goes down, replication stops flowing until the server comes back online? Or should replication continue to flow down to the subscribers since the primary server is still online, but the mirror is not.

Thanks

J

What you mean to say when mirror box goes down?

If the mirror server is unreachable or not available to connect on network then yes Replication will also be affected.