xnmb
asked on
SQL2K Log Shipping Error 3443
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.
Thanks.
[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.
Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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.
ASKER
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.
Thanks.