P2V to Azure, how to refresh?

[tenley0]

I am migrating a physical server to azure and its taking quite some time. A few questions arise.

Can someone confirm that starwinds will do a final snap at the end to pull in all the recent changes that have occured during the migration time?

Also, is it possible to "refresh" the Azure VM later, for example, if the migration finishes and we are not ready to connect users to the Azure VM, can we rerun P2V later and just pull in incremental changes or is it a fresh start?

[yaroslav (staff)]

Yes, you can continue using the system that undergoes P2V.
The converter makes a shadow copy of the disk so that data will be up-to-date in the resulting VHDX.

[beseech]

Great to know about the shadow copy feature! To add, once the initial migration is complete, you can use Azure Site Recovery (ASR) for ongoing replication and to keep your Azure VM in sync with any changes made to the physical server. This way, you can ensure that the Azure VM is updated incrementally rather than starting from scratch. ASR also allows for testing failovers, so you can verify everything is working properly before making the final switch for users.

[yaroslav (staff)]

Thanks for your remark, I do not see how it applies to the original request though.