@perry, how do you get to the secondary database retention settings on the secondary server?

Also, we ran into a situation over the weekend where something is conflicting the restore jobs on the secondary... we appear to have had a conflicting job that was processing the data from the database that was being log shipped to. Assuming that a situation like that is cleared, will the job that executes the restore just be smart enough to pick up where it left off?