I. Residual data
When you perform an SQL Server 2000 log transfer experiment, the setting process may be interrupted occasionally. If so, some data will still be stored in the log transfer data table of each server, and the subsequent log transfer settings will be affected. To ensure that all the remaining data is cleared, delete the data related to the log transfer table in the msdb database of 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 (...)
Solution:
You must manually execute the following stored procedures to delete the information recorded by Log Shipping in the database.
1. sp_delete_log_shipping_primary
Delete information about the Primary Server in the msdb. dbo. log_shipping_primary table
2. sp_delete_log_shipping_plan
Delete Log Shipping plan
3. sp_delete_log_shipping_secondary
Delete the Secondary Server information in the msdb. dbo. log_shipping_secondaries table
4. sp_remove_log_shipping_monitor
Delete Log Shipping monitoring from the msdb. dbo. log_shipping_monitor table
II. Database mode
If Log Shipping is set correctly, but there is no way to execute it normally, you can see this information and interface in the SQL Server Log:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged on to SQL Server 'ztao-1' as 'ztao-1Administrator '(trusted)
Starting maintenance plan 'log _ Plan_9 'on 2003-9-4 14:42:02
Backup can not be performed Med on database 'erplogshipping'. This sub task is ignored.
Deleting old text reports... 0 file (s) deleted.
End of maintenance plan 'log _ Plan_9 'on 2003-9-4 14:42:02
SQLMAINT. EXE Process Exit Code: 1 (Failed)
It may be that you have not set the database mode correctly. The full mode is used.
III. Log file storage path
I have read an article on MSDN saying that when setting Log Shipping again on the same computer, do not use the same directory to store Log files. I have not verified this. I just want to mention it and remind you!
