Veritas-bu

[Veritas-bu] SQL Restore problems

2008-10-31 03:30:13
Subject: [Veritas-bu] SQL Restore problems
From: "Sumeeth Singh (S)" <SinghS23 AT telkom.co DOT za>
To: <VERITAS-BU AT mailman.eng.auburn DOT edu>
Date: Fri, 31 Oct 2008 09:04:51 +0200

Hi,

 

I am currently experiencing some problems, performing a SQL restore. The first issue is that I can’t use the MS SQL Client GUI to generate the restore script(Call has been logged with Symantec) and am hence forced to write it manually. I have noticed that the NBIMAGE and the STORAGEIMAGE within the script are different.

 

Environment is running NBU5.1MP6, client is running the same, the backup is done using Flashsnap, using MSSQL2000 Client name is log-hr-01, Master/media server is log-bk-01.

 

Please assist if I am missing something in my restore script.

 

My scripts follows:

 

#  This is a template for the database MOVE command.

OPERATION RESTORE

OBJECTTYPE DATABASE

#  Replace the database name in the following line with the name of the database that you

#  want to move to. Also remove the hash mark <#> which precedes the keyword <DATABASE>.

DATABASE "CreditEase_2910"

#

#  Replace the file path <D:\Mssql\data\QMS.mdf>

#  with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.

#  The target of the MOVE keyword must be "QMS".

MOVE  "CreditEase_Data"

TO  "D:\SQLRestore2910\CreditEase_Data.MDF"

#

#

#  Replace the file path <T:\Mssql\data\QMS_log.LDF>

#  with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.

#  The target of the MOVE keyword must be "QMS_log".

MOVE  "CreditEase_Log"

TO  "D:\SQLRestore2910\CreditEase_Log.LDF"

#

NBIMAGE "log-hr-01.MSSQL7.LOG-HR-01.db.CreditEase.~.7.001of001.20081026144909..C"

SQLHOST "LOG-HR-01"

NBSERVER "LOG-BK-01"

BROWSECLIENT "LOG-HR-01"

MAXTRANSFERSIZE 0

BLOCKSIZE 7

RESTOREOPTION REPLACE

STORAGEIMAGE "log-hr-01.MSSQL7.LOG-HR-01.db.AOCHRS.~.7.001of001.20081026144851..C"

RECOVEREDSTATE RECOVERED

ENDOPER TRUE

 

Error follows:

 


#  This is a template for the database MOVE command.

OPERATION RESTORE
OBJECTTYPE DATABASE

#  Replace the database name in the following line with the name of the database that you
#  want to move to. Also remove the hash mark <#> which precedes the keyword <DATABASE>.

DATABASE "CreditEase_2910"
#
#  Replace the file path <D:\Mssql\data\QMS.mdf>
#  with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
#  The target of the MOVE keyword must be "QMS".
MOVE  "CreditEase_Data"
TO  "D:\SQLRestore2910\CreditEase_Data.MDF"
#
#
#  Replace the file path <T:\Mssql\data\QMS_log.LDF>
#  with a new file path. Also remove the hash mark <#> which precedes the keyword <TO>.
#  The target of the MOVE keyword must be "QMS_log".
MOVE  "CreditEase_Log"
TO  "D:\SQLRestore2910\CreditEase_Log.LDF"
#
NBIMAGE "log-hr-01.MSSQL7.LOG-HR-01.db.CreditEase.~.7.001of001.20081026144909..C"
SQLHOST "LOG-HR-01"
NBSERVER "LOG-BK-01"
BROWSECLIENT "LOG-HR-01"
MAXTRANSFERSIZE 0
BLOCKSIZE 7
RESTOREOPTION REPLACE
STORAGEIMAGE "log-hr-01.MSSQL7.LOG-HR-01.db.AOCHRS.~.7.001of001.20081026144851..C"
RECOVEREDSTATE RECOVERED
ENDOPER TRUE

INF - LOAD STARTED USING
Microsoft SQL Server  2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Enterprise Edition on Windows NT 5.0 (Build 2195: Service Pack 4)
Batch = C:\VERITAS\NetBackup\DbExt\MsSql\Data_Corruption_Restores\CreditEase_2910_AOC_SQLHOST.bch, Op# = 1.
INF - Using backup image 'log-hr-01.MSSQL7.LOG-HR-01.db.CreditEase.~.7.001of001.20081026144909..C'.
INF - Using storage image 'log-hr-01.MSSQL7.LOG-HR-01.db.AOCHRS.~.7.001of001.20081026144851..C'.
INF - restore database "CreditEase_2910" from VIRTUAL_DEVICE='VNBU0-3112-1432' with blocksize = 65536, maxtransfersize = 65536, buffercount = 1, replace , recovery, move 'CreditEase_Data' to 'D:\SQLRestore2910\CreditEase_Data.MDF', move 'CreditEase_Log' to 'D:\SQLRestore2910\CreditEase_Log.LDF', replace
INF - #Stripes: 1, #Bufs per stripe 1, From: NetBackup on LOG-BK-01
INF - Created VDI object for SQL Server instance <*DEFAULT*>. Connection timeout is <300> seconds.
Restore started Fri Oct 31 08:42:26 2008


