Package: backupninja Version: 0.9.6-4 Severity: wishlist Hi,
Apparently no locking of anykind is performed when backupninja launches backup actions. This might cause launching of several concurrent instances of the same backup action job, which is not desirable. This would happen if the first backup action does not finish until the next one is scheduled. For example, one might have an rdiff-backup job scheduled to run daily, which normally completes in matter of minutes or hours. But due to large changes in data and congested network link, it might take more than 24 hours to do the backup data transfer. I think backupninja should implement per-backup action locking so that in this case further invocations of the job would be skipped until the long-running job started previous day is finished. Regards, -- Tuomas Jormola <t...@solitudo.net>
signature.asc
Description: Digital signature
