Ok, that is almost certainly why your log-shipping isn't working. Your first task (if you really want to set up log-shipping) is to get him to stop that completely. If you don't do that this won't work.
- Next (and this is just what I would do), go back to your log-shipping job on the Primary server, and reconfigure it from scratch. Just dump everything and start again. (It's not working anyway, so who cares, right?) This time configure all of the jobs (that's LSBackup, LSCopy and LSRestore) to run more frequently than once a day. How frequently depends on your environment and how much data is changed etc. Plucking a number out of the air, let's say every 15 minutes. Set your jobs to run every 15 minutes.
- When you've done that, run each job manually once and observe what happens. So on the primary, run LSBackup, go to Job History and check that is has completed properly.
- Then go to the secondary and run LSCopy. Wait for it to complete successfully. Go into your log-shipping folder and check that the log backup file is physically there.
- If all is good so far, run your LSRestore job manually once too. Check the Job History and see that your 1 log file has been restored successfully. Monitor the whole process for the first few hours (not continuously- just check it now and then).
All of the above will only work if you are taking no other log backups. If your DBA takes extra log backups separately this won't work. S/He won't even need to take any anyway because you are taking them every 15 minutes.
Does that make sense?