Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


#245 Continue on error


When having the most complete backup possible is rather more important than the backup integrity, it would be very nice to be able to skip errors. I'm not talking about simple locked files that can be easily skipped (right now, I get an unexpected error that need further investigation, I'll let you know as soon as I get more precise information),


  • I have failed backups on a big job (300Gb, 10K files) because sometimes a file is deleted after the backup job was started but before Areca copies him. Then I get a FileNotFoundException and the whole job is rolled back. It would be nice being able to ignore such trivial erros.

    I don't know if it would feasible for Areca to use Linux inotify or a simillar API to monitor files on a backup set and so know when a file is deleted or changes permissions during the job and so prevent errors.