Log Shipping Error - Failing to save Secondary Server Configurations Err # 14262

I set up Log Shipping with just 2 servers primary and secondary. When I run from the Wizard for the very first time keeps failing at the stage of saving Secondary Server Configuration info. When i instead run the generated script this problem disappears but then restoring of transactions fails - the process can backup transactions from the Primary server , copy them accross to the secondary and fails on the restore. Any ideas why.

Hi Jonathan

When you use the SSMS UI to configure log shipping and it fails, can you give me the error message that should be available in the error dialog?

When you use the generated script to configure log shipping, but the restore fails, have you had a look at the log_shipping_monitor_error_detail tables on both the primary and seconary servers? These tables are in msdb (see BOL for more information) and should provide detailed error information.

Thanks, Mark

|||

Also its good to check whether both the instances have the same MDAC level & service pack, as this will happen if there is such mismatch.

http://www.sql-server-performance.com/sql_server_log_shipping.asp fyi.

|||

Hi Satya

Greetings to you. I managed to resolve the problem of failing to save Secondary Server configuration. I reinstalled SQL Server and the problem disappeared. My next challenge is I want to automate my backup strategy where I have Log Shipping between 6am to 8pm backing up transactions at 20 minute interval. Then Log Shipping between 8pm to 10pm at 1 hour interval then Full database backup daily , once a week , once a month etc. in which case I need to disable Log Shipping .

|||

Hi there Mark!

Thanks for your interest in my problem. I managed to go over the problem. I reinstalled SQL Server and the problem disappeared. However I have a new challenge. I need to automatically setup Log Shipping between 6am to 8pm backing up transactions at 20 minute intervals then Log shipping between 8pm to 10pm at 1hr intervals then automatically disable Log shipping and do Full Database backup at night like midnight per day ,week etc

|||

Hi Jonathan

Glad the problem disappeared.

Do you really need to have two different interval periods for the backups? It is obviously simpler if you only have the one configuration. If you do need the two schedules, then you should be able add a schedule to the backup job that is created. Using the log shipping UI, go to the "Transaction Log Backup Settings" dialog then the "Edit Job" button to pull up the job properties.

Regarding the full backup you do not need to disable log shipping for you to be able to do a full backup. See the topic in BOL titled "Creating Transaction Log Backups" for a description of the log sequence and how transaction log backups are independent of the full backup.