I am having to setup log shipping for a few instances to a remote datacenter. I know that log shipping essentially makes transaction log backups, copies those to the remote server and then restores those based on the load delay interval. Are these logs made with copy_only or actual transaction log backups? If actual, then I should make sure the primary folder for the logs are backed up to my data domain server just like my full and differential backups?
@scotty, sounds like you have a decent understanding of log shipping but that your primary question is how to get your tlog backups to your data domain backup solution. Since the transaction log backups that log shipping makes is your transaction log backups that you would be needing to store in your backup solution for historical purposes, you could simply create an additional SQL job to copy the tlogs to your data domain share, or leverage the data domain share as your local for the primary or secondary log. I am not sure how your DD solution is configured. In my shop we use a CIFS share which complicates things for SQL so I have to use a secondary job to copy my tlogs.
This should have all the detail that you need.
http://msdn.microsoft.com/en-us/library/ms187103.aspx There is no need to use the copy_only option in the backup command, in Log Shipping the copy process is literally an OS file copy step that gets the log file from the primary backup location to the location elected as the place from which the restore should take place.  - I missed out the info re log backup location. Personally I place my log backups in the same place as all other backups for the sake of consistency. "Where are the backups? In the backup folder."