Currently Being ModeratedSep 18, 2013 7:19 PM (in response to Ron Guest)
You can't back up virtual disk files reliably or efficiently. They won't be backed up at all while open, and when closed they'll quickly fill up any backup volume. You should exclude them from backup by Time Machine and instead back up the contents in the guest system, using a native backup tool.
Currently Being ModeratedSep 19, 2013 4:59 AM (in response to Linc Davis)
I woke up this morning and tried the copy again: failed with the same error.
I then tried Linc's suggestion of turning TM off(but I didn't turn it back on). The copy failed again. So I did some more internet searching for solutions. In doing so I decided to check the Backups space shown in the System Profiler again and it showed almost no backup space (briefly because the profiler crashed right after displaying). So I tried the copy again and it worked.
Bottom line is I think turning TM off did the trick, but it took some time to free up all the space because the local backup was more than 50GB.
Currently Being ModeratedNov 20, 2013 7:36 AM (in response to Ron Guest)
Ron, I had this issue as well when transferring VM images between two disks. Both the source and destination are excluded from time machine but this process quickly bloated the local "backup" area on my drive.
I think the lack of consistency between what the system report shows as your disk usage and what finder reports is appalling. Turning off time machine, waiting to see the reclaimspaceagent run and then re-checking the disk usage in system report showed these local backups were properly removed.