July 18, 2012 at 9:22 pm
I converted a physical server to a virtual server using vmware converter 5. MS Server is 2008 R2 as is the sql server. One database won't start. Other ones are functional. I noticed that there now are 2 entries in the studio pull down list for the same database and neither work.
Any ideas would be appreciated.
thanks
Ken
July 18, 2012 at 11:34 pm
I suspect the non-functional db was in use at some point during the P2V and is marked as unavailable. Error messages from the sql server log file should give you details.
If that isthe case, either redo the P2V, having ensured SQl server is sut down first, or take a database backup from the old real server and restore to the new virtual one.
Mike
July 19, 2012 at 2:49 am
Mike is correct here, the P2V operation is on a per drive basis and if a database is in use the time period netween the transafer of the data and log files can stop the database from starting on the clone VM. Best thing is to take a backup of the database from the physical tin box and restore it to the VM.
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 19, 2012 at 1:53 pm
I shutdown all SQL services and ran the converter but still have the same issue.
If I run a full backup, how do I restore it to the instance that it is in if the instance won't run?
What about detatching the database then cloning and reattaching?
thanks
Ken
July 19, 2012 at 1:56 pm
Error messages please? All relevant ones from the SQL error log. Plus a more detailed description of exactly what's wrong. I'm not sure if you have a database that won't start or a SQL instance that won't start.
Do not detach the damaged database, not likely to help, very likely to make matters worse.
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 19, 2012 at 2:32 pm
ken.schilstra (7/19/2012)
I shutdown all SQL services and ran the converter but still have the same issue.If I run a full backup, how do I restore it to the instance that it is in if the instance won't run?
What about detatching the database then cloning and reattaching?
thanks
Ken
Check the logs for more detailed info, can you access the remaing user and system databases. Also try and restore the backup as a new database name on the vm and verify that the database starts successfully.
How many disks does the source server have?
What size and partition type are the disks?
Were they all converted?
Were they resized?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
July 20, 2012 at 9:51 am
Thanks everyone for your help and guidance.
I found the problem in the log for I guess its called an instance. It shows up in the services listing as SQLserver (DAPS) (daps is the database instance name).
What I found in the DAPS log was that it was unable to inititalize and listen on the network connection.
The reason was that the virtualized machine used a different network driver for its virtualized connection.
I configured the network connection and removed the network interface that had come from the physical server and then everything worked.
Thanks Again.
Ken
July 20, 2012 at 9:59 am
thanks for posting back,
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply