Log Shipping and Recovery

I have just created a pair of log shipping SQL Servers.
Both are running SQL Server 2000 sp3 on Win2k sp3.
I've read the documentation on how to change roles between
the servers, but it assumes that both servers are
available for a controlled change. What if the primary
server is destroyed? How can I make the secondary server
the primary in an emergency situation? I know I can't just
change the database on the secondary from Read-Only to
Normal. What has to happen in order for this secondary
server to become active?
TIA,
Ken> I know I can't just
> change the database on the secondary from Read-Only to
> Normal.
Why do you say that? All you should need to do is:
RESTORE DATABASE dbname WITH RECOVERY
Above assumes that EM's log shipping doesn't do anything strange.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Ken Krause" <kenkrause@.promaxautonews.com> wrote in message
news:005601c3aba4$e6b6c5f0$a401280a@.phx.gbl...
> I have just created a pair of log shipping SQL Servers.
> Both are running SQL Server 2000 sp3 on Win2k sp3.
> I've read the documentation on how to change roles between
> the servers, but it assumes that both servers are
> available for a controlled change. What if the primary
> server is destroyed? How can I make the secondary server
> the primary in an emergency situation? I know I can't just
> change the database on the secondary from Read-Only to
> Normal. What has to happen in order for this secondary
> server to become active?
> TIA,
> Ken|||I have documentation for this, send me an email
and I will reply with the information.
>--Original Message--
>I have just created a pair of log shipping SQL Servers.
>Both are running SQL Server 2000 sp3 on Win2k sp3.
>I've read the documentation on how to change roles
between
>the servers, but it assumes that both servers are
>available for a controlled change. What if the primary
>server is destroyed? How can I make the secondary server
>the primary in an emergency situation? I know I can't
just
>change the database on the secondary from Read-Only to
>Normal. What has to happen in order for this secondary
>server to become active?
>TIA,
>Ken
>.
>|||The book Microsoft SQL Server 2000 High Availability
covers this in the Log Shipping chapter. Making a role
change has nothing to do with whether the primary is
available ... you can make it, but you may possibly lose
the last transactions if you can't get the tail of the
log. You're only as good as your last tran log you have
access to.
If you have the DB in read-only mode, this is incorrect.
I assume it is in STANDBY, which shows the DB as read-only.
>--Original Message--
>I have just created a pair of log shipping SQL Servers.
>Both are running SQL Server 2000 sp3 on Win2k sp3.
>I've read the documentation on how to change roles
between
>the servers, but it assumes that both servers are
>available for a controlled change. What if the primary
>server is destroyed? How can I make the secondary server
>the primary in an emergency situation? I know I can't
just
>change the database on the secondary from Read-Only to
>Normal. What has to happen in order for this secondary
>server to become active?
>TIA,
>Ken
>.
>