Transactional Replication with Transaction Log Backups

[PHead2]

I currently run a transaction log backup which truncates the logs every two hours, does a full backup twice a week and differential backups on the other nights. I want to setup a backup SQL server as well and use transactional replication to keep it current.

I was wondering if there is any conflict that can arise if I try to use transactional replication along with transaction log backups that truncate the log - will I lose transaction on the subscriber if the log is truncated before it is shipped?

Thanks.

 

[ClaireHCM]

After setting up replication,you can see there is a job listed in JOBS folder specially for this replication.As a job,you can schedule the execution time.(Right click on the job--select properties --- Go to schedle tab,you can edit the execution time as you like)

same thing for backup plan,you will set up the schedule time for taking backup.
What you can do is schedule the job for replication before the time of taking backup (as you said every 2 hrs)
You can avoid the conflict that replicate nothing due to the tran log is empty!

 

[ecobb]

If I'm not mistaken, since you have the logs set up to backup/truncate AND replicate, SQL Server will automatically know not to truncate a log until all transactions in it have been replicated.

I have Transactional Replication set up on several databases which are truncating logs every 30 minutes and I've never run into problem.

Hope this Helps.

 

[SQLBaby]

is it not better if you backup once in 24 hours (mid night, early in the morning or what time is suitable for you. when hust few users or none loged on) and then after every 30 minutes or 1-hour make transactional backup.

i had lot of problems before but since when i scedualed the jobs i never have problems. and every thing is going well.

So create jobs and scheduale these jobs as you want.

Knowledge is a key of success.