This is an example of the s[p for the trans logs:

CREATE PROCEDURE dbo.up_C_NICC_BackupSynapseProdLogs AS

DECLARE @PathName varchar(59)
DECLARE @DateStamp varchar(11)
DECLARE @TimeStamp varchar(4)
DECLARE @FullPathName varchar(100)

SET @PathName = ('\\PRG-240-690\SynapseBackups\TransNIRHBProd\TransNIRHBProd-')
SET @DateStamp = GetDate()
SET @TimeStamp = CAST(DATEPART(HOUR , CURRENT_TIMESTAMP) AS varchar) + CAST(DATEPART(MINUTE , CURRENT_TIMESTAMP) AS varchar)
SET @FullPathName = @PathName + @DateStamp + '-' + @TimeStamp + '.bak'

BACKUP LOG NIRHBProd TO DISK = @FullPathName

SET @PathName = ('\\PRG-240-690\SynapseBackups\TransReportNIRHBProd\TransReportNIRHBProd-')
SET @DateStamp = GetDate()
SET @TimeStamp = CAST(DATEPART(HOUR , CURRENT_TIMESTAMP) AS varchar) + CAST(DATEPART(MINUTE , CURRENT_TIMESTAMP) AS varchar)
SET @FullPathName = @PathName + @DateStamp + '-' + @TimeStamp + '.bak'

BACKUP LOG ReportNIRHBProd TO DISK = @FullPathName
GO

This works fine but again the backup is made over the wire and I am trying to avoid it. As for moving the hourly backups to tape using the backup software would just be a pain. I'd rather manage the whole thing right from the SQL server itself. I know this would be possible if I could use a second step in the job itself to capture the name of the file created in the first step and then use a command step to do a copy of the file to a remote location.