I have read about the implementation of log shipping and restoring procedure in the hot standby database, but I still have no clear idea on how sql server can maintain the two tasks (log shipping and regular log backup) separetely. My current production server does a FULL backup of all databases (around 20) every 2 days, and transaction log backups every 4 hours. These backups are stored in the same backup destination per database (20 backup files). INIT command is used when creating the FULL backup, NOINIT for subsequent LOG backups. LOG backups truncate the LOG after every backup. Now here comes my confusion. How does SQL server will now where to start the LOG backup previous to ship it to the hot standby database if there was already a regular LOG backup which have truncated the log previously? So in sequence FULL BACKUP INTO DEVICE1 LOG BACKUP FOR LOG SHIPPING INTO DEVICE2 LOG BACKUP FOR LOG SHIPPING INTO DEVICE2 LOG BACKUP FOR LOG SHIPPING INTO DEVICE2 LOG BACKUP FOR REGULAR BACKUP INTO DEVICE1 WITH TRUNCATE (IMPLICIT) LOG BACKUP FOR LOG SHIPPING INTO DEVICE2 (*) LOG BACKUP FOR LOG SHIPPING INTO DEVICE2 LOG BACKUP FOR LOG SHIPPING INTO DEVICE2 LOG BACKUP FOR REGULAR BACKUP INTO DEVICE1 WITH TRUNCATE (IMPLICIT) ... and so on (*) So where does the LOG backup for shipping start if there was a previous TRUNCATE. If I specify NO_TRUNCATE on the regular LOG backups, my logs will will grow forever right? But if that is the case, how does SQL Server maintain the correct SCNs for the regular LOG Backup and the LOG BACKUP for shipping? Thanks in advance for your answers.