sql logshipping error

xdai

we just set up the log shipping,

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.

please help

xdai

the restore finished around 12:25pm, then the first t-log backup at 12:30, it is successfully copied to network share every 15 mins (which is i specified on the remote server), but the load job couldn't successful (i set up every 5 mins).

xdai

we are using sql 5.4.

the backup on the source server took place at 10:57, finished at 11:24, the restore on the dest server finished at 12:25. the first transaction log backup occured at 12:30.

xdai

the source database already have a backup t-log job running every 15 mins initiated by sql server agent, so if i set up another backup jobs by sql backup tool, will it cause problem? thanks

petey

the source database already have a backup t-log job running every 15 mins initiated by sql server agent, so if i set up another backup jobs by sql backup tool, will it cause problem? thanks

Yes, that will cause problems. You currently have a continuous chain of transaction log backups, some created by SQL Server and others by SQL Backup. When you restore them, you will need to restore them sequentially. Unfortunately, this will require you to use SQL Server for some of the files, and SQL Backup for the rest of the files. This is obviously troublesome, and makes log shipping using SQL Backup impossible.

If you want to use SQL Backup for log shipping, you need to use only SQL Backup to perform the transaction log backups.