On Thu, Jan 12, 2006 at 06:14:51PM +0530, Srinivas Rao wrote:
> Dear Athanasios,
> Thanks for your reply. My database is working fine but the user wanted some
> info. from old backup of the same database and hence I had to restore from
> tape backup however the restoration failed due to "database is in use"
> error.
>
> One more query:
> If I restore the database which is existing and operational on the Networker
> client by using Normal restoration method and relocate it to the different
> path of the same client with the same database name, will it
> delete/overwrite the existing database??
Well, since I don't have any significant experience with that particular
module, I cannot speculate
what would it do. However we are not talking about files here, we are talking
about db data, am I
correct? What would be the purpose of specifying the path?
Cheers,
Athanasios
>
> Thanks in Advance,
> Srinivas Rao,
> Networker Administrator,
> Philips Software Centre,
> Bangalore, INDIA.
> Ph: +91 94482 92416
>
> ----- Original Message -----
> From: "Athanasios Douitsis" <aduitsis AT noc.ntua DOT gr>
> To: "Srinivas Rao" <rsrini AT blr.pin.philips DOT com>
> Cc: <NETWORKER AT LISTSERV.TEMPLE DOT EDU>
> Sent: Thursday, January 12, 2006 5:44 PM
> Subject: Re: [Networker] Problem restoring SQL Database...
>
>
> > On Thu, Jan 12, 2006 at 01:26:11PM +0530, Srinivas Rao wrote:
> >
> > > Hi,
> > > When I try to restore any SQL database from a Networker client running
> with NM-SQL3.1, it is getting failed due to below error:
> > >
> > > [Microsoft][ODBC SQL Server Driver][SQL Server]Exclusive access could
> not be obtained because the database is in use..
> > > [5988] [Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE
> is terminating abnormally..
> > >
> > > This be because of somebody is accessing the database I am trying to
> restore.
> > >
> > > But my questions are:
> > > 1. Why the database cannot be restored if it is being accessed at the
> time or restoration?
> > > 2. What is the alternate method to restore the database if it is being
> used(since the NW client is a live production system so SQL services cannot
> be restarted)?
> > > 3. Although we are restoring database from tape backup, why Networker
> connects to the existing database of NW client to check whether it is being
> accessed or not?
> > >
> > > Any help would be greatly appreciated.
> >
> > Hi,
> >
> > Obviously because the database may be inconsistent during the phase of the
> restoration. I would speculate that the restoration process
> > discards everything and rebuilds it from a specific stored checkpoint
> which was made in the past. During the restoration phase, information
> > may be partialy present and that could lead to very peculiar situations.
> About question no 3, any program that uses the database for any
> > purpose needs to do it via the standard way, e.g. connect to the database
> :-).
> > Lastly, about question 2, I would suggest that you restore the database
> somewhere else and then do things by hand. This will be tiresome though.
> >
> > Cheers,
> > Athanasios
> >
> >
> >
> > >
> > > Thanks in Advance,
> > > Srinivas Rao,
> > > Networker Administrator,
> > > Philips Software Centre,
> > > Bangalore, INDIA.
> > > Ph: +91 94482 92416
> > >
> > >
> > >
> > >
> > > To sign off this list, send email to listserv AT listserv.temple DOT edu
> > > and
> type "signoff networker" in the
> > > body of the email. Please write to networker-request AT listserv.temple
> > > DOT edu
> if you have any problems
> > > wit this list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> > > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|