Anmelden
 
HomeLibraryDownloadsSupportWebcasts & EventsCommunityForenBlogs
Ressourcen für IT-Professionals >
> 
> 
Logshipping error

Unanswered Logshipping error

  • Dienstag, 26. Februar 2013 17:50
     
     
    Anmelden
    0

    The log shipping primary database primaryserver.AbraHRMS_Live has backup threshold of 60 minutes and has not performed a backup log operation for 106062 minutes. Check agent log and logshipping monitor information. Event ID 14420

    I have deleted the log but I think the msdb table has the row, how do I know which table and which row to delete?

    exec master..sp_help_log_shipping_monitor_primary
    @primary_server = 'primaryserver',
    @primary_database = 'AbraHRMS_Live'

    primary_id    primary_server    primary_database    backup_threshold    threshold_alert    threshold_alert_enabled    last_backup_file    last_backup_date    last_backup_date_utc    history_retention_period
    9C843969-8485-4D08-8DAD-A2D3D209D041    primaryserver    AbraHRMS_Live    60    14420    1    NULL    2012-12-14 18:50:20.910    2012-12-15 00:50:20.910    2880

    Which table do I look into? Please advice

     

Alle Antworten

  • Dienstag, 26. Februar 2013 18:55
     
     
    Anmelden
    0

    Refer Link : http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=SQL+Server&ProdVer=2000.80.760.0&EvtID=14420&EvtSrc=MSSQLServer&LCID=1033

    User Action

    To troubleshoot this message:

    • Make sure that the SQL Server Agent service is running for the primary server instance and that the backup job for this primary database is enabled and is scheduled to run at the appropriate frequency.

    • The backup job on the primary server might be failing. In this case, examine the job history for the backup job to look for the cause.

    • The log shipping backup job, which runs on the primary server instance, might not be able to connect to the monitor server instance to update the log_shipping_monitor_primary table. This could be caused by an authentication problem between the monitor server instance and the primary server instance.

    • The backup alert threshold might have an incorrect value. Ideally, this value is set to at least three times the frequency of the backup job. If you change the frequency of the backup job after log shipping is configured and functional, you must update the value of the backup alert threshold accordingly.

    • When the monitor server instance goes offline and then comes back online, the log_shipping_monitor_primary table is not updated with the current values before the alert message job runs. To update the monitor tables with the latest data for the primary database, runsp_refresh_log_shipping_monitor on the primary server instance.

    • On the primary or monitor server instance, the date or time is incorrect. This may also generate alert messages. Possibly the system date or time was modified on the one of them.

      Note:

      Different time zones for the two server instances should not cause a problem.

    Regards,
    Rohit Garg
    (My Blog)
    This posting is provided with no warranties and confers no rights.
    Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.

     
  • Dienstag, 26. Februar 2013 22:20
     
     
    Anmelden
    0

    I have checked the job history of LSBAckup_database1 as LSBackup_database2 and it has no errors in the primary server as well as LSCopy_database1, LSCopy_database2 in the secondary server has no error so does the LSRestore_database1 and LSRestore_database2 has no error , all errors are in the LSAlert. I have deleted and recreated log shipping so may be there is a row created in msdb table which was created initially and was never deleted. I do not know which table to look into and which row o delete.

     
  • Montag, 11. März 2013 01:32
    Moderator
     
     
    Anmelden
    0

    Hi ChitraSaha,

    It might indicate one of the following problems:

    The backup job is not running. Possible causes for this include the following: the SQL Server Agent service on the primary server instance is not running, the job is disabled, or the job's schedule has been changed.

    The backup job is failing. Possible causes for this include the following: the backup folder path is not valid, the disk is full, or any other reason that the BACKUP statement could fail.

    MSSQLSERVER_14420:

    http://support.microsoft.com/kb/329133?wa=wsignin1.0.

    http://msdn.microsoft.com/en-US/library/aa337318(v=sql.105).aspx.

    Thanks.

    Maggie Luo
    TechNet Community Support