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 mate,

The way I understand it is you could have just shut down your production
server without changing/stopping/disabling the log shipping jobs and just
bring it back online when your happy (the hurricane has passed!) and the
backup/copy and restores should resume as normal?
The shipping jobs seems very automated once started and syncronised - think
of it like a 'long reboot' of your production boxes. Your boxes aer fine
after bouncing them right - so whats the difference if they are down for a
few days?

I'm in the middle of documenting a similar setup with my production box (non
clustered) getting logs sent to the backup SQL box accross a WAN - the most
complex part of the exercise seems to be getting the backup DB up and running
post failure/disaster of the production box.

Hope this helps you mate.

Paul.

"foghorn69 (AT) news (DOT) postalias" wrote: