We have a server at a disaster recovery site that was in warm standby. In
order for the server to be fully functional, we had to bring the databases
out of warm standby to install some client software that read the databases
of the standby server. While trying to put the databases back into warm
standby restoring the next log in sequence from the production server, I get
an error saying "Exclusive access could not be obtained because the database
is in use". However, the database is in single-user mode. When trying a
restore log command in SQL, I get an error "preceding restore operation did
not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
abnormally.
Is there any way to get the database(s) back into warm standy mode without
having to set it up again from scratch?
Thanks,
RS
Nope. Once it is set to "normal" mode you have to restore a full backup
WITH STANDBY.
Keith
"RS" <rspen@.yahoo.com> wrote in message
news:%23y9Z2Y7eEHA.2764@.TK2MSFTNGP11.phx.gbl...
> We have a server at a disaster recovery site that was in warm standby. In
> order for the server to be fully functional, we had to bring the databases
> out of warm standby to install some client software that read the
databases
> of the standby server. While trying to put the databases back into warm
> standby restoring the next log in sequence from the production server, I
get
> an error saying "Exclusive access could not be obtained because the
database
> is in use". However, the database is in single-user mode. When trying a
> restore log command in SQL, I get an error "preceding restore operation
did
> not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
> abnormally.
> Is there any way to get the database(s) back into warm standy mode without
> having to set it up again from scratch?
> Thanks,
> RS
>
sql
Showing posts with label recovery. Show all posts
Showing posts with label recovery. Show all posts
Wednesday, March 28, 2012
Put database in warm standby after changing it from read only?
We have a server at a disaster recovery site that was in warm standby. In
order for the server to be fully functional, we had to bring the databases
out of warm standby to install some client software that read the databases
of the standby server. While trying to put the databases back into warm
standby restoring the next log in sequence from the production server, I get
an error saying "Exclusive access could not be obtained because the database
is in use". However, the database is in single-user mode. When trying a
restore log command in SQL, I get an error "preceding restore operation did
not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
abnormally.
Is there any way to get the database(s) back into warm standy mode without
having to set it up again from scratch?
Thanks,
RSNope. Once it is set to "normal" mode you have to restore a full backup
WITH STANDBY.
Keith
"RS" <rspen@.yahoo.com> wrote in message
news:%23y9Z2Y7eEHA.2764@.TK2MSFTNGP11.phx.gbl...
> We have a server at a disaster recovery site that was in warm standby. In
> order for the server to be fully functional, we had to bring the databases
> out of warm standby to install some client software that read the
databases
> of the standby server. While trying to put the databases back into warm
> standby restoring the next log in sequence from the production server, I
get
> an error saying "Exclusive access could not be obtained because the
database
> is in use". However, the database is in single-user mode. When trying a
> restore log command in SQL, I get an error "preceding restore operation
did
> not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
> abnormally.
> Is there any way to get the database(s) back into warm standy mode without
> having to set it up again from scratch?
> Thanks,
> RS
>
order for the server to be fully functional, we had to bring the databases
out of warm standby to install some client software that read the databases
of the standby server. While trying to put the databases back into warm
standby restoring the next log in sequence from the production server, I get
an error saying "Exclusive access could not be obtained because the database
is in use". However, the database is in single-user mode. When trying a
restore log command in SQL, I get an error "preceding restore operation did
not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
abnormally.
Is there any way to get the database(s) back into warm standy mode without
having to set it up again from scratch?
Thanks,
RSNope. Once it is set to "normal" mode you have to restore a full backup
WITH STANDBY.
Keith
"RS" <rspen@.yahoo.com> wrote in message
news:%23y9Z2Y7eEHA.2764@.TK2MSFTNGP11.phx.gbl...
> We have a server at a disaster recovery site that was in warm standby. In
> order for the server to be fully functional, we had to bring the databases
> out of warm standby to install some client software that read the
databases
> of the standby server. While trying to put the databases back into warm
> standby restoring the next log in sequence from the production server, I
get
> an error saying "Exclusive access could not be obtained because the
database
> is in use". However, the database is in single-user mode. When trying a
> restore log command in SQL, I get an error "preceding restore operation
did
> not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
> abnormally.
> Is there any way to get the database(s) back into warm standy mode without
> having to set it up again from scratch?
> Thanks,
> RS
>
Put database in warm standby after changing it from read only?
We have a server at a disaster recovery site that was in warm standby. In
order for the server to be fully functional, we had to bring the databases
out of warm standby to install some client software that read the databases
of the standby server. While trying to put the databases back into warm
standby restoring the next log in sequence from the production server, I get
an error saying "Exclusive access could not be obtained because the database
is in use". However, the database is in single-user mode. When trying a
restore log command in SQL, I get an error "preceding restore operation did
not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
abnormally.
Is there any way to get the database(s) back into warm standy mode without
having to set it up again from scratch?
Thanks,
RSNope. Once it is set to "normal" mode you have to restore a full backup
WITH STANDBY.
--
Keith
"RS" <rspen@.yahoo.com> wrote in message
news:%23y9Z2Y7eEHA.2764@.TK2MSFTNGP11.phx.gbl...
> We have a server at a disaster recovery site that was in warm standby. In
> order for the server to be fully functional, we had to bring the databases
> out of warm standby to install some client software that read the
databases
> of the standby server. While trying to put the databases back into warm
> standby restoring the next log in sequence from the production server, I
get
> an error saying "Exclusive access could not be obtained because the
database
> is in use". However, the database is in single-user mode. When trying a
> restore log command in SQL, I get an error "preceding restore operation
did
> not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
> abnormally.
> Is there any way to get the database(s) back into warm standy mode without
> having to set it up again from scratch?
> Thanks,
> RS
>
order for the server to be fully functional, we had to bring the databases
out of warm standby to install some client software that read the databases
of the standby server. While trying to put the databases back into warm
standby restoring the next log in sequence from the production server, I get
an error saying "Exclusive access could not be obtained because the database
is in use". However, the database is in single-user mode. When trying a
restore log command in SQL, I get an error "preceding restore operation did
not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
abnormally.
Is there any way to get the database(s) back into warm standy mode without
having to set it up again from scratch?
Thanks,
RSNope. Once it is set to "normal" mode you have to restore a full backup
WITH STANDBY.
--
Keith
"RS" <rspen@.yahoo.com> wrote in message
news:%23y9Z2Y7eEHA.2764@.TK2MSFTNGP11.phx.gbl...
> We have a server at a disaster recovery site that was in warm standby. In
> order for the server to be fully functional, we had to bring the databases
> out of warm standby to install some client software that read the
databases
> of the standby server. While trying to put the databases back into warm
> standby restoring the next log in sequence from the production server, I
get
> an error saying "Exclusive access could not be obtained because the
database
> is in use". However, the database is in single-user mode. When trying a
> restore log command in SQL, I get an error "preceding restore operation
did
> not specify WITH NORECOVERY or WITH STANDBY. RESTORE LOG is terminating
> abnormally.
> Is there any way to get the database(s) back into warm standy mode without
> having to set it up again from scratch?
> Thanks,
> RS
>
Wednesday, March 7, 2012
Publisher set to Simple Recovery - Is this a problem?
If the publisher database is set on simple recovery mode and if the
transaction log gets truncated on check point, then is there a chance that
the rows that should be replicated might get lost before the log reader agent
can read them and send them to the distributor. Publisher is a 7.0 box and
the distributor/subscriber is a 2000 box.
Adam,
the rows won't be removed unless the log is marked by sp_repldone, so you're
safe.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
transaction log gets truncated on check point, then is there a chance that
the rows that should be replicated might get lost before the log reader agent
can read them and send them to the distributor. Publisher is a 7.0 box and
the distributor/subscriber is a 2000 box.
Adam,
the rows won't be removed unless the log is marked by sp_repldone, so you're
safe.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Publish Subscription replication - Side effects?
Hi Guys,
I've been given the task of creating a disaster recovery "replica" of a
production SQL server and keeping it current.
(SQL 2000)
At first we thought of using scripts to do a backup/restore method.
But a couple of the databases are upwards of a hundred gigabytes...
A bit hard on drive space.
I thought a better method would be to replicate the databases using the
Publish and "push subscriptions".
I'm not very knowledgeable about SQL management, However with the help of
Google and a little time,
I mamnaged to make it work experimentally with the Northwind database.
But that's tiny compared to the live DBs
My question is:
Am I likely to see any 'unforseen' side effects of replicating by this
method?
Thanks,
Jim
To keep maximum performance on your main SQL Server I would consider
"pulling" the transactionally replicated data.
This article from Microsoft has alot of great tips on how to maximize
replication performance.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
If you have money for a nice SAN unit you can check out Split Mirroring.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/spltmirr.mspx
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Jim Millar" <Jim.Millar_NOSPAM_@.hotmail.com> wrote in message
news:epEJFv0QIHA.2376@.TK2MSFTNGP02.phx.gbl...
> Hi Guys,
> I've been given the task of creating a disaster recovery "replica" of a
> production SQL server and keeping it current.
> (SQL 2000)
> At first we thought of using scripts to do a backup/restore method.
> But a couple of the databases are upwards of a hundred gigabytes...
> A bit hard on drive space.
> I thought a better method would be to replicate the databases using the
> Publish and "push subscriptions".
> I'm not very knowledgeable about SQL management, However with the help of
> Google and a little time,
> I mamnaged to make it work experimentally with the Northwind database.
> But that's tiny compared to the live DBs
> My question is:
> Am I likely to see any 'unforseen' side effects of replicating by this
> method?
> Thanks,
> Jim
>
|||Thanks Warren!
I'll give it a go.
Unfortunately the client is 'cheap' and wants to spend as little as
possible.
Getting to be par for the course these days...
"Warren Brunk" <wbrunk@.techintsolutions.com> wrote in message
news:elyRBZ5QIHA.4180@.TK2MSFTNGP06.phx.gbl...
> To keep maximum performance on your main SQL Server I would consider
> "pulling" the transactionally replicated data.
> This article from Microsoft has alot of great tips on how to maximize
> replication performance.
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
> If you have money for a nice SAN unit you can check out Split Mirroring.
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/spltmirr.mspx
>
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
>
> "Jim Millar" <Jim.Millar_NOSPAM_@.hotmail.com> wrote in message
> news:epEJFv0QIHA.2376@.TK2MSFTNGP02.phx.gbl...
>
I've been given the task of creating a disaster recovery "replica" of a
production SQL server and keeping it current.
(SQL 2000)
At first we thought of using scripts to do a backup/restore method.
But a couple of the databases are upwards of a hundred gigabytes...
A bit hard on drive space.
I thought a better method would be to replicate the databases using the
Publish and "push subscriptions".
I'm not very knowledgeable about SQL management, However with the help of
Google and a little time,
I mamnaged to make it work experimentally with the Northwind database.
But that's tiny compared to the live DBs
My question is:
Am I likely to see any 'unforseen' side effects of replicating by this
method?
Thanks,
Jim
To keep maximum performance on your main SQL Server I would consider
"pulling" the transactionally replicated data.
This article from Microsoft has alot of great tips on how to maximize
replication performance.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
If you have money for a nice SAN unit you can check out Split Mirroring.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/spltmirr.mspx
/*
Warren Brunk - MCITP,MCTS,MCDBA
www.techintsolutions.com
*/
"Jim Millar" <Jim.Millar_NOSPAM_@.hotmail.com> wrote in message
news:epEJFv0QIHA.2376@.TK2MSFTNGP02.phx.gbl...
> Hi Guys,
> I've been given the task of creating a disaster recovery "replica" of a
> production SQL server and keeping it current.
> (SQL 2000)
> At first we thought of using scripts to do a backup/restore method.
> But a couple of the databases are upwards of a hundred gigabytes...
> A bit hard on drive space.
> I thought a better method would be to replicate the databases using the
> Publish and "push subscriptions".
> I'm not very knowledgeable about SQL management, However with the help of
> Google and a little time,
> I mamnaged to make it work experimentally with the Northwind database.
> But that's tiny compared to the live DBs
> My question is:
> Am I likely to see any 'unforseen' side effects of replicating by this
> method?
> Thanks,
> Jim
>
|||Thanks Warren!
I'll give it a go.
Unfortunately the client is 'cheap' and wants to spend as little as
possible.
Getting to be par for the course these days...
"Warren Brunk" <wbrunk@.techintsolutions.com> wrote in message
news:elyRBZ5QIHA.4180@.TK2MSFTNGP06.phx.gbl...
> To keep maximum performance on your main SQL Server I would consider
> "pulling" the transactionally replicated data.
> This article from Microsoft has alot of great tips on how to maximize
> replication performance.
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/tranrepl.mspx
> If you have money for a nice SAN unit you can check out Split Mirroring.
> http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/spltmirr.mspx
>
> --
> /*
> Warren Brunk - MCITP,MCTS,MCDBA
> www.techintsolutions.com
> */
>
> "Jim Millar" <Jim.Millar_NOSPAM_@.hotmail.com> wrote in message
> news:epEJFv0QIHA.2376@.TK2MSFTNGP02.phx.gbl...
>
Subscribe to:
Posts (Atom)