Troubleshoot SQL Server 2000 log Shipping Features

server| Solution I. Residual data

when you experiment with SQL Server 2000 log shipping, you may break the setup process occasionally. If so, some of the data will still be stored in the Log shipping table for each server and affect subsequent log shipping setup actions. To ensure that the remaining data is cleared, do delete the data from the Log shipping table in the msdb database for each server.

Error message:

Error 14261: The specified primary_server_name.primary_database_name (' N ') already exists.
Error 14426: A Log Shipping monitor is already defined (...)

Processing method:

You must manually perform the following stored procedures to delete the information that log shipping records in the database.
1,sp_delete_log_shipping_primary
Remove primary server information from the Msdb.dbo.log_shipping_primary table
2,Sp_delete_log_shipping_plan
Delete Log shipping plan
3,sp_delete_log_shipping_secondary
Remove secondary server information from the Msdb.dbo.log_shipping_secondaries table
4,sp_remove_log_shipping_monitor
Delete log shipping monitor from table Msdb.dbo.log_shipping_monitor

II. model of the database

If log Shipping is set correctly, but there is no way to perform correctly, you can see this information and interface in SQL Server logs:

Microsoft (R) SQLMaint Utility (Unicode), Version logged on to SQL Server ' ZTAO-1 ' as ' ztao-1\administrator ' (trusted)
Starting maintenance ' Log_plan_9 ' on 2003-9-4 14:42:02
Backup can is performed on database ' erplogshipping '. This sub task is ignored.
Deleting old text reports ... 0 file (s) deleted.
End of maintenance the ' log_plan_9 ' on 2003-9-4 14:42:02
SQLMAINT. EXE Process Exit code:1 (Failed)

It may be that you did not set the database correctly, complete mode.

Three, log file storage path

Read an article on MSDN saying, do not use the same directory to store log files when you set up log shipping again on the same computer. This has not been verified, only mention, remind everyone!