Existing users, log in.  New users, create a free account.  Lost password?

Mac OS X  |  Desktop Enhancements  |  Themes  |  psync  |  Impact of using the psync.db

psync

psync

backup/sync script in Perl

Version:  0.69.3

   [ Views: 147 ]

Impact of using the psync.db

Feedback Type:  Troubleshooting Report

Contributed by: christer15--2008 Saturday, June 27 2009 @ 01:40 AM PDT

Product Platform: MacOSX

Used Product For: Over One Year

I have successfully (or so I thought) installed psync on my new MacBook Pro running os x 10.5.6. I run it through PsyncX, which I use to schedule backup batches. I backup to a mounted network file server. PsyncX calls psync via runpsync with the options -m -p -d -r

After several backups, I noticed that a large number of new files were not backed up. Manually running psync in verbose mode (-v3) showed me that some directories were just skipped over withouth the content being analysed, for example a directory with 200 jpegs.

The only way I found to overcome the problem was to delete the .psync.db in the source root.

Can anybody explain what has happended? I thought .psync.db would mainly be used during restore to set access rights, but apprently it also controls what happens during backup. And what is the impact of deleting .psync.db before running a backup? Will it have any negative consequences? What could I do to make backups run as they should without deleing the psync.db first?

Thanks for any help and suggestions.
  
System Info:

Rate this Troubleshooting Report

Was this Troubleshooting Report helpful? Yes | No

Comments

0 comments |

No user comments.