VMware V2V fails to re-sync on occasion with error 'requested information is not available' and 'unable to delete block-level tracking bitmap'

We are completing a number of V2V migrations using VMware vCentre Converter Standalone v 5.5.3 build 2183569

The first sync is completed, and on occasion we run the re-sync in order to bring the sync up to date.

The initial sync's were completed last week, and we've ran a resync every couple of days, leading up to the migration this weekend.

On occasion one or two servers will fail to complete the re-sync. So far we have seen this 5 times across 3 different servers out of the 10.   We have deleted the clone on the target and started the sync again, the re-sync then does complete.

At present we do not know why the re-sync can seem to fail at random. Obviously if this happens when we are trying to complete the final re-sync on the night we'll have an issue as there won't be enough time to complete a full sync in the outage window.

The error we see in vmware converter is attached;
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Networking issues, VMware Converter bug, High Rate of changes in the server - all can affect the Re-Sync operation.

It's a known issue, and either re-do the initial sync, or if it bothers you too much switch products.

Which is what we have done, for commercial usage, but our use is slightly different, as we are billing the client by the day, and we cannot us software which has issues.

We now use Double-Take MOVE.

HOW TO: Migrate physical, virtual and cloud based workloads with real-time replication to VMware vSphere (ESXi) using Double-Take MOVE
drm256Author Commented:
Thanks Andrew,

I'm just leading up to a migration, so if they get through that, perfect.  Anything I can do to reduce the risk of a failure, or am I just hoping for the best?

I can then look for something else next time!
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Try and ensure, that the physical server, is quiet, e.g. try not to do the re-sync at busy times, or (disconnect the network interface).

However, re-sync can fail, the longer you leave the final sync, we often sync every day, up to the final sync, and then we do two....one 1 hour before cutover, and another 5 minutes before cutover.
drm256Author Commented:
Thank you.
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.

All Courses

From novice to tech pro — start learning today.