SQL 2000 msdb restore

[molonede]

I can't get msdb recovered, I believe it is a bug.  Notice my command indicates recovered, but netbackup seems to use a norecovery.

Anyone have this issue, was there a patch sent?

I opened a support case with Symantic, just not getting any answers.

OPERATION RESTORE
OBJECTTYPE DATABASE
DATABASE "msdb"
# The following image is type: Full
NBIMAGE "jhs-meridian.MSSQL7.JHS-MERIDIAN.db.msdb.~.0.001of001.20080928145454..C"
SQLHOST "DM-PECSYS"
NBSERVER "ZAKORI.HEALTHALL.COM"
BROWSECLIENT "jhs-meridian"
MAXTRANSFERSIZE 0
BLOCKSIZE 0
RESTOREOPTION REPLACE
RECOVEREDSTATE RECOVERED
ENDOPER TRUE

INF - RESTORE STARTED USING
Microsoft SQL Server  2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Batch = C:\Program Files\VERITAS\NetBackup\DbExt\MsSql\restore_msdb.bch, Op# = 1.
INF - Using backup image jhs-meridian.MSSQL7.JHS-MERIDIAN.db.msdb.~.0.001of001.20080928145454..C
INF - restore database "msdb" from VIRTUAL_DEVICE='VNBU0-2948-2960-1222779062' with blocksize = 512, maxtransfersize = 65536, buffercount = 1, replace , norecovery
INF - Number of stripes: 1, Number of buffers per stripe 1.
INF - Created VDI object for SQL Server instance <DM-PECSYS>. Connection timeout is <300> seconds.
Restore started Tue Sep 30 08:51:05 2008

08:51:12 (4684476.xxx) Restore job id 4684476 will require 1 image.
08:51:12 (4684476.xxx) Media id T00198 is needed for the restore.

08:51:51 (4684476.001) Restoring from image created Sun Sep 28 14:54:57 2008
08:51:54 (4684476.001) INF - Data socket = achilles.healthall.com.IPC:1151;721272616859e4da4abfbd1882a2ec84;4;7200
08:51:55 (4684476.001) INF - Name socket = achilles.healthall.com.IPC:1152;8601c96339251d23e7a5c760011c0f70;4;7200
08:51:55 (4684476.001) INF - If Media id T00198 is not in a robotic library administrative interaction may be required to satisfy this mount request.
08:51:55 (4684476.001) INF - Job id = 4684476
08:51:55 (4684476.001) INF - Backup id = jhs-meridian.healthall.com_1222628097
08:51:55 (4684476.001) INF - Backup time = 1222628097
08:51:55 (4684476.001) INF - Policy name = NT_SQLSERVER_DAILY
08:51:56 (4684476.001) INF - Snapshot = 0
08:51:56 (4684476.001) INF - Frozen image = 0
08:51:56 (4684476.001) INF - Backup copy = 0
08:51:56 (4684476.001) INF - Master server = zakori.healthall.com
08:51:57 (4684476.001) INF - No drives available or requesting resources
08:51:57 (4684476.001) INF - Media server = achilles.healthall.com
08:51:57 (4684476.001) INF - New data socket = achilles.healthall.com.IPC:1150;a0365a715c55e1abaf6b495551d8de57;4;7200
08:51:57 (4684476.001) INF - Use shared memory = 0
08:51:57 (4684476.001) INF - Restore id = 4684476.001
08:51:57 (4684476.001) INF - Encrypt = 0
08:51:58 (4684476.001) INF - Client read timeout = 7200
08:51:58 (4684476.001) INF - Media mount timeout = 0
08:51:58 (4684476.001) INF - client = dm-pecsys.healthall.com
08:51:58 (4684476.001) INF - requesting_client = dm-pecsys.healthall.com
08:51:58 (4684476.001) INF - browse_client = jhs-meridian.healthall.com
08:52:01 (4684476.001) INF - Waiting for mount of media id T00198 on server achilles.healthall.com for reading.
08:52:24 (4684476.001) INF - Waiting for positioning of media id T00198 on server achilles.healthall.com for reading.
08:52:58 (4684476.001) INF - Beginning restore from server achilles.healthall.com to client dm-pecsys.healthall.com.
08:53:09 /jhs-meridian.MSSQL7.JHS-MERIDIAN.db.msdb.~.0.001of001.20080928145454..C
08:53:14 (4684476.001) Status of restore from image created Sun Sep 28 14:54:57 2008 = the requested operation was successfully completed

08:53:16 INF - Server status = 0
DBMS MSG - ODBC return code <-1>, SQL State <01000>, SQL Message <4035><[Microsoft][ODBC SQL Server Driver][SQL Server]Processed 5184 pages for database 'msdb', file 'MSDBData' on file 1.>.
DBMS MSG - SQL Message <4035><[Microsoft][ODBC SQL Server Driver][SQL Server]Processed 1 pages for database 'msdb', file 'MSDBLog' on file 1.>
DBMS MSG - SQL Message <927><[Microsoft][ODBC SQL Server Driver][SQL Server]Database 'msdb' cannot be opened. It is in the middle of a restore.>
DBMS MSG - SQL Message <3009><[Microsoft][ODBC SQL Server Driver][SQL Server]Could not insert a backup or restore history/detail record in the msdb database. This may indicate a problem with the msdb database. The backup/restore operation was still successful.>
DBMS MSG - SQL Message <3014><[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE successfully processed 5185 pages in 2.455 seconds (17.298 MB/sec).>
ERR - Error found executing <restore database "msdb" from VIRTUAL_DEVICE='VNBU0-2948-2960-1222779062' with blocksize = 512, maxtransfersize = 65536, buffercount = 1, replace , norecovery>.
08:53:18 (4684476.xxx) INF - Status = the requested operation was successfully completed.

[molonede]

BTW:  This leaves the msdb in a (Loading) state.

[NeilZhang]

I have the same question, is it a bug?

My configutations:

OS: Windows 2000 Server SP4

DB: SQL Server 2000 SP4

Netbackup: 6.0MP6

Client Log:

 OPERATION RESTORE
OBJECTTYPE DATABASE
DATABASE "msdb"
# The following image is type: Full
NBIMAGE "cnt2.MSSQL7.CNT2.db.msdb.~.7.001of001.20081123172112..C"
SQLHOST "hjh2-hz"
NBSERVER "COMPUTER"
BROWSECLIENT "cnt2"
MAXTRANSFERSIZE 0
BLOCKSIZE 7
RESTOREOPTION REPLACE
RECOVEREDSTATE RECOVERED
ENDOPER TRUE


INF - RESTORE STARTED USING
Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)
May  3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Batch = C:\Program Files\VERITAS\NetBackup\dbext\mssql\temp\__17_52_09_734_00.bch, Op# = 1.
INF - Using backup image cnt2.MSSQL7.CNT2.db.msdb.~.7.001of001.20081123172112..C
INF - restore database "msdb" from VIRTUAL_DEVICE='VNBU0-1404-1356-1227433930' with blocksize = 65536, maxtransfersize = 65536, buffercount = 1, replace , norecovery
INF - Number of stripes: 1, Number of buffers per stripe 1.
INF - Created VDI object for SQL Server instance <hjh2-hz>. Connection timeout is <300> seconds.
Restore started Sun Nov 23 17:52:11 2008

[ntanh]

me too, this is same my issue.
but i think change SQLServer Service to single mode, more infor with link
http://seer.entsupport.symantec.com/docs/266554.htm