I was hoping during the V2V conversion I would have been able to select a new disk size based on the amount of data - as in, usually the limit is the amount of disk in use plus 10% - I would have been happy with the amount of space in use and double that for the target disk. The C volume let me do that, but the D volume would not - it was like the 300GB is use times 5, instead of plus 10%. So I never even ran the V2V because it would have been useless based on that. Definitely I think I will retrace the steps from the AppAssure export and see if I missed anything.
Plamen wrote:
Perhaps conversion is not the right thing in this case. Can you afford to add a new virtual disk with appropriate size and just copy the files there? (assuming all system files are on C:)
Yes, the system Files are on C. I like this idea. So I can simply create a new virtual disk and copy the files, and then remove the oversized volume, using the vSphere Web Client? I will look into this. Thanks!