Log Shipping Question

I have successfully setup log shipping between my production SQL 2000 Server
(setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a WAN)
What is the best way if any to stop the log shipping for a extended period
of time and re-enable it without setting up the entire maintenance plan
again. Is this possible? What happened is I needed to shut down my
production server due to hurricane Wilma as a precaution. I disabled the log
shipping jobs on both servers but didn't actually physicall shut down the
Disaster Recovery SQL 2000 Server.
The servers got out of synch...although it said the logs were being shipped
and they were working correctly after I turned the production server back on.
However, the log were not being copied to the Disaster Recovery Server.
Any help would be appreciated. Thanks!!
Hello,
Based on my experience, you shall remove and recreate log shipping for this
situation becaseu the expected backup on the primary servers were not
properly created due to server shutdown.
More related information:
329133.KB.EN-US INF: Troubleshooting SQL Server 2000 Log Shipping "Out of
Sync" Errors
http://support.microsoft.com/default...B;EN-US;329133
314515.KB.EN-US INF: Frequently Asked Questions - SQL Server 2000 - Log
Shipping
http://support.microsoft.com/default...B;EN-US;314515
SQL Server 2000 How To Setup Log Shipping
http://www.microsoft.com/downloads/d...&familyid=7395
ec1b-199f-42bc-a31b-2056adf73f94
http://www.microsoft.com/technet/tre...hnet/prodtechn
ol/sql/deploy/prodspecs/logship1.asp
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
| Thread-Topic: Log Shipping Question
| thread-index: AcXmR7EoN/OMKH5UTPqRcRbKocEcOg==
| X-WBNR-Posting-Host: 66.20.1.9
| From: "=?Utf-8?B?Rm9naG9ybkxlZ2hvcm4=?=" <foghornleghorn@.nospam.postalias>
| Subject: Log Shipping Question
| Date: Thu, 10 Nov 2005 14:40:03 -0800
| Lines: 17
| Message-ID: <E1996FA4-68BA-4906-9886-D05F65119C1A@.microsoft.com>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="Utf-8"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Content-Class: urn:content-classes:message
| Importance: normal
| Priority: normal
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
| Newsgroups: microsoft.public.sqlserver.replication
| NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
| Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
| Xref: TK2MSFTNGXA02.phx.gbl microsoft.public.sqlserver.replication:66533
| X-Tomcat-NG: microsoft.public.sqlserver.replication
|
| I have successfully setup log shipping between my production SQL 2000
Server
| (setup in a Cluster) and my Disaster Recovery SQL 2000 Server (across a
WAN)
|
| What is the best way if any to stop the log shipping for a extended
period
| of time and re-enable it without setting up the entire maintenance plan
| again. Is this possible? What happened is I needed to shut down my
| production server due to hurricane Wilma as a precaution. I disabled the
log
| shipping jobs on both servers but didn't actually physicall shut down the
| Disaster Recovery SQL 2000 Server.
|
| The servers got out of synch...although it said the logs were being
shipped
| and they were working correctly after I turned the production server back
on.
| However, the log were not being copied to the Disaster Recovery Server.
|
| Any help would be appreciated. Thanks!!
|
|
|