Hello.
Yes, ok thank You. Finaly I got my test conversions.
And, if you dont mind, I wish make little beat of source question. In pointed ealrier topic about SQL conversion your final post was:
Let me give you a brief explanation how scheduled synchronization works: a bitmap driver starts tracking all changed clusters on the disk before the cloning starts. When the time for sync comes, a VSS snapshot is being done on the source volumes, and all the changed clusters are read from > that snapshot and transferred.
You can also instruct Converter to stop some services before the final sync, e.g, SQL server and exchange. Thus there will be no lost data from those services' activity.
There is two points before my question.
First is: As I understand, a job for pass a snapshot is work for one time. Against a complicate method in vMotion technology, when, as we told, for memory transfer uses set of snapshots, each over less in set, and finaly source freezes for a second and destination activates.
Second is: As I know, in example for oracle databases there is important to get syncroneous files in one time, because all datafiles has own identifier of thats called SCN, and it provides of DB consistence. And if they after copying finaly have not equal value in destination, then you cannt startup DB without hard manipulation or cannt startup at all (therefore it called as 'cold backup' and realy many beginners got a big trouble after try recover from cold backup, if it maked in warm state with running DB instance). And I think similar thing should be in most production databases.
And question is (sure, I'm not first, but however): have a place trouble when we do P2V and have running DB on VM (or any other db-like service)? In case of that trouble: have a VMware ability and plans to resolve that?