InstantForum.NET v2.9.0SQLServerCentralhttp://www.sqlservercentral.com/Forums/notifications@sqlservercentral.comFri, 24 May 2013 14:01:04 GMT20http://www.sqlservercentral.com/Forums/Topic1423750-1549-1.aspxJust to add one point -->You were seeing path as "C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\ C:\SQLLogs_LS\dbname.trn" .....The path C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\ would have been the default backup path for your instance... We did faced this issue last week and that is what I learned what a blank space can lead too.... Just thought to share ..:-)Tue, 05 Mar 2013 12:24:48 GMTBuntyBoyhttp://www.sqlservercentral.com/Forums/Topic1423750-1549-1.aspxWell, I figured it out - the path for the backup files, C:\SQLLogs_LS\, was actually ' C:\SQLLogs_LS\' with a leading space. I altered the job, and all is well. Need to be more watchful cutting and pasting from my DB documentation.Mon, 25 Feb 2013 14:57:17 GMTtim_harkinhttp://www.sqlservercentral.com/Forums/Topic1423750-1549-1.aspxI have log shipping set up (initial set up) and the backup and copy jobs are working fine. The restores, however, are failing. The SQL Agent logs show the following for each t-log restore attempted:[font="Courier New"]Error: Cannot open backup device 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\ C:\SQLLogs_LS\dbname.trn'[/font]In the LS configuration, I set the path C:\SQLLogs_LS\, and when I run sp_help_log_shipping_secondary_database it does show that as the backup_destination_directory. Any ideas why it is adding the default backup directory in front?Mon, 25 Feb 2013 12:48:40 GMTtim_harkin