I'm finding that qrecall chokes and won't backup a Windows virtual machine that's suspended within Parallels. I had been excluding my VMs from my backups, but just switched to a larger hard drive and decided to eliminate that exclusion. The first failure occurred during my daily backup of User files on 7/2. It killed that backup but left the archive intact, so I added the exclusion back in and thought I'd solved the problem.

Then yesterday I ran a manual full back without the exclusion. This time the VM both killed the backup and screwed up the archive. I'm repairing it now, and will add the exclusion back into the full backup as well. I can live with keeping the VM excluded from my backups, but thought you'd like to know about this problem.

Here are the console log entries from the two failures. Let me know if you'd like a full problem report from Qrecall.

2011-07-02 12:36:12.594 -0700 Failure Could not capture Windows XP VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds [2.734320.1567.64]

2011-07-02 12:36:12.718 -0700 Details File: mbhd:Users:ralph:Parallels:Windows XP VM.pvm:Windows XP VM-0.hdd:Windows XP VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds [2.734320.1567.64.1]

2011-07-02 12:36:12.742 -0700 Details Path: mbhd:Users:ralph:Parallels:Windows XP VM.pvm:Windows XP VM-0.hdd [2.734320.1567.65.1.2]

2011-07-02 12:36:12.743 -0700 Failure Could not process folder Windows XP VM-0.hdd [2.734320.1567.65.1]



2011-07-04 04:44:16.250 -0700 Failure Could not capture Windows XP VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds [2.734321.7804.76]

2011-07-04 04:44:16.303 -0700 Details File: mbhd:Users:ralph:Parallels:Windows XP VM.pvm:Windows XP VM-0.hdd:Windows XP VM-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds [2.734321.7804.76.1]

2011-07-04 04:44:16.599 -0700 Details Path: mbhd:Users:ralph:Parallels:Windows XP VM.pvm:Windows XP VM-0.hdd [2.734321.7804.77.1.2]

2011-07-04 04:44:16.599 -0700 Failure Could not process folder Windows XP VM-0.hdd [2.734321.7804.77.1]

Ralph

Ralph,

Please send a full diagnostic report. There's usually some additional log messages, near the ones you copied, that will tell which API QRecall was using and what the error code was.

Thanks!