September 18, 2008 at 12:59 pm
I am trying to restore a database from a monthend backup. The restore fails with Error: 3633, Severity: 16, State: 1.
The operating system returned the error '32(The process cannot access the file because it is being used by another process.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'E:\MSSQL\Data\AMCMO.mdf'.
I have run checkdb with no errors reported.
How do I fix this condition to complete the restore operation?
Todd Lemmiksoo
September 18, 2008 at 1:17 pm
Todd - Are you restoring over an existing database? Everything that I am finding on the web is indicating a file access issue, i.e. the file that is specified in the error is being used by another process. Can you send the restore script you are using?
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
September 18, 2008 at 1:28 pm
I think David is right, either you are restoring on top of the original database in which case you need the WITH REPLACE option, or you are restoring on top of a different database (restoring to database B, but on top of database A's files), in which case you need the WITH MOVE option to specify a new filename. If you are using the GUI - these options are on the 2nd tab (options, I believe).
Chad
September 18, 2008 at 1:38 pm
If restoring on an existing database use REPLACE and RESTRICTED_USER in restore command.
or kill all processes using this database at the time of restore.
SQL DBA.
September 18, 2008 at 2:59 pm
I am using the GUI and have replace on the second page selected.
Yes, am restoring to exsisting database.
Todd
September 18, 2008 at 4:07 pm
Make sure that the database isn't highlighted in blue when using the GUI to restore.
Stupid, I know. But if you left-click the database in question you want to restore, and then right-click "Restore"; management studio holds a lock on the database.
Just right-click over the database you want to restore over and choose Restore. Or better yet, write out a restore statement via t-sql...you'll learn more about the process.
Your friendly High-Tech Janitor... 🙂
September 19, 2008 at 11:30 am
thanks for all the replies. I am not the DBA/SQL guy here. Just have to pick up the pieces she is not around. I have to use the GUI as I know nothing about T-SQL or SQL commands.
I have discovered the problem with the restore. The backup is from SQL2000 and can not be used as a restore with SQL2005.
Todd
September 19, 2008 at 11:36 am
You can restore a 2000 backup to a 2005 server. That's a common upgrade path for many...
Something else is still going on.
Look up the RESTORE command in Books Online (it will be in the MSSQL Program Group). There are detailed examples that you should be able to follow.
Your friendly High-Tech Janitor... 🙂
September 19, 2008 at 1:31 pm
I was hopeing to not have to get into all of our dirt. Basiclly I was using SQL2005 to restore a SQL2000 database into a Sql2000 server without knowing it. I was led to believe that the database was a SQL2005 database from month end. But the person in charge of the application had not created a maintenance plan for backup after converting to SQL2005. Todd
September 19, 2008 at 1:34 pm
A bit confused by the last post but that is ok, it is pretty easy to do with me. 🙂
If you have a SQL Server 2000 backup then you can restore that to a SQL Server 2000 instance and / or a SQL Server 2005 instance. If you are using SQL Server 2005 tools you should still be able to do all that I just stated as well so, that should be a viable backup.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
September 19, 2008 at 1:53 pm
It does not work that way here. Both SQL instances are on the same box.
No need to go on.
todd
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply