SQL Databse Suspect after p2v conversion.

[PCSTUD]

When I run a p2v conversion of my sql 2000 server, one of the databases comes up as "suspect" and will not mount? I have been running daily conversions for months without a problem, but added a P600 array controller with a MSA50 and moved the databases to the MSA50 and left the log files on the server (moved into one directory). I do not understand why this one database comes up as suspect after the change. I can not bring down the sql services as this is a production server. I run the p2v conversion on VMware server 2.0.

[IamTHEvilONE]

Converter 3 does sequential snapshots ... I know this can bother some/most SQL servers that have different components on different partitions.

If you have 3 drives (C/D/E), and run converter against it ... you could have a situation like:

Convert C starting at 0 minutes

Convert D starting at 60 minutes (note that this data will be 60 minutes newer than the C drive)

Convert E starting at 120 minutes (note that this data will be 60 minutes newer than the D drive, and 120 minutes newer than the C drive)

This is assuming you have not shut down the SQL system to freeze data transactions.

I would also check the normal stuff for a suspect database per Microsoft.

Regards,

EvilOne

1 - Check the documents

2 - Search the forums

3 - Post Question

And remember to award points to those who assist you.

[paragsha · Accepted solution]

You should try using the converter 4.0 beta since we have made some imporvements to solve such problems (some changes in the way we snapshot). Also using Converter 4.0 beta you could choose to stop the SQL services before we take the snapshots, hence insuring database consistency.

[IamTHEvilONE]

>some changes in the way we snapshot

Specifically, we snapshot all volumes at the same time. So as long as the conversion completes, the db should have consistency.

There is also a catch up feature to allow a "second pass" during the conversion that would double check to see if anything changed since the start of the data copy.

so there is lots of love for Converter 4.0

[PCSTUD]

Thank you that makes sense, because the DB's and log files shared the same drive, but now have been moved to separate drives. I've only used Converter 4.0 in my test lab since it is beta. I will try Converter 4.0 in production due to all of the enhancements. Thank you again!

[PCSTUD]

If I stop the SQL services with Converter before the snapshots, how long will the services be down and will they restart, or do you have to restart the services manually?

[paragsha]

You will need to restart the services manually.

[PCSTUD]

And how long will the services need to be down for, the entire conversion or just during the snapshot?

[IamTHEvilONE]

entire conversion with 3.0.x.

I think 4.0 should technically be able to handle it without shutting down the services.

however, this will be more of a trail.

[paragsha]

Like Iamtheone said, you don't "have" to shut down the services for your use case. The reason that option is provided is so that you can shut down the services at the source machine and start them at the destination automatically after the import. Thus making sure that the database on your destination VM is the same as the source machine.

In your case you don't have to shut down the services. If you do decide to do it, you can restart them after snapshots.

[PCSTUD]

Cool, I am running a p2v of the SQL server now using converter 4.0. I will post the results. Thanks for all of your assistance!

[PCSTUD]

The conversion completed with 4.0 but the VM blue screens trying to boot?

[PCSTUD]

Oh, and I set the converter to NOT reconfigure the VM because I am using this for a DRP and need the VM to be the same.

[PCSTUD]

I do see from my successful 3.0 conversion, that the disk controller is BUS Logic and I selected "preserve source" in 4.0 it came up as LSI logic? I tried changing it to BUS but it still blue screens?

[PCSTUD]

I started a new conversion, selecting the reconfigure source virtual machine. I guess you need to select this to make it bootable? The only reason I did not select this option was because when I ran a 4.0 conversion test on my workstation, it said that I needed to activate windows before logging on?

[IamTHEvilONE]

I ran a 4.0 conversion test on my workstation, it said that I needed to activate windows before logging on?

You probably had an OEM version of windows, hence the activation. When you do a P2V, the virtual machine is considered a brand new set of hardware .... so an OEM windows will require activation before you can use it.

[PCSTUD]

Converter 3.0 worked without activation?

[IamTHEvilONE]

converter 3 and 4 should be the same in that respect.

it's a windows thing, not a vmware converter thing. if you took a physical computer and replaced enough hardware in it ... you'd have to activate it as well

[PCSTUD]

Last 4 attempts hit 28%, set there for about 5 hrs and dies? 3.0 worked every time until separating the databases and logs, it still works but a DB comes up as suspect some of the times.