How can I back up a log-shipped database?

(SQL Server 2000, SP3a)
Hello all!
I've got a database that is the secondary server in a log-shipped pair. Whe
never I try
and do a BACKUP on this database, I get an error message that the database i
s in a
READ-ONLY STANDBY mode.
Is there any way to circumvent this, temporarily, and make a database backup
of a
log-shipped database?
Thanks!Hi,
Just for my benefit, what would be the purpose of backing up a database that
does not change? I assume that the secondary DB of the pair resides in DR an
d
as a result the site will be protected (fire proof etc.) secondly the
Database in the prod environment is being backed up and the backups are sent
off site.
- You might want to consider Replication over logshipping of you really must
backup the secondary DB .
"John Peterson" wrote:

> (SQL Server 2000, SP3a)
> Hello all!
> I've got a database that is the secondary server in a log-shipped pair. W
henever I try
> and do a BACKUP on this database, I get an error message that the database
is in a
> READ-ONLY STANDBY mode.
> Is there any way to circumvent this, temporarily, and make a database back
up of a
> log-shipped database?
> Thanks!
>
>|||Hello Olu!
We had hoped to be able to grab some of these Production databases for Dev a
nd QE testing.
It'd be more convenient to grab them from our DR environment (the log-shippe
d environment)
because it's already on our corporate network. But, I see that it's proving
to be more of
a challenge than we had hoped. ;-)
Out of curiosity, how would I configure Replication over log-shipping? Does
that mean I'd
set up a log-shipped DB as the Replication Publisher? I would have thought
that couldn't
be done on a read-only DB...
At this point, I'm kind of considering using DTS and the Transfer Database T
ask to
accomplish what I want. Some of the DBs are big, and I hate the thought of
essentially
BCPing everything out, but it *does* appear to work...
"Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
news:C91B47A6-F4D2-4599-819F-D87924CE42D7@.microsoft.com...[vbcol=seagreen]
> Hi,
> Just for my benefit, what would be the purpose of backing up a database th
at
> does not change? I assume that the secondary DB of the pair resides in DR
and
> as a result the site will be protected (fire proof etc.) secondly the
> Database in the prod environment is being backed up and the backups are se
nt
> off site.
> - You might want to consider Replication over logshipping of you really mu
st
> backup the secondary DB .
> "John Peterson" wrote:
>|||Well, *shoot*! As it turns out, the DTS "Transfer Databases Task" will brin
g a DB out of
RECOVERY mode. <sigh> So that's a no go. :-(
"John Peterson" <j0hnp@.comcast.net> wrote in message
news:eCi9jeCkEHA.2652@.TK2MSFTNGP15.phx.gbl...
> Hello Olu!
> We had hoped to be able to grab some of these Production databases for Dev
and QE
> testing. It'd be more convenient to grab them from our DR environment (the
log-shipped
> environment) because it's already on our corporate network. But, I see th
at it's
> proving to be more of a challenge than we had hoped. ;-)
> Out of curiosity, how would I configure Replication over log-shipping? Do
es that mean
> I'd set up a log-shipped DB as the Replication Publisher? I would have th
ought that
> couldn't be done on a read-only DB...
> At this point, I'm kind of considering using DTS and the Transfer Database
Task to
> accomplish what I want. Some of the DBs are big, and I hate the thought o
f essentially
> BCPing everything out, but it *does* appear to work...
>
> "Olu Adedeji" <OluAdedeji@.discussions.microsoft.com> wrote in message
> news:C91B47A6-F4D2-4599-819F-D87924CE42D7@.microsoft.com...
>