[Cerio]

JJG,

Synchronizing to a backup file is a one way sync. It only pulls changes out of the backup file to synchronize to the device. It does not update the backup file with changes on the device because the backup files don't work that way - they can't dynamically resize to accomodate new songs and data. The entire file would have to be reconstructed in that case and it would be no better than you just generating a new backup file using the normal mechanism. If you make changes to your library and then sync to a backup file, what were you expecting to happen? If you change the merge behavior to "prompt user" then you will be notified of any changes, and then you could undo the changes you made. If you leave the default setting, you updated your library after the backup file was created so it's going to treat your changes as the latest and ignore the differences in the backup file.

Mike

Ok, probably it's a stupid question, but what is the purpose of that feature then? I only use a single device, have a big database, add new songs often, and all I need is backing up my database to Google drive from time to time. Is still faster to use the old method for me?

Thanks.