Re: Can't restore master db!!
From: caeriel (caeriel_at_discussions.microsoft.com)
Date: 08/03/04
- Next message: mat: "Server Restart"
- Previous message: Mikolas Stanevicius: "msCrm install fails on SQL database creation 80070002"
- In reply to: Keith Kratochvil: "Re: Can't restore master db!!"
- Next in thread: Keith Kratochvil: "Re: Can't restore master db!!"
- Reply: Keith Kratochvil: "Re: Can't restore master db!!"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 3 Aug 2004 07:43:06 -0700
Keith: I'm still unable to restore the master database....
I tried starting the server as you & Hari instructed; the server started in single user mode. However, the restore has to be issued from the Veritas software interface. Here's the SQL Server log.
*************************************
======================================================================
Job server: Test
Job name: MasterDB NoRecov 8-03
Job started: Tuesday, August 03, 2004 at 10:08:07 AM
Job type: Restore
Job Log: BEX41.txt
======================================================================
Drive and media information from media mount:
Robotic Library Name:
Drive Name: Quantum 1
Slot: 0
Media GUID: {2E9659D2-C5B5-43BF-BD2A-502B2E1054E1}
Media Label: Test Wk1 Monday
Overwrite Protection Time Left: None
Append Time Left: Infinite
======================================================================
Job Operation - Restore
======================================================================
Restoring data to Test .
Storage Media #1: " Media created 8/2/04 08:24:56 PM "
Backup performed on 8/3/04 at 8:12 AM
Backup set #6: " Full Backup "
Restore started on 8/3/04 at 10:10:35 AM.
An error occurred on a query to database master.
^ ^ ^ ^ ^
SQL Server returned the following error message:
RESTORE DATABASE must be used in single user mode when trying to restore the master database.
^ ^ ^ ^ ^
Restore completed on 8/3/04 at 10:13:42 AM.
1 item was skipped.
Processed 0 bytes in 3 minutes and 7 seconds.
Throughput rate: 0.0 MB/min
----------------------------------------------------------------------
======================================================================
Job ended: Tuesday, August 03, 2004 at 10:14:31 AM
Job completion status: Failed
======================================================================
****************************************************
2004-08-03 09:55:16.51 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel X86)
Nov 27 1998 22:20:07
Copyright (c) 1988-1998 Microsoft Corporation
Standard Edition on Windows NT 4.0 (Build 1381: Service Pack 6)
2004-08-03 09:55:16.51 kernel Copyright (C) 1988-1997 Microsoft Corporation.
2004-08-03 09:55:16.52 kernel All rights reserved.
2004-08-03 09:55:16.52 kernel Logging SQL Server messages in file 'D:\MSSQL7\log\ERRORLOG'.
2004-08-03 09:55:16.58 kernel initconfig: Number of user connections limited to 32767.
2004-08-03 09:55:16.58 kernel SQL Server is starting at priority class 'normal'(1 CPU detected).
2004-08-03 09:55:16.70 kernel User Mode Scheduler configured for thread processing
2004-08-03 09:55:17.96 server Directory Size: 10801
2004-08-03 09:55:18.05 spid1 Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks
2004-08-03 09:55:18.05 kernel Attempting to initialize Distributed Transaction Coordinator.
2004-08-03 09:55:18.82 spid1 Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE
2004-08-03 09:55:18.83 spid1 Warning ******************
2004-08-03 09:55:18.83 spid1 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-08-03 09:55:18.84 spid1 Warning ******************
2004-08-03 09:55:18.85 spid1 Starting up database 'master'.
2004-08-03 09:55:18.85 spid1 Opening file D:\MSSQL7\data\master.mdf.
2004-08-03 09:55:18.89 spid1 Opening file D:\MSSQL7\data\mastlog.ldf.
2004-08-03 09:55:18.99 spid1 Loading SQL Server's Unicode collation.
2004-08-03 09:55:19.01 spid1 Loading SQL Server's non-Unicode sort order and character set.
2004-08-03 09:55:19.24 spid1 4 transactions rolled forward in database 'master' (1).
2004-08-03 09:55:19.25 spid1 0 transactions rolled back in database 'master' (1).
2004-08-03 09:55:19.35 spid1 Starting up database 'model'.
2004-08-03 09:55:19.36 spid1 Opening file D:\MSSQL7\DATA\model.mdf.
2004-08-03 09:55:19.43 spid1 Opening file D:\MSSQL7\DATA\modellog.ldf.
2004-08-03 09:55:19.63 spid1 Clearing tempdb database.
2004-08-03 09:55:19.69 spid1 Creating file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.87 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:19.97 spid1 Creating file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:19.99 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:20.12 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:20.14 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.15 spid1 Closing file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.25 spid1 Closing file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.34 spid1 Starting up database 'tempdb'.
2004-08-03 09:55:21.38 spid1 Opening file D:\MSSQL7\DATA\TEMPDB.MDF.
2004-08-03 09:55:21.41 spid1 Opening file D:\MSSQL7\DATA\TEMPLOG.LDF.
2004-08-03 09:55:21.69 spid1 Server name is 'AOATESTBOX'.
2004-08-03 09:55:21.70 kernel Using 'SQLEVN70.DLL' version '7.00.623'.
2004-08-03 09:55:21.71 kernel Using 'OPENDS60.DLL' version '7.00.00.0623'.
2004-08-03 09:55:21.71 ods Using 'SSNMPN70.DLL' version '7.0.623' to listen on '\\.\pipe\sql\query'.
2004-08-03 09:55:21.72 ods Using 'SSMSSO70.DLL' version '7.0.623' to listen on '3180'.
2004-08-03 09:55:21.82 ods Using 'SSMSRP70.DLL' version '7.0.623' to listen on 'AOATESTBOX'.
2004-08-03 09:55:22.68 spid5 Starting up database 'msdb'.
2004-08-03 09:55:22.68 spid5 Opening file D:\MSSQL7\DATA\msdbdata.mdf.
2004-08-03 09:55:22.70 spid6 Starting up database 'pubs'.
2004-08-03 09:55:22.70 spid6 Opening file D:\MSSQL7\DATA\pubs.mdf.
2004-08-03 09:55:22.72 spid7 Starting up database 'Northwind'.
2004-08-03 09:55:22.72 spid7 Opening file D:\MSSQL7\DATA\northwnd.mdf.
2004-08-03 09:55:22.82 spid5 Opening file D:\MSSQL7\DATA\msdblog.ldf.
2004-08-03 09:55:22.85 spid7 Opening file D:\MSSQL7\DATA\northwnd.ldf.
2004-08-03 09:55:22.87 spid6 Opening file D:\MSSQL7\DATA\pubs_log.ldf.
2004-08-03 09:55:23.55 spid1 Recovery complete.
2004-08-03 09:55:23.56 spid1 SQL Server's Unicode collation is:
2004-08-03 09:55:23.57 spid1 'English' (ID = 1033).
2004-08-03 09:55:23.57 spid1 comparison style = 196609.
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode sort order is:
2004-08-03 09:55:23.58 spid1 'nocase_850' (ID = 42).
2004-08-03 09:55:23.58 spid1 SQL Server's non-Unicode character set is:
2004-08-03 09:55:23.58 spid1 'cp850' (ID = 2).
2004-08-03 09:57:00.02 spid6 Using 'xpstar.dll' version '1998.11.13' to execute extended stored procedure 'sp_MSgetversion'.
2004-08-03 10:16:44.05 kernel SQL Server shutdown due to Ctrl-C or Ctrl-Break signal.
*******************************************************
Here's the Veritas log:
************************************************
************************************************
"Keith Kratochvil" wrote:
> This method will work. I think Hari copied and pasted the answer directly
> from Books Online! I would have provided exactly the same answer. I
> probably would have also pointed you at Books Online (within your SQL Server
> program group). BACKUP and RESTORE information and examples can be found
> there. Knowing how to restore the data that you are backing up is
> important. Cathy, you are smart to be doing your research now (instead of
> when the entire company is waiting for you to restore the data).
>
> --
> Keith
>
>
> "Hari Prasad" <hari_prasad_k@hotmail.com> wrote in message
> news:u%23SoMWKeEHA.1764@TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > To restore the master database you have start the SQL server itself in
> > Single user mode.
> >
> > 1. Stop the MSSQL server and sql agent service
> >
> > 2. Go to command prompt and execute below command,.
> >
> > sqlservr.exe -c -m
> >
> > 3. Login to sql server using query analyzer and retore the master
> database.
> >
> > 4. After the restore .. go to old comamnd prompt and press CONTRL and C to
> > close the old session
> >
> > 5. Go to control panel and start the MSSQL server and Sql agent service.
> >
> > Note:
> >
> > I recommend you to restore the master database first followed with other
> > databases.
> >
> > Thanks
> > Hari
> > MCDBA
> >
> >
> >
> > "Cathy Finnegan" <eliminates_spam_caeriel1@cablespeed.com> wrote in
> message
> > news:jamsg0tqoig5fqs15kdonltvlitoiktf3u@4ax.com...
> > > Hi:
> > >
> > > I've got a problem that's causing me headaches! I'm using Veritas Backup
> > Exec to perform my db backups. I've just
> > > recently taken over the DBA responsibilities and one of the first things
> > I've wanted to do is test those backups since
> > > we've never had occassion to use the backups. I have a test system that
> > I'm using and have it configured exactly as the
> > > production system.
> > >
> > > After installing MS SQL Server 7 putting on SP4 and all the security
> > patches I try to restore all the databases. I can
> > > get all my databases restored except the master db that contains all my
> > security info. I keep getting the message
> > > "must be in single user mode". I've tried to set the master db into
> > single user mode and there's just no way to do it!!
> > > I've tried using the EM and the sp_dboption. Without that master db
> > restored I'm in deep doo-doo!
> > >
> > > Any ideas how I can handle this?? Any help/suggestions is greatly
> > appreciated.
> > >
> > > TIA
> > >
> > > Cathy
> > >
> > > SQL Server 7( SP4), NT4.0
> >
> >
>
>
- Next message: mat: "Server Restart"
- Previous message: Mikolas Stanevicius: "msCrm install fails on SQL database creation 80070002"
- In reply to: Keith Kratochvil: "Re: Can't restore master db!!"
- Next in thread: Keith Kratochvil: "Re: Can't restore master db!!"
- Reply: Keith Kratochvil: "Re: Can't restore master db!!"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|