question

jonesg avatar image
jonesg asked

Any suggestions on why the replication job fails when backups are running.

I am replicating data between 11 remote sites and a central site. At one site the replication distribution subsystem gives the message "The process could not connect to Subscriber". The other 10 sites run fine during backups. Any suggestions of where to look to solve the problem would be very much appreciated.
replicationbackup
1 comment
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Is this during backups at the remote site or central site? Are the backups going over the network? How are you performing the backups?
0 Likes 0 ·
ruancra avatar image
ruancra answered
The backups might be causing locks on the database which will prevent replication from processing. Check the logreader and distribution history tables for errors: use distribution select top 10 * From MSlogreader_history --where agent_id= 14 order by time DESC select * From MSdistribution_history --where agent_id= 8 order by time desc
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

jonesg avatar image
jonesg answered
For KenJ: The backups are being done on the remote site and outputs to a local hard drive. The Backup is being done using the SQL Backup command.
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

jonesg avatar image
jonesg answered
For ruancra: Checked the history files and found no errors. Could not find any evidence of locks or blocks.
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.