When I use Retrospect to backup my hard drives, it always backs up the entire winxp.hdd file -- all 13 GB of it. This is understandable. In an attempt to get a real incremental backup, I pointed Retrospect to the Windows drive via the shared volume "[C] Microsoft Windows XP" that Parallels mounts for me (which is really a view into winxp.hdd), and was expecting Retrospect to dive into the share and back up the Windows files. However, while Retrospect sees the volume, it refuses to recognize that volume as having any files. It's like it thinks the volume is empty. I have no problem pointing Retrospect to other shared volumes on real Windows machines (mounted as cifs or smb). I don't even know if this is a Retrospect issue or Parallels issue. I notice that the Parallels volume has a "Server" beginning with "file://localhost/..." which differs from "cifs://..." for my other Windows machines, but I don't know what good to make of that. Can anyone shed some light on this?
I was able to get Retrospect to recognize files on the Parallels volume by mounting it as a network share, but that seems like a very roundabout approach and I'm sure very inefficient.