08:42:29 (118382.xxx) Restore job id 118382 will require 1 image.
08:42:29 (118382.xxx) Media id 1489L3 is needed for the restore.

08:47:33 (118382.001) Restoring from image created 10/26/08 14:51:43
08:47:35 (118382.001) INF - Waiting for mount of media id 1489L3 on server log-bk-01 for reading.
08:47:35 (118382.001) INF - Data socket = log-bk-01.3180
08:47:35 (118382.001) INF - Name socket = log-bk-01.1547
08:47:35 (118382.001) INF - Job id = 118382
08:47:36 (118382.001) INF - Backup id = log-hr-01_1225025503
08:47:36 (118382.001) INF - Backup time = 1225025503
08:47:36 (118382.001) INF - Policy name = LOG-HR-01-FlashSnap_Monthly
08:47:36 (118382.001) INF - Snapshot = 0
08:47:37 (118382.001) INF - Frozen image = 0
08:47:37 (118382.001) INF - Backup copy = 0
08:47:37 (118382.001) INF - Master server = log-bk-01
08:47:37 (118382.001) INF - Media server = log-bk-01
08:47:37 (118382.001) INF - New data socket = log-bk-01.2470
08:47:38 (118382.001) INF - Use shared memory = 0
08:47:38 (118382.001) INF - Restore id = 118382.001
08:47:38 (118382.001) INF - Encrypt = 0
08:47:38 (118382.001) INF - Client read timeout = 3600
08:47:39 (118382.001) INF - Media mount timeout = 1800
08:47:39 (118382.001) INF - client = log-hr-01
08:47:39 (118382.001) INF - requesting_client = log-hr-01
08:47:39 (118382.001) INF - browse_client = LOG-HR-01
08:48:16 (118382.001) INF - Waiting for positioning of media id 1489L3 on server log-bk-01 for reading.
08:50:14 (118382.001) INF - Beginning restore from server log-bk-01 to client log-hr-01.
08:51:27 /log-hr-01.MSSQL7.LOG-HR-01.db.CreditEase.~.7.001of001.20081026144909..C
08:51:30 (118382.001) Status of restore from image created 10/26/08 14:51:43 = the requested operation was successfully completed

DBMS MSG - ODBC message. ODBC return code <-1>, SQL State <37000>, Message Text <[Microsoft][ODBC SQL Server Driver][SQL Server]The file on device 'VNBU0-3112-1432' is not a valid Microsoft Tape Format backup set.>
DBMS MSG - <[Microsoft][ODBC SQL Server Driver][SQL Server]RESTORE DATABASE is terminating abnormally.>
ERR - Error found executing <restore database "CreditEase_2910" from VIRTUAL_DEVICE='VNBU0-3112-1432' with blocksize = 65536, maxtransfersize = 65536, buffercount = 1, replace , recovery, move 'CreditEase_Data' to 'D:\SQLRestore2910\CreditEase_Data.MDF', move 'CreditEase_Log' to 'D:\SQLRestore2910\CreditEase_Log.LDF', replace>
ERR - Error in VDS->Close: 0x80770004. The text follows:
    CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #1 of batch C:\VERITAS\NetBackup\DbExt\MsSql\Data_Corruption_Restores\CreditEase_2910_AOC_SQLHOST.bch FAILED with status 1. Elapsed time = 546(546) seconds.
08:51:32 INF - Server status = 0
INF - Results of executing <C:\VERITAS\NetBackup\DbExt\MsSql\Data_Corruption_Restores\CreditEase_2910_AOC_SQLHOST.bch>:
<0> operations succeeded. <1> operations failed.
08:51:33 (118382.xxx) INF - Status = the requested operation was successfully completed.

 

 

Regards,
Sumeeth Singh
Telkom SA Ltd
ITX Hosting Support : Storage Management
( : 012 680 3020
@ : 012 680 3299
) : 082 402 8944
* : SinghS23 AT telkom.co DOT za
As you move up to the level of "success" don’t ever forget to send the lift down.”

 

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This e-mail is subject to the Telkom SA electronic communication legal notice, available at :
http://www.telkom.co.za/TelkomEMailLegalNotice.PDF
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
<Prev in Thread] Current Thread [Next in Thread>
  • [Veritas-bu] SQL Restore problems, Sumeeth Singh (S) <=