https://forums.qrecall.com/posts/list/6.page JForum - http://www.jforum.net https://forums.qrecall.com/posts/preList/582/2740.page https://forums.qrecall.com/posts/preList/582/2740.page GMT
First, make sure you're using QRecall 2.0 (currently in [url=http://www.qrecall.com/download/]beta[/url], but close to a final release). If your still running into problems, send a diagnostic report.]]> https://forums.qrecall.com/posts/preList/582/2742.page https://forums.qrecall.com/posts/preList/582/2742.page GMT
I am still seeing some issues with backing up running VMs.

[list]If said VMs have active snapshots, the backup time increases hugely, with the machine crawling to the verge of being completely unusable[/list]
[list]I also see that QRecall spends an inordinate amount of time trying to backup vmware lck files (I guess I should exclude them, but not sure how to proceeded with files within a package)

[img]http://i.imgur.com/MqbUrA3.jpg[/img][/list]

Any suggestion most welcome]]> https://forums.qrecall.com/posts/preList/582/2817.page https://forums.qrecall.com/posts/preList/582/2817.page GMT
If that doesn't help, there are additional things to try.

It's also unlikely that QRecall is spending a lot if time capturing .lck files. These tend to be very small semaphore files. It's more likely that a .lck file was just the last thing it captured while looking for the next thing to capture.]]> https://forums.qrecall.com/posts/preList/582/2818.page https://forums.qrecall.com/posts/preList/582/2818.page GMT