Hi all, We have a pretty basic, home-grown log shipping setup. Until now, if for some reason the secondary server is unable to apply the latest log backups (usually because it can't get exclusive access to the target DB) it fails and that database has to be fully re-synced from the primary. I am testing a modified system which uses tables in the msdb databases on both servers which have a list of the databases in the log shipping and flag against each one which is set to 1 if the last lot of logs were applied successfully or 0 if they were not. If the primary sees a 0 on either it's own or the secondary's table for a given DB, it appends the transactions onto the current set (specifying WITH NOINIT). It will keep doing this until it sees a 1 on both the status tables for that database, indicating the last lot of logs were applied OK. When it does it backs up the logs using WITH INIT, which overwrites the current set. The issue is that if the secondary has to apply more than one set of logs (written using WITH NOINIT), then once that has succeeded the next time it tries to apply a single set (written using WITH INIT) it fails with the message "The log in this backup set begins at LSN xxxxxx, which is too late to apply to the database. An earlier log backup that includes LSN 1247592000000017600001 can be restored. [SQLSTATE 42000] (Error 4305)". Anyone got any ideas? Should I be using WITH FORMAT instead of WITH INIT for normal (i.e. when it's not appending logs) backups?