By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
440,602 Members | 1,473 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 440,602 IT Pros & Developers. It's quick & easy.

Backup/Restore locks up EM

P: n/a
When I am trying to use backup or restore from the EM, a dialog box
never pops up, and the EM interface locks up. Has anyone else had
problems like this? Looks like all other functions from EM are
working fine.

Thanks,
Dave
Jul 20 '05 #1
Share this Question
Share on Google+
9 Replies


P: n/a

"Dave" <no****@nospam.com> wrote in message
news:qe********************************@4ax.com...
When I am trying to use backup or restore from the EM, a dialog box
never pops up, and the EM interface locks up. Has anyone else had
problems like this? Looks like all other functions from EM are
working fine.
Yeah I've noticed that. Not sure if the latest SP fixes that or not.


Thanks,
Dave

Jul 20 '05 #2

P: n/a
Dave (no****@nospam.com) writes:
When I am trying to use backup or restore from the EM, a dialog box
never pops up, and the EM interface locks up. Has anyone else had
problems like this? Looks like all other functions from EM are
working fine.


The obvious workaround is to learn the syntax for BACKUP and RESTORE
and run them from Query Analyzer...
--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 20 '05 #3

P: n/a

"Erland Sommarskog" <so****@algonet.se> wrote in message
news:Xn*********************@127.0.0.1...
Dave (no****@nospam.com) writes:
When I am trying to use backup or restore from the EM, a dialog box
never pops up, and the EM interface locks up. Has anyone else had
problems like this? Looks like all other functions from EM are
working fine.
The obvious workaround is to learn the syntax for BACKUP and RESTORE
and run them from Query Analyzer...

Except, that doesn't solve the problem he's referring to. Or at least the
one I'm having.

I have a restore job that runs each day (basically takes a backup of one
server and restores it to a 2nd).

Takes 4-5 hours. I've discovered that during the restore, SQL EM just won't
respond. I think somehow the select statement it must be doing in the
background to get the list of databases is being blocked by the RESTORE.
(actually thinking about this, I'm pretty sure this IS the case since I
remember figuring this out via sp_who2).

I haven't seen this problem with the BACKUP statement (which makes sense
since the DB is online during a backup. :-)



--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

Jul 20 '05 #4

P: n/a
Dave wrote:
When I am trying to use backup or restore from the EM, a dialog box
never pops up, and the EM interface locks up. Has anyone else had
problems like this? Looks like all other functions from EM are
working fine.


Could this be your problem?

http://support.microsoft.com/default...;en-us;Q319246

Ian.
Jul 20 '05 #5

P: n/a
Greg D. Moore (Strider) (mo****************@greenms.com) writes:
I have a restore job that runs each day (basically takes a backup of one
server and restores it to a 2nd).

Takes 4-5 hours. I've discovered that during the restore, SQL EM just
won't respond. I think somehow the select statement it must be doing in
the background to get the list of databases is being blocked by the
RESTORE. (actually thinking about this, I'm pretty sure this IS the case
since I remember figuring this out via sp_who2).


This does not sound right to me. I did a quick test on our development
server, and ran Enterprise Manager against that server without a problem.
I could even expand the node for that database. When I started to look at
objects, I did of course get an error message, but EM never stopped
responding. True, this was a two-minute restore, but I can't see that the
length would matter.

Could you give more details? Do you see blocking in Query Analyzer
with sp_who when it happens? In such case what does DBCC INPUTBUFFER say?

--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 20 '05 #6

P: n/a

"Erland Sommarskog" <so****@algonet.se> wrote in message
news:Xn********************@127.0.0.1...
Greg D. Moore (Strider) (mo****************@greenms.com) writes:
I have a restore job that runs each day (basically takes a backup of one
server and restores it to a 2nd).

Takes 4-5 hours. I've discovered that during the restore, SQL EM just
won't respond. I think somehow the select statement it must be doing in
the background to get the list of databases is being blocked by the
RESTORE. (actually thinking about this, I'm pretty sure this IS the case
since I remember figuring this out via sp_who2).
This does not sound right to me. I did a quick test on our development
server, and ran Enterprise Manager against that server without a problem.
I could even expand the node for that database. When I started to look at
objects, I did of course get an error message, but EM never stopped
responding. True, this was a two-minute restore, but I can't see that the
length would matter.

Could you give more details? Do you see blocking in Query Analyzer
with sp_who when it happens? In such case what does DBCC INPUTBUFFER say?


I'll have to try it again tomorrow if I get a chance, but as I recall, it's
during a restore of a DB to our SQL 7.0 server.

And it may only be the first time EM is opened.

Like I say, it's strange, but hasn't been a big enough problem for me to
investigate beyond the original problem.

And yes, I did a sp_who2 active and found the blocking SPID. A DBCC
INPUTBUFFER on the spid showed the restore.


--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

Jul 20 '05 #7

P: n/a
Greg D. Moore (Strider) (mo****************@greenms.com) writes:
I'll have to try it again tomorrow if I get a chance, but as I recall,
it's during a restore of a DB to our SQL 7.0 server.
And EM is SQL2000 or SQL7?
And yes, I did a sp_who2 active and found the blocking SPID. A DBCC
INPUTBUFFER on the spid showed the restore.


I was more interested in what the blocked spid was up to.
--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 20 '05 #8

P: n/a

"Erland Sommarskog" <so****@algonet.se> wrote in message
news:Xn**********************@127.0.0.1...
Greg D. Moore (Strider) (mo****************@greenms.com) writes:
I'll have to try it again tomorrow if I get a chance, but as I recall,
it's during a restore of a DB to our SQL 7.0 server.
And EM is SQL2000 or SQL7?
And yes, I did a sp_who2 active and found the blocking SPID. A DBCC
INPUTBUFFER on the spid showed the restore.


I was more interested in what the blocked spid was up to.


Ah good point. I THINK it was doing a select against the sysdatabases
table, but I'll have to check later today.



--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp

Jul 20 '05 #9

P: n/a

"Greg D. Moore (Strider)" <mo****************@greenms.com> wrote in message
news:HS*****************@twister.nyroc.rr.com...

"Erland Sommarskog" <so****@algonet.se> wrote in message
news:Xn**********************@127.0.0.1...
Greg D. Moore (Strider) (mo****************@greenms.com) writes:
I'll have to try it again tomorrow if I get a chance, but as I recall,
it's during a restore of a DB to our SQL 7.0 server.
And EM is SQL2000 or SQL7?
And yes, I did a sp_who2 active and found the blocking SPID. A DBCC
INPUTBUFFER on the spid showed the restore.


I was more interested in what the blocked spid was up to.


Ah good point. I THINK it was doing a select against the sysdatabases
table, but I'll have to check later today.


Ok, finally remembered to do it.

The SPID doing the restore:
RPC "master"."dbo"."restore_foo" -- no real surprise here. this is the
stored proc doing the work.

The blocked SPID from SQL EM (2000) against the DB (SQL 7.0)

select name, DATABASEPROPERTY(name, N'IsDetached'), (case when
DATABASEPROPERTY(name, N'IsShutdown') is null then -1 else
DATABASEPROPERTY(name, N'IsShutdown') end), DATABASEPROPERTY(name,
N'IsSuspect'), DATABASEPROPERTY(name, N'IsOffline'), D




--
Erland Sommarskog, SQL Server MVP, so****@algonet.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp


Jul 20 '05 #10

This discussion thread is closed

Replies have been disabled for this discussion.