Thanks joshopper,
That's what I noticed in the past, when I changed datastore location it would just create a new swap file. But since I got this error I reassessed that assumption thinking maybe vSphere copied the existing swap rather then creating a new one. Good to know that it is a fresh build on start up!
I've run through all possible swap file settings, and the new data stores have plenty of available space.
Here is the exact error I see when I set it to "Store with virtual machine"
Failed to create swap file '/vmfs/volumes/53c63036-4a12ebfc-c8d0-00221982bfe2/vmx-wwgen_VEEAMHost01-1525547079-1.vswp' : Not found
Could not start VMX: msg.vmk.status.VMK_NOT_FOUND
I even removed the VM, went back and added the VMX to inventory, and then removed the hard drive and pointed a new virtual hard drive to the proper VMDK file. So by all means I feel it should be working.
Something is probably not being addressed properly, as in it's looking for a directory that doesn't exist. I just don't know where that directory setting is and can be changed.
Thanks,
Peter