July 27, 2011 at 11:27 am
Turning that into something that's actually readable....
RESTORE DATABASE [db1]
FROM VIRTUAL_DEVICE='VDI_D8B0897D-3BBC-412F-B7F3-AF854B8906C6_0',
VIRTUAL_DEVICE='VDI_D8B0897D-3BBC-412F-B7F3-AF854B8906C6_1',
VIRTUAL_DEVICE='VDI_D8B0897D-3BBC-412F-B7F3-AF854B8906C6_2'
WITH BLOCKSIZE=65536, MAXTRANSFERSIZE=1048576, BUFFERCOUNT=20, STATS = 10,
MOVE N'db1' TO N'P:\MSSQL.10\Data\db1.mdf',
MOVE N'db1_log' TO N'P:\MSSQL.10\Data\db1_log.ldf',
MOVE N'db1_Indexes' TO N'P:\MSSQL.10\Data\db12.ndf',
MOVE N'MemberProperties1' TO N'P:\MSSQL.10\Data\db13.ndf',
MOVE N'SnapShot1' TO N'P:\MSSQL.10\Data\db14.ndf',
MOVE N'db12' TO N'P:\MSSQL.10\Data\db15.ndf ',
MOVE N'db1TypeId_Par_0_and_1.ndf' TO N'P:\MSSQL.10\Data\db16.ndf',
MOVE N'db1TypeId_Par_2.ndf' TO N'P:\MSSQL.10\Data\db1_1.ndf',
MOVE N'db1TypeId_Par_3.ndf' TO N'P:\MSSQL.10\Data\db1_2.ndf',
MOVE N'sysft_FaqFullTextCatalog' TO N'P:\MSSQL.10\Data\db1'
So which file shouldn't be there? Some of the secondary files' logical names look odd (logical names don't usually have .ndf, but that would just be a naming thing, nothing more), but it looks completely in order.
What 3rd party backup/restore tool is this?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
July 27, 2011 at 11:43 am
How did you delete the DB? IIRC when the db is in emergency, the log files don't get deleted.
That could be the problematic file.
July 27, 2011 at 11:46 am
We use SQL Litespeed for backup and restore.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply