I have just completed my first planned failover to cloud (partial, only 1 VM) to the VCC provider and everything worked as expected on failover and connectivity using NEA. I then ran a failback, which worked fine, but I need some help understand a couple things as highlighted in this screenshot:
I don't understand how 14GB of changes occurred (2nd highlight). The VM itself only consumes about 24GB on disk (as thin provisioned) in its entirety and only changes I directly made while the replica was booted was logging in via console and creating a text file not he desktop. The first highlight seemed like a more appropriate size for changes made to the replica that needed to be replicated back to on-prem. This VM was only failed over for maybe 30 minutes while I did basic connectivity testing.
It seems like almost the entire VM was replicated back to on-prem on failback, is this normal? I did not use "Quick Rollback" option during failback--if I used that would I see different behavior?