After setting up Log Shipping plan successfully in LiteSpeed 5.0, the following messages may appear in the History page of the LiteSpeed console:
"First transaction log backup file to restore was not found"
All the log shipping jobs appear to have run successfully despite the above error message.
The subscriber instance performing the first restoration could not find any transaction log (T-log) backup files from the subscriber's copy directory for the initial execution of the T-log restore job, due to delay the first copy jobs.
WORKAROUND 1:
This particular message is OK for the first few job executions. Usually, this happens if:
1. The backup / copy / restore jobs are executed simultaneously and scheduled with the same interval (e.g. 15 minutes). The message will disappear after the succeeding restore job executions.
2. You have changed the "Database load delay (min)" from the default value of '0' to a higher value. This will cause the subscriber to delay the first copy jobs so it can fall behind the publisher based on the specified delay time. The message will disappear after the first T-log has been restored.
WORKAROUND 2:
If workaround 1 above does not apply, check if the T-log backup files (*.TRN) are indeed being copied over to the subscriber's copy directory. The copy job status may report successful but the files may be missing from the directory.
