Monday, 24 May 2010

Bonkey 3.4.1, Windows and OS X

A new version to fix a couple of bugs:
  • backing up from CloudFiles should now work (thanks to Savvas for the bug report!);
  • temporary files used in backups were being left in the user's temp directory if a backup failed - these are now removed.
Bananas bananas bananas. Find them in the usual place: Bonkey 3.4.1 for Windows and Bonkey 3.4.1 for Mac OSX.


Savvas said...

Awesome! Great! Perfect! It works extremely well!

Thank you bonkey!

Mark M. said...

I was hoping this version would solve a problem I'm having, but it didn't. When I try to check for updates in Bonkey, I get a "Network Connection Problems" message with the following details:

Network connection problems encountered during search.
Unable to access "".
Unable to access site: "" [Server returned HTTP response code: "403 Forbidden" for URL:]

Any thoughts?

bonkey said...

Hi Mark - the update functionality isn't quite complete, which unfortunately means that updating requires you to check back here and download a new version.


Jay said...

Hi Bonkey crew!

I cannot get the S3 EU backup running. It always says "unreachable" in the log. I have no idea on how I can get around this, since uploading 400gb of backups to a US S3 server really takes a lot more time then if the EU one were available.

Any idea on what I can do?

zebazga said...

Tried the latest version. It does clear the temp files on a Mac now when it fails, yay! The bad news, it still failed for me.

I added all of the Documents folder to a Group and then disabled one folder. When I ran the group, it attempted to run the disabled folder and failed. I looked, and the folder was enabled. OK, maybe I only thought I disabled it. Disabled it again, verified it was, ran it again. Again the backup tried to run that folder.

Apparently the disable doesn't work for a folder. From what I've seen, my only option now is to create a new group and just never add that folder?

FYI, running and failing filled up my hard drive and hung my entire machine. Closing Bonkey cleared the files. However, is there anyway to not hold multiple gigs of files until the end?

bonkey said...

Hi Jay - are you still having this problem? Amazon may have changed the configuration for EU. Let me know if it is still a problem and I'll look into it.


Anonymous said...

I apologize if this is the wrong place, but I am having an unusual problem. I am using bonkey to backup files to another computer on my network (using Windows 7 Homegroup) and bonkey is reporting that the backup was successful but the files do not show up on the other computer. Any idea where I should start looking?

bonkey said...

Hi AstroJason - you can see more information about the backup by opening the backup group, going to the history table at the bottom and double-clicking on an entry. This should include (to the right) the destination. Hopefully that will reveal where your files are stashed.

bonkey said...

Hi zebazga - sorry for the delay on this one. Disabling a folder should work, it sounds like there's a bug there so I'll investigate when I get some time for this. I'll also look at whether I can free the disk space earlier.

Anonymous said...

Thanks for the reply, I checked in that section and the program says it copied the files to the correct location. Also, all the files are listed in that location in Bonkey under the locations list. However, when I browse to the directory either from the machine bonkey is installed, or the machine itself there are no files. I have ensured that this machine has write access to the network directory but cannot seem to find out why this is happening.

Anonymous said...

Will you include the ability to backup new files (and still save the old version of the file) om future versions?


bonkey said...

AstroJason - that's strange. I'm not sure I can really help much here, it's very hard to debug issues with Windows networks, especially from a distance. Let me know if you figure out what the problem is. Bonkey

bonkey said...

Olof - if you use S3, you can enable versioning yourself. See