Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Log Shipping Looking for Backups in wrong location Expand / Collapse
Author
Message
Posted Monday, February 25, 2013 12:48 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, April 17, 2014 2:25 PM
Points: 222, Visits: 569
I 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:

Error: Cannot open backup device 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\ C:\SQLLogs_LS\dbname.trn'

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?
Post #1423750
Posted Monday, February 25, 2013 2:57 PM
SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Thursday, April 17, 2014 2:25 PM
Points: 222, Visits: 569
Well, 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.
Post #1423783
Posted Tuesday, March 05, 2013 12:24 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Wednesday, September 25, 2013 6:23 AM
Points: 392, Visits: 405
Just 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 ..


===========================================
Better try and fail than not to try at all...

Database Best Practices

SQL Server Best Practices
Post #1426985
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse