1
I'm having issues setting up log shipping on a remote server. We have a very large production database that needs to be migrated offsite. The db is 9 GB backed up. It takes about 4 hours to copy the file to the remote server when it is archived. During the log shipping process the file takes a lot more time than that to arrive at the remote server. I decided to use log shipping for this migration, because we can't have our production box down for the 4 to 8 hours it would take to migrate the database, migrate replication, etc.
After several attempts using the Wizard in SQL 2000, my latest hump is an inability to restore the log files.
Server: Msg 4305, Level 16, State 1, Line 1
The log in this backup set begins at LSN 114798000000031800001, which is too late to apply to the database. An earlier log backup that includes LSN 114762000000056700001 can be restored.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE LOG is terminating abnormally.
The db file that initialized on the remote server was last modified 3/28/2007 10:56 AM and the first log file available for restore on the remote server is 3/29/2007 4:11 AM.
Is there a workaround for this? I'm trying a newer full backup of the db and looking at doing a point in time restore. Thoughts, suggestions?
