RICH K.  hoooray! Works with 10.6 ! i have used this program for many years to make backups which have been indispensable. Respect to the developer for only taking 3 days to get compatibility working again!   
(Version 2.0.2)

PETER DA SILVA  Dagnabbit, I *just* switched to using Time Machine for my backups and they go and fix at least half the problems I was having with Silverkeeper.

Oh well, maybe I can use it for my bootable backups.  
(Version 2.0.1)

ATA  Thanks LaCie! I've been waiting for this update for awhile. Love this software.  
(Version 2.0.1)

RICHTHEONE  Good work POMO!

We obviously need to wake these guys up inorder to make them update SK.  
(Version 1.1.4)

POMO  Use caution: silently fails with read-only files - Version: 1.1.4

A few months back I found that several of my C++ source files were not current on my backup. As a result, I lost several days of work. I traced this problem to the following situation:

1) SK saves a read-only file to the backup.

2) The original file is changed.

3) During the next backup, SK fails to copy the changed read-only file onto the read-only version on the backup disk.

This occurs even when you have set SK to "full privilges" by entering your password.

Such a situation is likely to happen if you use a source control system that leaves files locked.

In detail, during step 3) SK changes the permissions of the backed up file to writable, but then fails to copy the changed file. If, as step 4), you do a second backup, then the changed file will be correctly copied to the backup (because the destination file is now writable). The result is that all of your changed read-only files will be backed up only every other time!

This bug is very easy to confirm by setting up a simple backup of one folder to another on your local drive.

I had a lively email exchange with LaCie about this problem, eventually diagnosing and documenting it, and giving them a clear example. Unfortunately, their final communication was "Thanks for the feedback. We will consider for the next update." That was 15-May-2006, and SK still has not been updated.

I think SK is a fine program and appreciate LaCie for providing it for free. However, this bug will bite you if you work with any read-only files that change. Until LaCie fixes it, you'll need to run SK twice to insure that such files are correctly backed up.

I hesitated to post here, but since LaCie has neither acknowledged nor fixed this bug in five months, I hope this warning will save others from a backup disaster.   
(Version 1.1.4)

RICHTHEONE  Leaks memory like a water pipe!!!  
(Version 1.1.4)

DGOMBAU  After struggling with Retrospect Express and Maxtor FireWire drive, I switched to a LaCie drive with Silverkeeper. Man, what a difference in backing up a boot drive. SK - 20 mins Vs. RE - several hours!

The SilverKeeper/LaCie boot drive booted first time. The Retrospect Express/Maxtor One Touch II combo, has always been temperemental. The first One Touch has been incredibly flakey.

In fact, Silverkeeper 1.1.4 will back up both the boot drive and a second internal hard drive for media files, with a single click.  
(Version 1.1.4)

FRANSIK  ...while the GUI could certainly be much better (too little space for localised version, among other things), it gets the job done easily (while iBackup have not worked for me)  
(Version 1.1.4)

GERWINPHILIPPO  I do not find this a very good backup tool:

1: The way sets work is very impractical: A set can only hold one directory. Which means that you have to have several sets, for Docs, Pics, Library items, etc.

Then, if you want to backup, you need to select the option "backup all sets", but that's not what I want, I only want to backup some particular directories. This is highly inflexible.

2: There is no option to include the full path in the backupdirectory. This is very inconvenient, because all users have "Documents" to backup, and now you have to create separate directories for all users to make backups for them.

3: Also, I cannot make the destination readonly to protect it from other users, because then SK fails.

4: The screen is very small, and long file names don't fit, but you cannot enlarge the screen. This is a beginners interface fault that only Philips Consumer Electronics makes usually, and they are very stupid indeed.  
(Version 1.1.4)

ANONYMOUS  My Saturday backup still overwrites my Friday, and does a Saturday, when you only specify a Saturday backup only. Minor bug, but they do need to fix the scheduling popup menus.  
(Version 1.1.4)