Problem Restoring Backup database in MSSQL 2000.

I made a backup of one of my databases from one server and now I'm trying to restore to the production server (Clustering)using Enterprise Manager.I remote the server- launched Enterprise Manager andI select the restore from disk and I give the full path of a local drive in the server where the backup is located - when I clicked "ok" it first tells me: "Unable to verify the existence of the backup file location. Do you want to use the backup file location anyway?" If I answer "Yes" and "OK" it presents a error msg: "Cannpt open backup device 'c:.......bak. Restore database terminating - Microsoft SQL-DMO(ODBC SQLSTATE 42000). I have moved this backup around and I still get the same msg. Can anybody help - need assistance ASAP - thank you

Ensure that the sql service account has write permissions for the folder containing the backup. You can also use the T-sql to perform restoration. Pls use the below syntax,
(a) RESTORE FILELISTONLY FROM DISK='D:\YourBackupfilename.bak'
GO
(b)RESTORE DATABASE NewDatabaseName
FROM DISK='D:\YourBackupfilename.bak'
WITH MOVE'LOgicalName of the SOurceDatafile' TO 'D:\NewDatabase.mdf',
MOVE 'Logicalname of sourcelogfile' TO'D:\NewDatabase_log.ldf'

Note : To get the logical file name run the step (a) and copy past the data and log file name
Change the script accordingly and run. If you overwriting an existing database use With replace in (b)

- Deepak

Deer Deepak,

I am having similar error with a different message.

---------------------------
Microsoft SQL-DMO (ODBC SQLState: 42000)
---------------------------
There is insufficient free space on disk volume 'D:\' to create the database. The database requires 17881628672 additional free bytes, while only 9883058176 bytes are available.
RESTORE DATABASE is terminating abnormally.


I have more than 9 GB space available in my D drive. What else I am missing here?

Thanks
Sajid

Excuse me for the reviving of the long abandoned topic, but I've see this question unanswered.

I got this error message, too, and didn't solve this problem. Now I use the third-party SQL backup software. For me, it was the one viable solution.

If this problem may be solved correctly using internal means, I will glad to see the solution in the future.

Again, I'm sorry for my too late comment.

Excuse me for the reviving of the long abandoned topic, but I've see this question unanswered.

I got this error message, too, and didn't solve this problem. Now I use the third-party SQL backup software. For me, it was the one viable solution.

If this problem may be solved correctly using internal means, I will glad to see the solution in the future.

Again, I'm sorry for my too late comment.

Hello Please raise a new question or start a new thread.Its really of no use posting on old thread

Hope this helps