UNSOLVED

Tomi

updated

20 years ago

T

Tomi

36 Posts

0

5145

March 1st, 2007 06:00

MSSQL2005 restore problem

Environments:

NW Server 7.1.3
NW Client 7.2 build 494 (aka jumbo 7.2.2)
NMSQL 5.0

Win2003 Server x64 SP1
MS SQL Server 2005 64-bit

Problem:
Backing the online databases went without problems.
The problem is while trying to restore a SQL database. Fails only.

Questions:
Can the restore be done while the SQL is online? Is it possible to restore a database to a different name? Is there something wrong with my recover syntax?

Any help would be greatly appreciated.

Log:
C:\>nsrsqlrc -s nw.server.local -t 02/28/07 -d MSSQL:TESTDB2 -c sql01

MSSQL:TESTDB[4796] 03/01/07 15:32:31 Recovering database 'TESTDB' into 'TESTDB2' ...
RESTORE database [TESTDB2] FROM virtual_device='Legato#31cb6f69-a6d3-465c-b0c3-1b4a12de6444' WITH move 'TESTDB_1_Log' to 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\Data\TESTDB2_TESTDB_log2_9612.ldf', move 'studiofore5_Data' to 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\Data\TESTDB2_TESTDB_9612.mdf', move 'studiofore5_data2' to 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\Data\TESTDB2_TESTDB2_9612.mdf', move 'studiofore5_Log' to 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\Data\TESTDB2_TESTDB_log_9612.ldf'
[4796] 03/01/07 15:34:08 TESTDfore SQL Server Provider error:
[4796] 03/01/07 15:34:08 The file 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\FTData\SearchDump0003' cannot be overwritten. It is being used by database 'TESTDB'..
[4796] 03/01/07 15:34:08 File 'sysft_SearchDump' cannot be restored to 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\FTData\SearchDump0003'. Use WITH MOVE to identify a valid location for the file..
[4796] 03/01/07 15:34:08 The file 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\FTData\ItemCatalog0003' cannot be overwritten. It is being used bydatabase 'TESTDB'..
[4796] 03/01/07 15:34:08 File 'sysft_ItemCatalog' cannot be restored to 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\FTData\ItemCatalog0003'. Use WITH MOVE to identify a valid location for the file..
[4796] 03/01/07 15:34:08 The file 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\FTData\AttachmentCatalog0003' cannot be overwritten. It is being used by database 'TESTDB'..
[4796] 03/01/07 15:34:08 File 'sysft_AttachmentCatalog' cannot be restoredto 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\FTData\AttachmentCatalog
0003'. Use WITH MOVE to identify a valid location for the file..
[4796] 03/01/07 15:34:08 The file 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\FTData\SearchTemp0003' cannot be overwritten. It is being used by database 'TESTDB'..
[4796] 03/01/07 15:34:08 File 'sysft_SearchTemp' cannot be restored to 'D:\Program Files\TESTDfore SQL Server\MSSQL.1\MSSQL\FTData\SearchTemp0003'. Use WITH MOVE to identify a valid location for the file..
[4796] 03/01/07 15:34:08 Problems were identified while planning for the RESTORE statement. Previous messages provide details..
[4796] 03/01/07 15:34:08 RESTORE DATABASE is terminating abnormally..
[4796] 03/01/07 15:34:08 nsrsqlado.cpp(2525): ExecuteFailed event arrived.
[4796]
03/01/07 15:34:08 Error processing SQL database 'TESTDB'.
nsrsqlrc: unknown XBSA error 1359 (0x54f)
  • Tomi

    36 Posts

    2022

    0

    Posted March 1st, 2007 06:00

    Yes I'm the SQL admin. I gave the networker all the required accesses also.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2022

    0

    Posted March 1st, 2007 06:00

    Are you MS SQL admin?
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2022

    0

    Posted March 1st, 2007 07:00

    Try

    nsrsqlrc -s nw.server.local -c sql01 -d MSSQL:TESTDB2 MSSQL:DB

    (I assume here MSSQL:DB is original database). You need to run that from host where you are restoring db.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2022

    0

    Posted March 1st, 2007 07:00

    I think there should force option when doing restore. Not sure what switch is from CLI - should somewhere in docs. If you check on SQL forums you will see this quite often. What confuses me here is that it looks as it wants to overwrite TESTDB. Anyway, try to use -C and specify new path. I think I have read also that order in which parameters are send it important so pay attention to that.
  • Tomi

    36 Posts

    2022

    0

    Posted March 1st, 2007 07:00

    Keep getting the same error messages.
    ...."cannot be overwritten. It is being used by database 'TESTDB'..

    Why does it want to write on the used files, shouldnt it create new ones?
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2022

    0

    Posted March 1st, 2007 11:00

    You get that even with -C?
  • Tomi

    36 Posts

    2022

    0

    Posted March 2nd, 2007 00:00

    With the option -C it seems to start doing restoring however it seems to overwrite the old db.

    I want to create a new restored db or if possible restore the db to a file on the client computer.
  • ble1

    6 Operator

    •

    14354 Posts

    •

    56186 Points

    2028

    0

    Posted March 2nd, 2007 00:00

    I don't have some system to test this so I would suggest to contact your support. Not sure about your SQL module, but latest build for 5.0 is 184 - might be you need a patch or something. I would suggest to place a call with support and see what is going on. If it still fails as you say with -C and you used option as outlined on page 179 of admin guide I guess something is not working then as it should so support is next step.
  • Tomi

    36 Posts

    504

    0

    Posted March 16th, 2007 04:00

    Not yet.. I sent the problem to our local networker support. Seems like they couldnt help either so they will be opening a case with EMC about this.
  • asiden

    5 Posts

    2027

    0

    Posted March 16th, 2007 04:00

    Hi

    Did you get a solution to this? I have the same problem!

    Cheers
    Andreas