Ashish,

You should already have deleted the log shipping maintenance plan that was
moved from the original primary server onto the current primary server
during fail-over so that log shipping will stop. Provided that you do not
have another server to be used as a standby server for the new primary
server, you have the following options (I am sure other people can think of
more):

Do the back up of the current server and restore the database on the
original primary server while making the database on the primary server
restricted so that no new transaction will take place on the current primary
server (you probably want to do this during off hours anyway) then
reconfigure log shipping from the original primary server.

or
Configure the log shipping from the current primary (original secondary)
server then fail-over to the original primary server. You may want to
transfer logins if any new logins were created after the initial fail-over.

Hope this helps.

Sang Nahm

-----Original Message-----
From: Viradia, Ashish [mailto:[Email Address Removed] Wednesday, June 19, 2002 2:46 PM
To: '[Email Address Removed] Log shipping


Can any one help me with fail back to original primary from current
primary(original secondary) using Log shipping?


Ashish Viradia
Database Administration
(410) 613-6405



---------------------------------------------------------------------
To unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page