Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 General SQL Server Forums
 New to SQL Server Administration
 Logshipping

Author  Topic 

laddu
Constraint Violating Yak Guru

332 Posts

Posted - 2009-11-18 : 11:06:49
Logshipping issue
I have configured logshipping between our production server and DR server (servers are in workgroup –not in domain)
I created a window user account syncaccount (in both servers with same username and pw)and added in admin group. SQL server services restarted with syncaccount . Created a shared folder in both servers and syncaccount has full permissions on shared folder.
Now configured logshipping , in secondary server restore job got below details, it seems tlogs are not copying to secondary server shared folder, please let me know next steps

Message
2009-11-18 11:00:00.92 Retrieving restore settings. Secondary ID: '0e16a55f-0ef7-427a-85d5-e505f72bef10'
2009-11-18 11:00:00.92 Retrieved common restore settings. Primary Server: 'SourceServer', Primary Database: 'DBname', Backup Destination Directory: 'E:\TranLogs', File Retention Period: 4320 minute(s)
2009-11-18 11:00:00.93 Retrieved database restore settings. Secondary Database: 'DBname', Restore Delay: 0, Restore All: True, Restore Mode: Standby, Disconnect Users: True, Last Restored File: <None>, Block Size: Not Specified, Buffer Count: Not Specified, Max Transfer Size: Not Specified
2009-11-18 11:00:00.96 Searching through log backup files for first log backup to restore. Secondary DB: 'DBname'
2009-11-18 11:00:00.96 Could not find a log backup file that could be applied to secondary database 'DBname'.
2009-11-18 11:00:00.96 The restore operation was successful. Secondary Database: 'DBname', Number of log backup files restored: 0
2009-11-18 11:00:00.96 Deleting old log backup files. Primary Databa

laddu
Constraint Violating Yak Guru

332 Posts

Posted - 2009-11-19 : 23:43:38
resolved, issue was log chain broke up. Manually forced the restore job to restore old tlogs first.
Go to Top of Page
   

- Advertisement -