SQL Server 2000 log Transfer function may occur
First, the residual data When you perform the experiments transmitted by SQL Server 2000 log, the setup process will be interrupted. If this is this, some information will still store the log transfer data sheet for each server and affect the subsequent log transfer settings. In order to ensure that these remaining materials are cleared, do delete information about log transfer data tables in each server MSDB database.
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: The following stored procedures must be manually executed to delete information logs recorded in the database. 1, sp_delete_log_shipping_primary delete msdb.dbo.log_shipping_primary table Primary Server information 2, sp_delete_log_shipping_plan Delete Log Shipping Plan 3, sp_delete_log_shipping_secondary delete Secondary Server information msdb.dbo.log_shipping_secondaries table 4, sp_remove_log_shipping_monitor Delete Log Shipping monitors from the table msdb.dbo. LOG_SHIPPING_MONITOR
Second, the database mode If log shipping is properly set, there is no way to perform it normally, you can see this information and interface in the log of SQL Server:
Microsoft (R) SQLMAINT UTILITY (Unicode), Version Logged On To SQL Server 'ZTAO-1' As 'Ztao-1 / Administrator' (Trusted) Starting Maintenance Plan 'Log_PLAN_9' On 2003-9-4 14: 42: 02Backup CAN NOT be Performed 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: 02sqlmaint.exe process.exe process EXIT CODE: 1 (failed)
Maybe you don't have the pattern of the database correctly, full mode.
Third, log file storage path
I have seen an article on MSDN that when setting up log shipping again on the same computer, do not use the same directory to store the log file. This has not been certified, just mention it, remind everyone!
