February 23, 2011 at 2:42 am
Guys,
I am facing issues with the SQL Server 2000 SP4 database restoration. Here is the complete scenario:
I have a VMWare that is connected to the EMC storage. i.e. the drives E:,F:,G: are actually the EMC storage drives. When i try to restore the database on any of these drives, the following error comes:
"Modify file encountered operating system error 2(the system cannot find the file specified) while attempting to expand the physical file. Could not create one or more files. Consider using the WITH MOVE option to identify valid locations. RESTORE database is terminating abnormally."
Also in my application event logs, i got the error "Operating system error 2(The system cannot find the file specified.) encountered."
The script that i used for restoring the database is as follows:
exec master.dbo.xp_restore_database @database = N'test', @filename = N'D:\ERPPROD_FULL.BAK', @filenumber = 1, @with = N'RECOVERY', @with = N'NOUNLOAD', @with = N'STATS = 10', @with = N'MOVE N''PSSYS84_INDEX'' TO N''E:\test_index.ndf''', @with = N'MOVE N''PSSYS84_data'' TO N''F:\test_Data.mdf''', @with = N'MOVE N''PSSYS84_log'' TO N''G:\test_Log.ldf'''
I also tried to do it from enterprise manager but the same error comes.
One important point to note here that all the drives E:,F:,G: are having the RAW file system. When i try to use the above script to restore database on the other NTFS local drives or on a server that has NTFS file system, it works perfectly!!
So the question is:
1. Is it an issue with the VMware. Seems like its not..
2. Is it an issue with the RAW file system. Seems like Yes. But wats the solution????
Regards,
Led
February 25, 2011 at 12:20 am
Sounds more like a disk space issue.
Restoring the data files will create them at the same size as they were when they were when backed up - including empty space. Look at the source db from where the backup was taken and see the individual file sizes, then ensure that the destination paths in the restore has enough disk space. Use WITH MOVE to relocate the data files at the time of restoring to alternate drives with more space.
I'm running several servers that happen to be VM (against my recommendation), that are SQL2000 sp4 and sitting on RAW disks. I suppose there may be a SS hot fix difference or a VM version diff between you and I.
Jim
Jim Murphy
http://www.sqlwatchmen.com
@SQLMurph
February 25, 2011 at 2:46 am
Hey Jim,
Its not a disk space issue. We have enough space in the server. The situation seems complex than that. OK. So as i am new to the RAW file system (I have never worked on it before), here is a very basic question:
Like we create or restore a database thru Enterprise manager on an NTFS drive, do we do the same way for RAW file system? I mean i have 3 drives with RAW file system. While restoring the database, i use them for .mdf, .ldf and .ndf (separate file group for Indexes). And If you see the script in my previous post, i am using the WITH MOVE option.
FYI, the RAW file system that i am using is actually a part of EMC storage...
February 25, 2011 at 7:26 am
I saw you were using with move. I was just noting to cross examine the disk space requirements one more time.
Have you tried to create a simple db on the RDM drives as they exist in your configuration? If this works, the restore should work.
RDM is the way to go for SS. Faster, but harder to administer. The only issues that I have heard with this is if the RDM is not in physical compatibility mode or if the server is part of a cluster. Otherwise, seem to be lots of folks using this configuration.
Jim
Jim Murphy
http://www.sqlwatchmen.com
@SQLMurph
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply