Logshipping question

Win 2K Adv Server SQL2K sp3a
I have implemented logshipping from server A to server B monitor
server C following the instructions
Everything works fine, every 15 minutes the Backup, Copy and Restore
jobs run
But the destination database is in Loading io Read Only
What is wrong ?
TIA
Jan Waumans<jw@.jw.com> wrote in message
news:8ef6601rfk0kg6i68vb539q1d6ap43op3v@.
4ax.com...
> Win 2K Adv Server SQL2K sp3a
> I have implemented logshipping from server A to server B monitor
> server C following the instructions
> Everything works fine, every 15 minutes the Backup, Copy and Restore
> jobs run
> But the destination database is in Loading io Read Only
> What is wrong ?
When the logs are restored onto server B they are restored WITH NO RECOVERY.
In other words the logs are not rolled forward to make the database
consistent. It is waiting for the next set of logs. If the database was
not read-only then if people made changes to the Server B database you would
not be able to read the next shipped logs.
If you want to have an updatable copy of your database where changes are
replicated every 15 minutes you might wnat to take a peek at replication.|||Bob,
I use replication since 6.0
The reason I want to go to logshipping is that replication is too
difficult to maintain for recovery sites (no schema changes except
with the unusable additional column in 2K mode, only 1 logreader per
published database, ...)
Since in Win2K you can restore a DB in read-only state allowing
additional log restores, I figure this is what logshipping should do
How the destination db could be usable anyway?
Our setup as disaster recovery does not need an access to the
destination db's in normal circumstances, but we need to be able to
switch over in case of emergency
MS clearly states that logshipping is a better solution for disaster
recovery than replication
I must do something wrong
JW
On Thu, 25 Mar 2004 20:42:59 -0000, "Bob Simms"
<bob_simms@.somewhere.com> wrote:

><jw@.jw.com> wrote in message
> news:8ef6601rfk0kg6i68vb539q1d6ap43op3v@.
4ax.com...
>When the logs are restored onto server B they are restored WITH NO RECOVERY
.
>In other words the logs are not rolled forward to make the database
>consistent. It is waiting for the next set of logs. If the database was
>not read-only then if people made changes to the Server B database you woul
d
>not be able to read the next shipped logs.
>If you want to have an updatable copy of your database where changes are
>replicated every 15 minutes you might wnat to take a peek at replication.
>|||log shipping is better than replication in case you want to have the second
server for stand-by. You can read DBs on stand-by server as long as the log
restore is not running. In your case there is nothing wrong when you see
the DB in single user mode.
<jw@.jw.com> wrote in message
news:2dh660tsgo13lv90e53dquf1c03jcren8m@.
4ax.com...
> Bob,
> I use replication since 6.0
> The reason I want to go to logshipping is that replication is too
> difficult to maintain for recovery sites (no schema changes except
> with the unusable additional column in 2K mode, only 1 logreader per
> published database, ...)
> Since in Win2K you can restore a DB in read-only state allowing
> additional log restores, I figure this is what logshipping should do
> How the destination db could be usable anyway?
> Our setup as disaster recovery does not need an access to the
> destination db's in normal circumstances, but we need to be able to
> switch over in case of emergency
> MS clearly states that logshipping is a better solution for disaster
> recovery than replication
> I must do something wrong
> JW
>
> On Thu, 25 Mar 2004 20:42:59 -0000, "Bob Simms"
> <bob_simms@.somewhere.com> wrote:
>
RECOVERY.
would
>|||Study the docs in books on line referring to Log Shipping... There is a
procedure you must go through to make the log ship databases Primary, in the
case of failure.. There is a DTS job and some exports involved... You'd be
well served to test this and ensure you have a good plan...
But until you run recovery on the secondary ( part of the process) it will
show as loading...
Wayne Snyder, MCDBA, SQL Server MVP
Computer Education Services Corporation (CESC), Charlotte, NC
www.computeredservices.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<jw@.jw.com> wrote in message
news:8ef6601rfk0kg6i68vb539q1d6ap43op3v@.
4ax.com...
> Win 2K Adv Server SQL2K sp3a
> I have implemented logshipping from server A to server B monitor
> server C following the instructions
> Everything works fine, every 15 minutes the Backup, Copy and Restore
> jobs run
> But the destination database is in Loading io Read Only
> What is wrong ?
> TIA
> Jan Waumans