sql logshipping error
the database has been restored successfully on destination server, though we use compression rate 2 to compress the transaction log backup, looks like it is much more bigger than the backup file backup by sql server it self, at the same time stamp. why is that?
also, on the destination server, there is error when server start load the log file.
6/22/2009 1:25:00 PM: Warning 170: Log files are not in sequence: 'LOG_son_db_20090622123000.sqb' and 'LOG_son_db_20090622124501.sqb'
6/22/2009 1:25:00 PM: Warning 170: Log files are not in sequence: '' and 'LOG_son_db_20090622130001.sqb'
6/22/2009 1:25:00 PM: Warning 170: Log files are not in sequence: '' and 'LOG_son_db_20090622131501.sqb'
6/22/2009 1:25:00 PM: Restoring son_db (transaction logs) from:
6/22/2009 1:25:00 PM: \\fjelitedb2\son_db\LOG_son_db_20090622123000.sqb
SQL error 3013: SQL error 3013: RESTORE LOG is terminating abnormally.
SQL error 4305: SQL error 4305: The log in this backup set begins at LSN 829672000002600800001, which is too late to apply to the database. An earlier log backup that includes LSN 829662000001074300001 can be restored.