SQL2K Log Shipping Error 3443

Posted on 2005-05-16
Last Modified: 2008-03-03
I setup log shipping which was working perfectly for serveral months. Then one day the standby server started receiving this error:

[Microsoft SQL-DMO (ODBC SQLState: HY000)] Error 3443: [Microsoft][ODBC SQL Server Driver][SQL Server]Database 'DB6198' (database ID 7) was marked for standby or read-only use, but has been modified. The RESTORE LOG statement cannot be performed.

restoring manually a t-log file doesn't work either.

First time I encountered this, I couldn't resolve the issue, and so I reconfigured log shipping and had it working again, although only for about 1-2 weeks. Then the same error occured again in the log shipping monitor history.

What's causing this problem and how do I fix it? I wanted to get a better understanding of the cause of this error (and of course how to resolve it) before I attempt to re-setup log shipping.

BTW, the standby serveris not accessible to anyone except me, and so it's next to impossible that anyone had modified/changed the standby DB, considering also that the DB is in read-only mode.

I'll give an extra 500 points (total of 1000) to anyone who could explain what exactly is happening here and how the issue can be resolved.


Question by:xnmb
    LVL 13

    Accepted Solution

    1. The database was in STANDBY OR READ-ONLY mode?
    2. Describe your logshipping settings:
    For example: Production->FTP server->Backup
    3. Any disk space bottlenecks on the path?
    LVL 5

    Author Comment

    Sorry for my late response. Been very busy.

    1) READ-ONLY mode
    2) Prodcution backs up on a shared directory on the standby server (also the log shipping monitor server) over the internet. Connection is very reliable, there are no issues in the transaction log backups.
    3) The server on which logs are backed up have plenty of free disc space.

    No problems in backing up. The issue is restoring the log files on the standby server.

    LVL 5

    Author Comment

    i was never able to identify the culprit and had to re-setup log shipping to rid the problem. in any case, i appreciate ispalany's efforts in trying to help here and so i'm awarding him all the points.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Find Ransomware Secrets With All-Source Analysis

    Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

    International Data Corporation (IDC) prognosticates that before the current the year gets over disbursing on IT framework products to be sent in cloud environs will be $37.1B.
    The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…
    Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
    Viewers will learn how to use the UPDATE and DELETE statements to change or remove existing data from their tables. Make a table: Update a specific column given a specific row using the UPDATE statement: Remove a set of values using the DELETE s…

    760 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    8 Experts available now in Live!

    Get 1:1 Help Now