I've recently been testing Espionage, and the way it manages encrypted disk images seems ideal for my requirements. However, I've encountered an issue with the built-in backup facility.
Having set up all my encrypted folder today, I attempted to run my first backup. The backup was to a networked drive, connected via AFP. The local machine's OS in OS X 10.6.4 and the remote (on an internal network, via gigabit ethernet) machine's OS is 10.5.8.
I left the backup running for a couple of hours, and when I came back noticed that Espionage was still attempting to backup the first folder. I was a bit surprised, as although it's a reasonably large folder (approx 1GB) I didn't expect it to take that long. Checking the backup folder on the networked drive I noticed well over 100,000 zero kb sparse bundle files had been created and this was still increasing very quickly! I stopped the backup by restarting my machine and tried a much smaller folder, but had exactly the same issue - within minutes there were several thousand zero kb files.
As a test, I created a new folder and placed a single 300kb file inside it and tried backing it up to the network drive. Again, within a couple of minutes I had over 7,000 zero kb files in the destination folder.
Wondering whether it was the fact it was a networked drive causing the issue, I attempted to backup to a local folder instead. The backup completed successfully within seconds.
So it seems that Espionage doesn't like my network! Can you advise if there might be something I'm doing incorrectly that could fix this issue? This is pretty key for me, as the networked machine backs up to the cloud overnight, so is an important element of my backup strategy.
Thanks in advance! :)
Having set up all my encrypted folder today, I attempted to run my first backup. The backup was to a networked drive, connected via AFP. The local machine's OS in OS X 10.6.4 and the remote (on an internal network, via gigabit ethernet) machine's OS is 10.5.8.
I left the backup running for a couple of hours, and when I came back noticed that Espionage was still attempting to backup the first folder. I was a bit surprised, as although it's a reasonably large folder (approx 1GB) I didn't expect it to take that long. Checking the backup folder on the networked drive I noticed well over 100,000 zero kb sparse bundle files had been created and this was still increasing very quickly! I stopped the backup by restarting my machine and tried a much smaller folder, but had exactly the same issue - within minutes there were several thousand zero kb files.
As a test, I created a new folder and placed a single 300kb file inside it and tried backing it up to the network drive. Again, within a couple of minutes I had over 7,000 zero kb files in the destination folder.
Wondering whether it was the fact it was a networked drive causing the issue, I attempted to backup to a local folder instead. The backup completed successfully within seconds.
So it seems that Espionage doesn't like my network! Can you advise if there might be something I'm doing incorrectly that could fix this issue? This is pretty key for me, as the networked machine backs up to the cloud overnight, so is an important element of my backup strategy.
Thanks in advance! :)