SQL 2005 - restoring a database; media formed incorrectly error

I have two SQL servers - both on different domains.  Both running SQL 2005.

I'm trying to export a database from the one server and then restore it to the other server.  (Both servers are running the same database, but one is a test environment, a virtual machine, that's used for testing items in the database).

This is the error i'm getting when i try to restore the database.  It shows up in SQL management studio as '**INCOMPLETE**'.

I've tried copying the file from the original SQL server over the network, i've tried even running the backup from server1 with management studio running on server2 (where i'm trying to get the backup restored to).

I'm running out of ideas.  What can i do?
untitled.JPG
Mystical_IceAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

kenwagersCommented:
Try using 'reattaching' the server.    Shut down server 1, and then copy the database and log files to server 2.  Restart server 1.  On server 2, right click on the Databases option in Microsoft SQL Server Management Studio, and select Attach.  Choose the files you just moved.

This also has the advantage of being quite a bit faster than backup / restore.  But it will only work if you can shut down Server 1 while you make copies of the files.
0
ylarvorCommented:
solution : you can detach the database from the server A after all user be stop, you copy the file , not move, to the server b and attach the file and the log.

that's dangerous, so be careful!
0
DBAduck - Ben MillerPrincipal ConsultantCommented:
I think that if you ran SELECT @@VERSION on each server you would find that one is a different version than the other.  Post the results and this may help us help you better.

SELECT @@VERSION
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

Coralie CrumrineCommented:
Usually you see this message if the backup file has been corrupted or was not able to complete for some reason.
Try first of all to take a new and complete (full) backup. Make sure that it is not appending to a previous backup file. Make sure that the process is completed before moving the file over to the new location.
If you continue to see the same message, something is not right with the backup process and you will want to check the error logs to see if there is a reason why it is not backing up correctly.
0
ylarvorCommented:
I think like dbaduck! I had the same problem in CTIFL last year!
0
Mystical_IceAuthor Commented:
Sorry for the delay in getting back to this question, and i appreciate all the responses.  In the end, this was the correct one.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.