January 23, 2015 at 8:45 am
Maybe it is just your efforts to anonymize the name, but you are missing a backslash in the file name? 'E:xxxxxxxx.trn'
Outside of that try running a profiler trace on the secondary to see the exact sql server calls that are done by log shipping?
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
February 10, 2015 at 2:15 am
Sanjay,
It could be your reporting/SSMS component has an open connection to the database therefore when restoring the log file it is unable to obtain an exclusive connection to the database due to the open connections. There would be an option when setting up log shipping to disconnect any connections to allow it to restore the log backup.
When setting up a log shipping secondary as a read-only standby, there is an option to disconnect any existing connections before attempting log shipping restores. This option is available whether you use the Management Studio GUI or T-SQL commands.
Else you can try in 'NoRecovery' mode where user connections and read only mode is prohibited, test it and let me know the output.
Regards,
Viewing 2 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply