We have replication running from Server1, which has a database published and p2p enabled. We backup this database after the replication is created, and restore it on the Target. We then create a push subscription on Server1 to the target DB on Server2. There are no publications on Server2. After we restore the db and create the subscription on Server2, we do a transaction log backup on Server2 and everything works fine.
After about a day we start seeing this message when backing up transaction logs on Server2:
The log was not truncated because records at the beginning of the log are pending replication or Change Data Capture. Ensure the Log Reader Agent or capture job is running or use sp_repldone to mark transactions as distributed or captured.
There is no log reader running on this side. When I try to use sp_repldone it tells me the database is not published. I don't understand how transactions are getting marked for replication on Server2 when there is only a subscription?
Because of this error, the .ldf file continues to grow and eventually we have a problem.
This happens on two different setups we have. The first sql server 2008 SP3 to sql server 2008 Sp3 and the second is SQL Server 2008 R2 to SQL Server 2008 R2. This weekend we just re-initilaized replication on both of these setups. After it was done, we did a tranlog backup on the Server2 -- no message about cannot truncate log.
Now this morning it is there again for both of them.
John Tracy
John