I did not know of this aritcle -- but when log shipping broke Saturday because of a third party log backup I decided I had nothing to lose if it did not work. I took a differential of the primary and applied it to the secondary with Standby= 'filename' and was very pleasently surprised (happy dance in the kitchen ). Then I kicked off the backup, copy and restore jobs and the alert stopped notification. I am very thankful for the people who programmed the restore and backup processes for SQL server and have made it very robust.

Thanks for the article. I was thinking through the "what would happen if a Full had occurred" and this answered that question.